| View previous topic :: View next topic |
| Author |
Message |
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
 Posted: Sun Jan 09, 2022 5:34 pm Post subject: circular dependency problem in preserved rebuild |
 |
|
Dear All,
I am running | Code: | | gentoo amd64 stable |
on an FX 8350 box.
I ran the following command:
| Code: | | pigface / # USE=-test emerge --ask --autounmask --update @preserved-rebuild |
the end of the output to the terminal is as follows:
| Code: | sqlite ssl xml -bluetooth -build -examples -hardened -lto% -pgo% -test -tk -verify-sig -wininst (-ipv6%*)" 18,709 KiB
Total: 237 packages (215 upgrades, 20 new, 2 in new slots), Size of downloads: 1,665,848 KiB
* Error: circular dependencies:
(virtual/libcrypt-2:0/2::gentoo, ebuild scheduled for merge) depends on
(sys-libs/libxcrypt-4.4.25-r1:0/1::gentoo, ebuild scheduled for merge) (runtime)
(dev-lang/perl-5.34.0-r3:0/5.34::gentoo, ebuild scheduled for merge) (buildtime)
(virtual/libcrypt-2:0/2::gentoo, ebuild scheduled for merge) (buildtime_slot_op)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
pigface / #
|
My file looks like this:
| Code: | pigface /etc/portage # more make.conf
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
MAKEOPTS="-j9"
USE="elogind alsa audit discover desktop-portal display-manager farstream grub gtk gui handbook intros
pection jpeg2k mdev non-root network networkmanager consolekit corefonts ipv6 jpeg pie positioning
pulseaudio qt5 smart suid tcl tiff test threads thunderbolt tools truetype udev vala wallpapers widget
s X xml xorg"
VIDEO_CARDS="nouveau"
INPUT_DEVICES="libinput synaptics"
ACCEPT_LICENSE="* =@EULA"
#ACCEPT_KEYWORDS="~amd64"
# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/var/db/repos/gentoo"
DISTDIR="/var/cache/distfiles"
PKGDIR="/var/cache/binpkgs"
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
GENTOO_MIRRORS="https://mirror.bytemark.co.uk/gentoo/"
GRUB_PLATFORMS="efi-64"
pigface /etc/portage #
|
There was a long delay since my last sync to the repositories and I think something is not quite right as
a result.
Suggestions on e.g. some use flag changes that could fix this would be appreciated.
Regards
MF
PS
The output of is here:
https://paste.debian.net/1226492/ |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 5:48 pm Post subject: |
|
|
It should be simpler
| Code: |
emerge @preserved-rebuild
|
Why are you running this?
Did portage request you to?
A better option would be
| Code: |
emerge --sync
emerge -uDUav --keep-going --with-bdeps=y @world
emerge -a --depclean
#####THEN IF PORTAGE ADVISES YOU
emerge @preserved-rebuild
|
_________________
Last edited by alamahant on Sun Jan 09, 2022 5:58 pm; edited 1 time in total |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 5:56 pm Post subject: |
|
|
Many thanks for your response.
I had problems with conflicting dependencies etc in world updates and so I removed a lot of
packages to try to fix the problem.
But then emerge started to ask me to run the @preserved-rebuild command to add packages back in again.
I ran the standard command
| Code: | | emerge @preserved-rebuild |
and I now get the following output:
| Code: | Total: 561 packages (234 upgrades, 1 downgrade, 314 new, 3 in new slots, 9 reinstalls), Size of downloads: 3,208,789 KiB
* Error: circular dependencies:
(dev-python/pytest-cov-3.0.0:0/0::gentoo, ebuild scheduled for merge) depends on
(dev-python/pytest-cov-3.0.0:0/0::gentoo, ebuild scheduled for merge) (buildtime)
It might be possible to break this cycle
by applying the following change:
- dev-python/pytest-cov-3.0.0 (Change USE: -test)
Note that this change can be reverted, once the package has been installed.
Note that the dependency graph contains a lot of cycles.
Several changes might be required to resolve all cycles.
Temporarily changing some use flag for all packages might be the better option.
WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
dev-python/docutils:0
(dev-python/docutils-0.18:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_9 (-pypy3) (-python3_10) -python3_8" conflicts with
<dev-python/docutils-0.18[python_targets_python3_9(-)] required by (dev-python/sphinx-4.3.1:0/0::gentoo, ebuild scheduled for merge) USE="test -doc -latex" ABI_X86="(64)" PYTHON_TARGETS="python3_9 (-pypy3) (-python3_10) -python3_8"
^ ^^^^
pigface /etc/portage #
|
I will try emerging the python cov-3.0.0 package.
It probably won't fix the problem.
Cheers
Regards
MF
PS
I ran
| Code: | pigface /etc/portage # USE=-test emerge dev-python/pytest-cov
|
and got the following output:
| Code: | Calculating dependencies... done!
!!! The following installed packages are masked:
- sys-libs/glibc-2.32-r7::gentoo (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# Andreas K. Hüttel <dilfridge@gentoo.org> (2017-05-21)
# (and others, updated later)
# These old versions of toolchain packages (binutils, gcc, glibc) are no
# longer officially supported and are not suitable for general use. Using
# these packages can result in build failures (and possible breakage) for
# many packages, and may leave your system vulnerable to known security
# exploits.
# If you still use one of these old toolchain packages, please upgrade (and
# switch the compiler / the binutils) ASAP. If you need them for a specific
# (isolated) use case, feel free to unmask them on your system.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
>>> Verifying ebuild manifests
>>> Emerging (1 of 16) dev-python/setuptools-59.2.0::gentoo
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
* setuptools-59.2.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
* python-gentoo-patches-3.10.0rc1.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking setuptools-59.2.0.tar.gz to /var/tmp/portage/dev-python/setuptools-59.2.0/work
>>> Unpacking python-gentoo-patches-3.10.0rc1.tar.xz to /var/tmp/portage/dev-python/setuptools-59.2.0/work
/usr/lib/portage/python3.9/phase-helpers.sh: line 365: xz: command not found
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
* ERROR: dev-python/setuptools-59.2.0::gentoo failed (unpack phase):
* unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz
*
* Call stack:
* ebuild.sh, line 127: Called src_unpack
* environment, line 2941: Called default
* phase-functions.sh, line 858: Called default_src_unpack
* phase-functions.sh, line 885: Called __eapi0_src_unpack
* phase-helpers.sh, line 785: Called unpack 'setuptools-59.2.0.tar.gz' 'python-gentoo-patches-3.10.0rc1.tar.xz'
* phase-helpers.sh, line 537: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 366: Called __assert_sigpipe_ok 'unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz'
* isolated-functions.sh, line 41: Called die
* The specific snippet of code:
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
*
* If you need support, post the output of `emerge --info '=dev-python/setuptools-59.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-python/setuptools-59.2.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/setuptools-59.2.0/work'
* S: '/var/tmp/portage/dev-python/setuptools-59.2.0/work/setuptools-59.2.0'
>>> Failed to emerge dev-python/setuptools-59.2.0, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'
* Messages for package dev-python/setuptools-59.2.0:
* ERROR: dev-python/setuptools-59.2.0::gentoo failed (unpack phase):
* unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz
*
* Call stack:
* ebuild.sh, line 127: Called src_unpack
* environment, line 2941: Called default
* phase-functions.sh, line 858: Called default_src_unpack
* phase-functions.sh, line 885: Called __eapi0_src_unpack
* phase-helpers.sh, line 785: Called unpack 'setuptools-59.2.0.tar.gz' 'python-gentoo-patches-3.10.0rc1.tar.xz'
* phase-helpers.sh, line 537: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 366: Called __assert_sigpipe_ok 'unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz'
* isolated-functions.sh, line 41: Called die
* The specific snippet of code:
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
*
* If you need support, post the output of `emerge --info '=dev-python/setuptools-59.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-python/setuptools-59.2.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/setuptools-59.2.0/work'
* S: '/var/tmp/portage/dev-python/setuptools-59.2.0/work/setuptools-59.2.0'
pigface /etc/portage # dev-python/pytest-cov-3.0.0 |
It might be that I have a date and clock problem that is stopping me fetching some packages from the gentoo repositories . I think I can fix that and then try it again if it is a problem.
Cheers
MF
Last edited by mikefot on Sun Jan 09, 2022 6:02 pm; edited 1 time in total |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 6:01 pm Post subject: |
|
|
Maybe
| Code: |
USE="-test" emerge -1av pytest-cov
emerge @preserved-rebuild
|
plz REMEMBER:
When rebuilding packages always use
emerge -1 .......
You get
| Code: |
/usr/lib/portage/python3.9/phase-helpers.sh: line 365: xz: command not found
|
Maybe
| Code: |
emerge -1av xz-utils
|
_________________
Last edited by alamahant on Sun Jan 09, 2022 6:23 pm; edited 1 time in total |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 6:13 pm Post subject: |
|
|
Many thanks again.
an OK apart from a bit of grumble toward the end:
| Code: |
...normal output from start.....
xfce-extra/xfce4-power-manager/xfce4-power-manager-4.16.0.ebuild
xfce-extra/xfce4-wavelan-plugin/Manifest
xfce-extra/xfce4-wavelan-plugin/xfce4-wavelan-plugin-0.6.2-r1.ebuild
Number of files: 147,871 (reg: 121,112, dir: 26,759)
Number of created files: 2,935 (reg: 2,865, dir: 70)
Number of deleted files: 3,104 (reg: 2,974, dir: 130)
Number of regular files transferred: 28,867
Total file size: 236.79M bytes
Total transferred file size: 88.04M bytes
Literal data: 88.04M bytes
Matched data: 0 bytes
File list size: 3.87M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 589.89K
Total bytes received: 93.15M
sent 589.89K bytes received 93.15M bytes 1.14M bytes/sec
total size is 236.79M speedup is 2.53
!!! Unable to verify: gemato-14.5+ is required
Action: sync for repo: gentoo, returned code = 127
|
I then ran the command you suggested to emerge dev-python cov:
| Code: | pigface /etc/portage # USE="-test" emerge -1av pytest-cov
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] dev-python/setuptools-59.2.0::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild UD ] dev-python/certifi-3021.3.16-r1::gentoo [10001-r1::gentoo] USE="-test" PYTHON_TARGETS="python3_9* (-pypy3) -python3_8* (-python3_10) (-python3_7%*)" 0 KiB
[ebuild N ] dev-python/pyparsing-2.4.7-r1::gentoo USE="-examples" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/packaging-21.0::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild U ] dev-python/setuptools_scm-6.3.2::gentoo [6.0.1-r1::gentoo] USE="-test" PYTHON_TARGETS="python3_9* (-pypy3) -python3_8* (-python3_10) (-python3_7%*)" 0 KiB
[ebuild N ] dev-python/py-1.11.0::gentoo USE="-doc -test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild R ] dev-python/toml-0.10.2::gentoo USE="-test" PYTHON_TARGETS="python3_9* (-pypy3) -python3_8* (-python3_10) (-python3_7%*)" 0 KiB
[ebuild N ] dev-python/coverage-6.1.2::gentoo PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/iniconfig-1.1.1::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/more-itertools-8.11.0::gentoo USE="-doc -test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/pluggy-1.0.0-r1::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/namespace-zope-1-r1::gentoo PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/zope-interface-5.4.0::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/attrs-21.2.0::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/pytest-6.2.5-r2::gentoo USE="-test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
[ebuild N ] dev-python/pytest-cov-3.0.0::gentoo USE="-doc -test" PYTHON_TARGETS="python3_9 (-pypy3) -python3_8 (-python3_10)" 0 KiB
Total: 16 packages (1 upgrade, 1 downgrade, 13 new, 1 reinstall), Size of downloads: 0 KiB
!!! The following installed packages are masked:
- sys-libs/glibc-2.32-r7::gentoo (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# Andreas K. Hüttel <dilfridge@gentoo.org> (2017-05-21)
# (and others, updated later)
# These old versions of toolchain packages (binutils, gcc, glibc) are no
# longer officially supported and are not suitable for general use. Using
# these packages can result in build failures (and possible breakage) for
# many packages, and may leave your system vulnerable to known security
# exploits.
# If you still use one of these old toolchain packages, please upgrade (and
# switch the compiler / the binutils) ASAP. If you need them for a specific
# (isolated) use case, feel free to unmask them on your system.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 16) dev-python/setuptools-59.2.0::gentoo
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
* setuptools-59.2.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
* python-gentoo-patches-3.10.0rc1.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking setuptools-59.2.0.tar.gz to /var/tmp/portage/dev-python/setuptools-59.2.0/work
>>> Unpacking python-gentoo-patches-3.10.0rc1.tar.xz to /var/tmp/portage/dev-python/setuptools-59.2.0/work
/usr/lib/portage/python3.9/phase-helpers.sh: line 365: xz: command not found
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
* ERROR: dev-python/setuptools-59.2.0::gentoo failed (unpack phase):
* unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz
*
* Call stack:
* ebuild.sh, line 127: Called src_unpack
* environment, line 2941: Called default
* phase-functions.sh, line 858: Called default_src_unpack
* phase-functions.sh, line 885: Called __eapi0_src_unpack
* phase-helpers.sh, line 785: Called unpack 'setuptools-59.2.0.tar.gz' 'python-gentoo-patches-3.10.0rc1.tar.xz'
* phase-helpers.sh, line 537: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 366: Called __assert_sigpipe_ok 'unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz'
* isolated-functions.sh, line 41: Called die
* The specific snippet of code:
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
*
* If you need support, post the output of `emerge --info '=dev-python/setuptools-59.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-python/setuptools-59.2.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/setuptools-59.2.0/work'
* S: '/var/tmp/portage/dev-python/setuptools-59.2.0/work/setuptools-59.2.0'
>>> Failed to emerge dev-python/setuptools-59.2.0, Log file:
>>> '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'
* Messages for package dev-python/setuptools-59.2.0:
* ERROR: dev-python/setuptools-59.2.0::gentoo failed (unpack phase):
* unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz
*
* Call stack:
* ebuild.sh, line 127: Called src_unpack
* environment, line 2941: Called default
* phase-functions.sh, line 858: Called default_src_unpack
* phase-functions.sh, line 885: Called __eapi0_src_unpack
* phase-helpers.sh, line 785: Called unpack 'setuptools-59.2.0.tar.gz' 'python-gentoo-patches-3.10.0rc1.tar.xz'
* phase-helpers.sh, line 537: Called __unpack_tar 'xz -d'
* phase-helpers.sh, line 366: Called __assert_sigpipe_ok 'unpack: failure unpacking python-gentoo-patches-3.10.0rc1.tar.xz'
* isolated-functions.sh, line 41: Called die
* The specific snippet of code:
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
*
* If you need support, post the output of `emerge --info '=dev-python/setuptools-59.2.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-python/setuptools-59.2.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-59.2.0/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/setuptools-59.2.0/work'
* S: '/var/tmp/portage/dev-python/setuptools-59.2.0/work/setuptools-59.2.0'
pigface /etc/portage #
|
Since emerge --sync worked it can't be that we can't get hold of the python setuptools package to compile it.
Comments appreciated on the problem here.
Regards
MF
PS
The build.log file for this is here:
http://dpaste.com/94R5VS377
Last edited by mikefot on Sun Jan 09, 2022 6:28 pm; edited 1 time in total |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 6:20 pm Post subject: |
|
|
Plz look my above edited post about
xz-utils
Then run
_________________
|
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 6:41 pm Post subject: |
|
|
Many thanks again.
I looked at the xzutils post. I am not quite sure how it fits in with my situation yet.
Maybe I need to reset my profile.
I will check on this.
Meanwhile I tried running your command:
The output is here:
https://paste.debian.net/1226497/
Here is a bit of the output:
| Code: | >>> Failed to emerge sys-libs/glibc-2.33-r7, Log file:
>>> '/var/tmp/portage/sys-libs/glibc-2.33-r7/temp/build.log'
* Messages for package sys-libs/glibc-2.33-r7:
* Simple build failed ... assuming this is desired #324685
* Failed to compile the ABI test. Broken host glibc?
* Could not find a gcc that supports the __thread directive!
* Please update your binutils/gcc and try again.
* ERROR: sys-libs/glibc-2.33-r7::gentoo failed (pretend phase):
* No __thread support in gcc!
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* glibc-2.33-r7.ebuild, line 728: Called sanity_prechecks
* glibc-2.33-r7.ebuild, line 689: Called die
* The specific snippet of code:
* die "No __thread support in gcc!"
*
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.33-r7::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.33-r7::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.33-r7/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.33-r7/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.33-r7/empty'
* S: '/var/tmp/portage/sys-libs/glibc-2.33-r7/work/glibc-2.33'
Task was destroyed but it is pending!
task: <Task pending name='Task-20' coro=<ForkProcess._proc_join() done, defined at /usr/lib/python3.9/site-packages/portage/util/_async/ForkProcess.py:75> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f901a71fd60>()]> cb=[_EbuildFetcherProcess._proc_join_done(<Process name...code=-SIGTERM>)()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-21' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.9/site-packages/portage/util/_async/PipeLogger.py:85> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f901b611220>()]> cb=[PipeLogger._io_loop_done()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-22' coro=<BuildLogger._main() done, defined at /usr/lib/python3.9/site-packages/portage/util/_async/BuildLogger.py:98> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.9/site-packages/_emerge/AsynchronousTask.py:49, <TaskWakeupMethWrapper object at 0x7f901b1c2d60>()]> cb=[BuildLogger._main_exit()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-23' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.9/site-packages/portage/util/_async/PipeLogger.py:85> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7f901b611d60>()]> cb=[PipeLogger._io_loop_done()]>
Task was destroyed but it is pending!
task: <Task pending name='Task-24' coro=<SpawnProcess._main() done, defined at /usr/lib/python3.9/site-packages/_emerge/SpawnProcess.py:177> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.9/site-packages/_emerge/AsynchronousTask.py:49, <TaskWakeupMethWrapper object at 0x7f901c086760>()]> cb=[SpawnProcess._main_exit()]> |
Comments appreciated.
Regards
MF |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 6:53 pm Post subject: |
|
|
| Quote: |
I looked at the xzutils post. I am not quite sure how it fits in with my situation yet.
|
It fits because portage can not untar because it lacks
/usr/bin/xz binary.
Things seem dire
| Code: |
* Simple build failed ... assuming this is desired #324685
* Failed to compile the ABI test. Broken host glibc?
* Could not find a gcc that supports the __thread directive!
* Please update your binutils/gcc and try again.
* ERROR: sys-libs/glibc-2.33-r7::gentoo failed (pretend phase):
* No __thread support in gcc!
|
_________________
|
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 7:00 pm Post subject: |
|
|
Many thanks for your help again.
I tried compiling in the hope it cure the problem.
But it crashes:
| Code: | pigface /etc/portage # emerge xzutils
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "xzutils".
emerge: searching for similar names...
emerge: Maybe you meant any of these: app-arch/xz-utils, x11-apps/xkbutils, dev-util/cutils?
pigface /etc/portage # emerge app-arch/xz-utils
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-arch/xz-utils-5.2.5-r1::gentoo
* xz-5.2.5.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking xz-5.2.5.tar.gz to /var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work
>>> Source unpacked in /var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work
>>> Preparing source in /var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5 ...
* Running elibtoolize in: xz-5.2.5/
* Applying ppc64le/2.4.4 patch ...
* Running elibtoolize in: xz-5.2.5/build-aux/
* Applying portage/1.2.0 patch ...
* Applying sed/1.5.6 patch ...
* Applying as-needed/2.4.3 patch ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5 ...
* abi_x86_64.amd64: running multilib-minimal_abi_src_configure
* econf: updating xz-5.2.5/build-aux/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating xz-5.2.5/build-aux/config.sub with /usr/share/gnuconfig/config.sub
/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5/configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/xz-utils-5.2.5-r1 --htmldir=/usr/share/doc/xz-utils-5.2.5-r1/html --with-sysroot=/ --libdir=/usr/lib64 --enable-threads --enable-nls --disable-static
XZ Utils 5.2.5
System type:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
Configure options:
checking if debugging code should be compiled... no
checking which encoders to build... lzma1 lzma2 delta x86 powerpc ia64 arm armthumb sparc
checking which decoders to build... lzma1 lzma2 delta x86 powerpc ia64 arm armthumb sparc
checking which match finders to build... hc3 hc4 bt2 bt3 bt4
checking which integrity checks to build... crc32 crc64 sha256
checking if external SHA-256 should be used... no
checking if assembler optimizations should be used... x86_64
checking if small size is preferred over speed... no
checking if threading support is wanted... yes, posix
checking how much RAM to assume if the real amount is unknown... 128 MiB
checking if library symbol versioning should be used... yes
checking if sandboxing should be used... maybe (autodetect)
checking for a shell that conforms to POSIX... /bin/sh
Initializing Automake:
checking for a BSD-compatible install... /usr/lib/portage/python3.9/ebuild-helpers/xattr/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether ln -s works... yes
checking whether make supports the include directive... yes (GNU style)
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5-abi_x86_64.amd64':
configure: error: C compiler cannot create executables
See `config.log' for more details
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5-abi_x86_64.amd64/config.log
* ERROR: app-arch/xz-utils-5.2.5-r1::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 1651: Called multilib-minimal_src_configure
* environment, line 1039: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 1292: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 969: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 967: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 359: Called multilib-minimal_abi_src_configure
* environment, line 1033: Called multilib_src_configure
* environment, line 1514: Called econf '--enable-threads' '--enable-nls' '--disable-static'
* phase-helpers.sh, line 711: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=app-arch/xz-utils-5.2.5-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-arch/xz-utils-5.2.5-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/temp/environment'.
* Working directory: '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5-abi_x86_64.amd64'
* S: '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5'
>>> Failed to emerge app-arch/xz-utils-5.2.5-r1, Log file:
>>> '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/temp/build.log'
* Messages for package app-arch/xz-utils-5.2.5-r1:
* ERROR: app-arch/xz-utils-5.2.5-r1::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 1651: Called multilib-minimal_src_configure
* environment, line 1039: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 1292: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 969: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 967: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 359: Called multilib-minimal_abi_src_configure
* environment, line 1033: Called multilib_src_configure
* environment, line 1514: Called econf '--enable-threads' '--enable-nls' '--disable-static'
* phase-helpers.sh, line 711: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=app-arch/xz-utils-5.2.5-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-arch/xz-utils-5.2.5-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/temp/environment'.
* Working directory: '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5-abi_x86_64.amd64'
* S: '/var/tmp/portage/app-arch/xz-utils-5.2.5-r1/work/xz-5.2.5'
pigface /etc/portage # |
Comments appreciated.
Regards
MF
PS
The build.log file for the crash is here:
http://dpaste.com/FXARVUF5Y
MF |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 7:04 pm Post subject: |
|
|
You get
| Code: |
configure: error: C compiler cannot create executables
|
Maybe you need a more drastic step like using an intermediate build chroot
https://wiki.gentoo.org/wiki/Upgrading_Gentoo#Updating_old_systems
But plz defer that until you are certain that there is no way out.
Just make sure also that in make.conf
| Code: |
COMMON_FLAGS="-O2 -pipe"
|
the O2 is <CAPITAL-O>2 NOT <ZERO>2
_________________
Last edited by alamahant on Sun Jan 09, 2022 7:11 pm; edited 1 time in total |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 7:07 pm Post subject: |
|
|
Many thanks.
I am already chrooting into the gentoo install from an ubuntu install I have on the same machine.
Cheers
MF
PS
I think I am already using the 17.1 profile:
See here:
| Code: | pigface /etc/portage # eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/17.1 (stable) *
[2] default/linux/amd64/17.1/selinux (stable)
[3] default/linux/amd64/17.1/hardened (stable)
[4] default/linux/amd64/17.1/hardened/selinux (stable)
[5] default/linux/amd64/17.1/desktop (stable)
[6] default/linux/amd64/17.1/desktop/gnome (stable)
[7] default/linux/amd64/17.1/desktop/gnome/systemd (stable)
[8] default/linux/amd64/17.1/desktop/plasma (stable)
[9] default/linux/amd64/17.1/desktop/plasma/systemd (stable)
[10] default/linux/amd64/17.1/desktop/systemd (stable)
[11] default/linux/amd64/17.1/developer (exp)
[12] default/linux/amd64/17.1/no-multilib (stable)
[13] default/linux/amd64/17.1/no-multilib/hardened (stable)
[14] default/linux/amd64/17.1/no-multilib/hardened/selinux (stable)
[15] default/linux/amd64/17.1/no-multilib/systemd (dev)
[16] default/linux/amd64/17.1/no-multilib/systemd/selinux (exp)
[17] default/linux/amd64/17.1/systemd (stable)
[18] default/linux/amd64/17.1/systemd/selinux (exp)
[19] default/linux/amd64/17.1/clang (exp)
[20] default/linux/amd64/17.0 (dev)
[21] default/linux/amd64/17.0/selinux (dev)
[22] default/linux/amd64/17.0/hardened (dev)
[23] default/linux/amd64/17.0/hardened/selinux (dev)
[24] default/linux/amd64/17.0/desktop (dev)
[25] default/linux/amd64/17.0/desktop/gnome (dev)
[26] default/linux/amd64/17.0/desktop/gnome/systemd (dev)
[27] default/linux/amd64/17.0/desktop/plasma (dev)
[28] default/linux/amd64/17.0/desktop/plasma/systemd (dev)
[29] default/linux/amd64/17.0/developer (exp)
[30] default/linux/amd64/17.0/no-multilib (dev)
[31] default/linux/amd64/17.0/no-multilib/hardened (dev)
[32] default/linux/amd64/17.0/no-multilib/hardened/selinux (dev)
[33] default/linux/amd64/17.0/systemd (dev)
[34] default/linux/amd64/17.0/x32 (dev)
[35] default/linux/amd64/17.0/musl (exp)
[36] default/linux/amd64/17.0/musl/hardened (exp)
[37] default/linux/amd64/17.0/musl/hardened/selinux (exp)
[38] default/linux/amd64/17.0/uclibc (exp)
[39] default/linux/amd64/17.0/uclibc/hardened (exp)
pigface /etc/portage #
|
Regards
MF
Last edited by mikefot on Sun Jan 09, 2022 7:14 pm; edited 1 time in total |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 7:13 pm Post subject: |
|
|
| Quote: |
Many thanks.
I am already chrooting into the gentoo install from an ubuntu install I have on the same machine.
Cheers
|
Yes but the intermediate chroot is not the same like a normal chroot.
Plz read the wiki carefully..
Since you are now in ubuntu the procedure will be something like
| Code: |
#### exit from the chroot and into ubuntu
#### unmount the gentoo system
mkdir /mnt/build
tar --acls --xattrs -xpvf <fresh-stage3> -C /mnt/build
##### then chroot into /mnt/build like the normal way
##### mount your old system on the intermediate chroot's /mnt
then run
emerge --sync
eslelect profile set 1
env update
emerge --root=/mnt --config-root=/mnt -1av xz-utils
emerge --root=/mnt --config-root=/mnt -1av glibc gcc binutils
emerge --root=/mnt --config-root=/mnt @preserved-rebuild
emerge --root=/mnt --config-root=/mnt -uDUav @world
emerge --root=/mnt --config-root=/mnt -a --depclean
#####then exit chroot and reboot into livecd/or ubuntu system again delete any stage3 files from /mnt/build and remount your old gentoo system.
|
Somethinglike that
And check again my updated post about CFLAGS
_________________
Last edited by alamahant on Sun Jan 09, 2022 7:46 pm; edited 6 times in total |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 7:23 pm Post subject: |
|
|
Many thanks again.
The wiki page seems to suggest that you make a new mount point for a new upgraded version of the system.
If the upgrade works presumably you keep it and delete the old one (or part of it????)?
Please excuse my ignorance here.
Cheers
MF |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Jan 09, 2022 7:35 pm Post subject: |
|
|
Plz look a very rough attempt into describing how to do it above.
PLZ be CAREFUL.
_________________
|
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 7:43 pm Post subject: |
|
|
Many thanks.
I will tread carefully.
Regards
MF |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23686
|
| Posted: Sun Jan 09, 2022 8:00 pm Post subject: |
|
|
| alamahant wrote: | You get | Code: | | configure: error: C compiler cannot create executables |
Maybe you need a more drastic step like using an intermediate build chroot |
Before we go there, perhaps we should find out why the C compiler fails. The build output suggests examining config.log. What does that log show? |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Sun Jan 09, 2022 9:28 pm Post subject: |
|
|
Many thanks for your help again.
The output is here:
http://dpaste.com/8NVNDER3A
Regards
MF
The log file shows that some input file is missing to run the compiler. Or something like that. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23686
|
| Posted: Sun Jan 09, 2022 9:45 pm Post subject: |
|
|
| http://dpaste.com/8NVNDER3A: | configure:5328: x86_64-pc-linux-gnu-gcc -O2 -pipe -Wl,-O1 -Wl,--as-needed conftest.c >&5
x86_64-pc-linux-gnu-gcc: fatal error: cannot execute 'as': execvp: No such file or directory
compilation terminated. |
Your as is broken. Is binutils installed, and properly set? What is the output of emerge --pretend --verbose sys-devel/binutils ; binutils-config -l? This is also implicitly shown by omission in your emerge --info output. There should be a line telling us what binutils versions you have, but there is not. |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2402
|
| Posted: Sun Jan 09, 2022 10:01 pm Post subject: |
|
|
| (Note that you should be doing preserved-rebuild last after a depclean too, and it looks like you need to focus on a world upgrade right now, but there's obviously other issues that have been picked up on by posters here.) |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Tue Jan 11, 2022 10:28 am Post subject: |
|
|
Many thanks for the help again.
| Code: | pigface / # emerge --pretend --verbose sys-devel/binutils ; binutils-config -l
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] dev-tcltk/expect-5.45.4::gentoo USE="threads -debug -doc" 0 KiB
[ebuild N ] dev-util/dejagnu-1.6.3::gentoo USE="test" 0 KiB
[ebuild N ] sys-devel/binutils-2.37_p1:2.37::gentoo USE="gold nls plugins test (-cet) -default-gold -doc -multitarget -static-libs -vanilla" 0 KiB
Total: 3 packages (3 new), Size of downloads: 0 KiB
pigface / #
|
I am going to try running emerge --depclean and emerge @preserved-rebuild again and see how I get on.
Cheers
MF
PS
I ran emerge binutils.
Here is the output:
/code | Code: | pigface / # emerge binutils
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 3) dev-tcltk/expect-5.45.4::gentoo
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
* expect5.45.4.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking expect5.45.4.tar.gz to /var/tmp/portage/dev-tcltk/expect-5.45.4/work
>>> Source unpacked in /var/tmp/portage/dev-tcltk/expect-5.45.4/work
>>> Preparing source in /var/tmp/portage/dev-tcltk/expect-5.45.4/work/expect5.45.4 ...
* Applying expect-5.45.4-examples.patch ... [ ok ]
* Applying expect-5.45-gfbsd.patch ... [ ok ]
* Applying expect-5.44.1.15-ldflags.patch ... [ ok ]
* Applying expect-5.45-headers.patch ... [ ok ]
* Applying expect-5.45-format-security.patch ... [ ok ]
* Running 'autoconf' ... [ !! ]
* Failed running 'autoconf'!
*
* Include in your bug report the contents of:
*
* /var/tmp/portage/dev-tcltk/expect-5.45.4/temp/autoconf.out
* ERROR: dev-tcltk/expect-5.45.4::gentoo failed (prepare phase):
* Failed running 'autoconf'!
*
* Call stack:
* ebuild.sh, line 127: Called src_prepare
* environment, line 2414: Called eautoconf
* environment, line 792: Called autotools_run_tool '--at-m4flags' 'autoconf'
* environment, line 568: Called die
* The specific snippet of code:
* die "Failed running '${1}'!";
*
* If you need support, post the output of `emerge --info '=dev-tcltk/expect-5.45.4::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-tcltk/expect-5.45.4::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-tcltk/expect-5.45.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-tcltk/expect-5.45.4/temp/environment'.
* Working directory: '/var/tmp/portage/dev-tcltk/expect-5.45.4/work/expect5.45.4'
* S: '/var/tmp/portage/dev-tcltk/expect-5.45.4/work/expect5.45.4'
>>> Failed to emerge dev-tcltk/expect-5.45.4, Log file:
>>> '/var/tmp/portage/dev-tcltk/expect-5.45.4/temp/build.log'
* Messages for package dev-tcltk/expect-5.45.4:
* Failed running 'autoconf'!
*
* Include in your bug report the contents of:
*
* /var/tmp/portage/dev-tcltk/expect-5.45.4/temp/autoconf.out
* ERROR: dev-tcltk/expect-5.45.4::gentoo failed (prepare phase):
* Failed running 'autoconf'!
*
* Call stack:
* ebuild.sh, line 127: Called src_prepare
* environment, line 2414: Called eautoconf
* environment, line 792: Called autotools_run_tool '--at-m4flags' 'autoconf'
* environment, line 568: Called die
* The specific snippet of code:
* die "Failed running '${1}'!";
*
* If you need support, post the output of `emerge --info '=dev-tcltk/expect-5.45.4::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-tcltk/expect-5.45.4::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-tcltk/expect-5.45.4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-tcltk/expect-5.45.4/temp/environment'.
* Working directory: '/var/tmp/portage/dev-tcltk/expect-5.45.4/work/expect5.45.4'
* S: '/var/tmp/portage/dev-tcltk/expect-5.45.4/work/expect5.45.4'
pigface / # |
The build log file is here:
http://dpaste.com/EENYRNMNK
Regards
MF
The autoconf.out log file is here:
http://dpaste.com/85UFWXE5K
I tried emerging but got a circular dependency problem again.
The screen output is here:
https://paste.debian.net/1226714/ |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2266
|
| Posted: Tue Jan 11, 2022 1:54 pm Post subject: |
|
|
| mikefot wrote: | I had problems with conflicting dependencies etc in world updates and so I removed a lot of
packages to try to fix the problem.
|
Unfortunately, you've now broken the building toolchain. binutils is critical to compiling any package, even itself.
This is why we say not use --unmerge (-C) at all unless instructed to. It leads to nothing but headaches.
Time to get a binpkg from another machine for binutils and other things.
Edit: chrooting into a new stage3 and using 'quickpkg --include-config=y binutils' and the like to place into the broken install is also an option |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Tue Jan 11, 2022 6:52 pm Post subject: |
|
|
Many thanks for your help again.
Out of interest, if I would use the gentoo installation dvd (or put it on a usb stick and boot from it etc), could you use it to
chroot into my existing install and then run the command you suggested without crfeating new partitions and installing a new version of gentoo
using a stage3 tarball?
What I mean is that the installation dvd presumably runs on gentoo and likely has its own binutils binary in it anyway.......
So is there a way to run | Code: | | quickpkg --include-config=y binutils |
on the dvd install itself and then park the binutils binary in my broken system?
Comments appreciated.
Regards
MF |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 2266
|
| Posted: Tue Jan 11, 2022 7:07 pm Post subject: |
|
|
| mikefot wrote: | Many thanks for your help again.
Out of interest, if I would use the gentoo installation dvd (or put it on a usb stick and boot from it etc), could you use it to
chroot into my existing install and then run the command you suggested without crfeating new partitions and installing a new version of gentoo
using a stage3 tarball?
What I mean is that the installation dvd presumably runs on gentoo and likely has its own binutils binary in it anyway.......
So is there a way to run | Code: | | quickpkg --include-config=y binutils |
on the dvd install itself and then park the binutils binary in my broken system?
Comments appreciated.
Regards
MF |
You don't need an ISO to get a chroot going. Just use the "broken" install to unpack a stage3 to a directory, mount proc, sys and dev and chroot into it.
You need to quickpkg all of binutils and its deps (see above output from emerge) as well as dev-lang/perl which is crucial for autotools to work.
Then put them in the PKGDIR (output of 'portageq pkgdir') and then use the --binpkgonly and --oneshot flags to emerge.
Edit: On second thought, you may still need one since you broke xz as well unless busybox still exists on that system for 'busybox xz'. But the point is that you don't need new partitions. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 709
|
| Posted: Tue Jan 11, 2022 7:43 pm Post subject: |
|
|
Many thanks again for your helpful response.
You are right. I have broken the xz utility as well.
So using the ISO can help me here.
If I would use it, after chrooting into my broken install what would be the
best commands to run then?
e.g. (using the ISO)
| Code: | quickpkg --include-config=y binutils
quickpkg --include-config=y dev-lang/perl |
Then go into the PKGDIR directory.
Then run
| Code: | | emerge --binpkgonly --oneshot binutils |
Would that do it?
Cheers
MF |
|
| 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
|
|
Portage & Programming
