| View previous topic :: View next topic |
| Author |
Message |
edgar_uriel84
Guru
Joined: 21 Dec 2008
Posts: 485
Location: Tultitlan, México
|
 Posted: Sun Jun 18, 2023 5:19 am Post subject: Error de compilación de dev-ruby/kpeg |
 |
|
Hola a todos.
Estoy haciendo mi actualización semestral de Gentoo, me sale este error, a ver si a alguien más le pasa:
| Code: | * Messages for package dev-ruby/kpeg-1.3.3:
* ERROR: dev-ruby/kpeg-1.3.3::gentoo failed (install phase):
* Unable to generate gemspec file.
*
* Call stack:
* ebuild.sh, line 136: Called src_install
* environment, line 2110: Called ruby-ng_src_install
* environment, line 1708: Called _ruby_each_implementation 'each_ruby_install'
* environment, line 445: Called _ruby_invoke_environment 'ruby31' 'each_ruby_install'
* environment, line 600: Called each_ruby_install
* environment, line 860: Called each_fakegem_install
* environment, line 807: Called ruby_fakegem_install_gemspec
* environment, line 1997: Called die
* The specific snippet of code:
* fi ) || die "Unable to generate gemspec file.";
*
* If you need support, post the output of `emerge --info '=dev-ruby/kpeg-1.3.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-ruby/kpeg-1.3.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-ruby/kpeg-1.3.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-ruby/kpeg-1.3.3/temp/environment'.
* Working directory: '/var/tmp/portage/dev-ruby/kpeg-1.3.3/work/ruby31/kpeg-1.3.3'
* S: '/var/tmp/portage/dev-ruby/kpeg-1.3.3/work/ruby31/kpeg-1.3.3'
Task was destroyed but it is pending!
task: <Task pending name='Task-5' coro=<ForkProcess._proc_join() running at /usr/lib/python3.11/site-packages/portage/util/_async/ForkProcess.py:81> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[_EbuildFetcherProcess._proc_join_done(<Process name...code=-SIGTERM>)()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-9' coro=<SpawnProcess._main() running at /usr/lib/python3.11/site-packages/_emerge/SpawnProcess.py:180> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.11/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[SpawnProcess._main_exit()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-8' coro=<PipeLogger._io_loop() running at /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:98> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-7' coro=<BuildLogger._main() running at /usr/lib/python3.11/site-packages/portage/util/_async/BuildLogger.py:101> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.11/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[BuildLogger._main_exit()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-6' coro=<PipeLogger._io_loop() running at /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:98> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]> |
En eselect he seleccionado Ruby 31 y el error persiste. También traté con MAKEOPTS="-j1" y persiste. Sigo buscando la solución, espero alguien me de una idea.
Saludos.
_________________
Algún día habrá una persona mejor que yo, pero esa persona no eres tú ni ese momento es ahora. |
|
| Back to top |
|
 |
quilosaq
Veteran
Joined: 22 Dec 2009
Posts: 1539
|
| Posted: Sun Jun 18, 2023 11:01 am Post subject: |
|
|
Prueba a desinstalar y volver a instalar ruby 31. Si no funciona publica tu y | Code: | | /var/tmp/portage/dev-ruby/kpeg-1.3.3/temp/build.log |
|
|
| Back to top |
|
|
edgar_uriel84
Guru
Joined: 21 Dec 2008
Posts: 485
Location: Tultitlan, México
|
| Posted: Sun Jun 18, 2023 6:02 pm Post subject: |
|
|
Gracias por la respuesta quilosaq.
Encontré el problema, parece que no ha terminado de actualizarse todo a Ruby 3.1
El paquete dev-ruby/psych-5.1.0 del cual depende kpeg, solo tiene RUBY_TARGETS="-ruby30*". Toca esperar a que todo se actualice supongo.
_________________
Algún día habrá una persona mejor que yo, pero esa persona no eres tú ni ese momento es ahora. |
|
| Back to top |
|
|
quilosaq
Veteran
Joined: 22 Dec 2009
Posts: 1539
|
| Posted: Sun Jun 18, 2023 6:36 pm Post subject: |
|
|
| edgar_uriel84 wrote: | ...
El paquete dev-ruby/psych-5.1.0 del cual depende kpeg, solo tiene RUBY_TARGETS="-ruby30*"
... |
Esa configuración de RUBY_TARGETS que dices no está en el ebuild, lo mas probable es que la tengas en tu sistema. Revisa los archivos en | Code: | | /etc/portage/package.use |
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Spanish
