Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

SOLVED: glibc woes

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
3 posts • Page 1 of 1
Author
Message
Atom2
Apprentice
Apprentice
Posts: 185
Joined: Mon Aug 01, 2011 9:16 am

SOLVED: glibc woes

  • Quote

Post by Atom2 » Mon Dec 25, 2017 9:04 pm

Hi Guys,
I am being faced with an issue during upgrading a system. Trying to do a world update I was given a warning about an issue with a multiple slot installation for zlib. I tried to rectify this with

Code: Select all

emerge --ask --verbose --update --deep --newuse --backtrack=30 --oneshot --usepkg =sys-libs/zlib-1.2.11-r1-1
and after confirmation it started the process - obviously after displaying the packages it wanted to upgrade as follows:

Code: Select all

These are the packages that would be merged, in order:

Calculating dependencies... done!
[binary  r  U  ] sys-libs/zlib-1.2.11-r1-1:0/1::gentoo [1.2.11:0/0::gentoo] USE="-minizip -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary   R    ] app-arch/bzip2-1.0.6-r8-2:0/1::gentoo [1.0.6-r8:0/0::gentoo] USE="-static -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary     U  ] dev-lang/python-exec-2.4.5-1:2::gentoo [2.4.4:2::gentoo] PYTHON_TARGETS="(jython2_7) (pypy) (pypy3) (python2_7) (python3_4) (python3_5) (python3_6)" 0 KiB
[binary     U  ] dev-db/mysql-init-scripts-2.2-r2-1::gentoo [2.1-r1::gentoo] 0 KiB
[binary   R    ] dev-libs/libffi-3.2.1-2::gentoo  USE="-debug -pax_kernel* -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary     U  ] sys-apps/sandbox-2.10-r4-1::gentoo [2.10-r3::gentoo] ABI_X86="(32) (64) (-x32)" 0 KiB
[binary     U  ] sys-process/procps-3.3.12-r1-1:0/5::gentoo [3.3.12:0/5::gentoo] USE="kill ncurses nls unicode (-elogind) -modern-top (-selinux) -static-libs -systemd {-test}" 0 KiB
[binary     U  ] sys-apps/file-5.32-1::gentoo [5.30::gentoo] USE="zlib -python -static-libs" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 (-pypy) -python3_4 -python3_5 -python3_6" 0 KiB
[binary     U  ] app-portage/portage-utils-0.64-1::gentoo [0.62::gentoo] USE="nls -static" 0 KiB
[binary  rR    ] media-libs/libpng-1.6.29-2:0/16::gentoo  USE="-apng (-neon) -static-libs" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse" 0 KiB
[binary     U  ] sys-apps/coreutils-8.28-r1-1::gentoo [8.25::gentoo] USE="acl nls (xattr) -caps -gmp -hostname -kill -multicall (-selinux) -static {-test%} -vanilla" 0 KiB
[binary     U  ] dev-libs/openssl-1.0.2n-1::gentoo [1.0.2k::gentoo] USE="asm sslv3 tls-heartbeat zlib -bindist -gmp -kerberos -rfc3779 -sctp -sslv2 -static-libs {-test} -vanilla" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)" 0 KiB
[binary  r  U  ] dev-libs/libxml2-2.9.6-1:2::gentoo [2.9.4-r1:2::gentoo] USE="ipv6 readline -debug -examples -icu -lzma -python -static-libs {-test}" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 -python3_4 -python3_5 -python3_6%" 0 KiB
[binary     U  ] app-arch/tar-1.29-r3-1::gentoo [1.29-r1::gentoo] USE="acl nls (xattr) -minimal (-selinux) -static" 0 KiB
[binary     U  ] net-misc/rsync-3.1.2-r2-1::gentoo [3.1.2::gentoo] USE="acl iconv ipv6 xattr -examples -static -stunnel" 0 KiB
[binary     U  ] sys-libs/pam-1.2.1-r2-1::gentoo [1.2.1::gentoo] USE="berkdb cracklib filecaps%* nls (pie) -audit -debug -nis (-selinux) {-test} (-vim-syntax%*)" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary     U  ] sys-auth/pambase-20150213-r1-1::gentoo [20150213::gentoo] USE="cracklib nullok sha512 -consolekit -debug (-elogind) -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -passwdqc -securetty (-selinux) -systemd" 0 KiB
[binary  r  U  ] net-misc/openssh-7.5_p1-r3-1::gentoo [7.5_p1-r1::gentoo] USE="hpn pam (pie) ssl -X -X509 -audit -bindist -debug -kerberos -ldap -ldns -libedit -libressl -livecd -sctp (-selinux) -skey -ssh1 -static {-test}" 0 KiB
[binary     U  ] dev-lang/perl-5.24.3-1:0/5.24::gentoo [5.24.1-r2:0/5.24::gentoo] USE="berkdb gdbm -debug -doc -ithreads" 0 KiB
[binary     U  ] virtual/perl-Test-Harness-3.360.100_rc-r2-1::gentoo [3.360.100_rc-r1::gentoo] 0 KiB
[binary     U  ] virtual/perl-File-Spec-3.630.100_rc-r2-1::gentoo [3.630.100_rc-r1::gentoo] 0 KiB
[binary     U  ] virtual/perl-Storable-2.560.100_rc-r2-1::gentoo [2.560.100_rc-r1::gentoo] 0 KiB
[binary     U  ] virtual/perl-Sys-Syslog-0.330.100_rc-r4-1::gentoo [0.330.100_rc-r3::gentoo] 0 KiB
[binary  r  U  ] dev-lang/python-2.7.14-r1-1:2.7::gentoo [2.7.12:2.7::gentoo] USE="gdbm hardened ipv6 ncurses readline ssl (threads) (wide-unicode) xml (-berkdb) -build -doc -examples -libressl -sqlite -tk -wininst" 0 KiB
[binary  N     ] dev-python/pyblake2-1.1.0-1::gentoo  PYTHON_TARGETS="python2_7 (-pypy) -python3_4 -python3_5 -python3_6" 0 KiB
[binary     U  ] sys-apps/portage-2.3.13-r1-1::gentoo [2.3.6::gentoo] USE="(ipc) native-extensions (xattr) -build -doc -epydoc (-selinux)" LINGUAS="-ru" PYTHON_TARGETS="python2_7 (-pypy) -python3_4 -python3_5 -python3_6" 0 KiB
[binary  r  U  ] dev-db/mysql-5.6.38-2:0/18::gentoo [5.6.36:0/18::gentoo] USE="openssl perl server -debug -embedded -extraengine -jemalloc -latin1 -libressl -numa% -profiling (-selinux) -static -static-libs -systemtap -tcmalloc {-test} -yassl" ABI_X86="(64) -32 (-x32)" 0 KiB
[binary     U  ] virtual/mysql-5.6-r9-1:0/18::gentoo [5.6-r6:0/18::gentoo] USE="server%* -embedded -static (-static-libs%)" ABI_X86="(-32%) (-64%*) (-x32%)" 0 KiB
[binary     U  ] app-editors/vim-core-8.0.1298-1::gentoo [8.0.0386::gentoo] USE="acl nls -minimal" 0 KiB
[binary     U  ] app-editors/vim-8.0.1298-1::gentoo [8.0.0386::gentoo] USE="acl nls -X -cscope -debug -gpm -lua -luajit -minimal -perl -python -racket -ruby (-selinux) -tcl -terminal% -vim-pager" PYTHON_SINGLE_TARGET="python2_7%* -python3_4% -python3_5% -python3_6%" PYTHON_TARGETS="python2_7 -python3_4 -python3_5 -python3_6" 0 KiB

Total: 30 packages (26 upgrades, 1 new, 3 reinstalls, 30 binaries), Size of downloads: 0 KiB

The following packages are causing rebuilds:

  (sys-libs/zlib-1.2.11-r1-1:0/1::gentoo, binary scheduled for merge) causes rebuilds for:
    (dev-lang/python-2.7.14-r1-1:2.7/2.7::gentoo, binary scheduled for merge)
    (dev-db/mysql-5.6.38-2:0/18::gentoo, binary scheduled for merge)
    (dev-libs/libxml2-2.9.6-1:2/2::gentoo, binary scheduled for merge)
    (net-misc/openssh-7.5_p1-r3-1:0/0::gentoo, binary scheduled for merge)
    (media-libs/libpng-1.6.29-2:0/16::gentoo, binary scheduled for merge)
  (app-arch/bzip2-1.0.6-r8-2:0/1::gentoo, binary scheduled for merge) causes rebuilds for:
    (dev-lang/python-2.7.14-r1-1:2.7/2.7::gentoo, binary scheduled for merge)

!!! The following installed packages are masked:
- sys-devel/binutils-2.28-r2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Michał Górny <mgorny@gentoo.org>, Andreas K. Hüttel <dilfridge@gentoo.org>,
# Matthias Maier <tamiko@gentoo.org> (21 May 2017)
# 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.

- sys-kernel/hardened-sources-4.8.17-r2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches

- sys-libs/glibc-2.23-r4::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
It happily installed a number of packages from my binary package host until it reached dev-libs/openssl, which failed:

Code: Select all

>>> Running pre-merge checks for sys-libs/pam-1.2.1-r2
 * pam-1.2.1-r2-1.xpak MD5 SHA1 size ;-) ...                             [ ok ]
>>> Running pre-merge checks for net-misc/openssh-7.5_p1-r3
 * openssh-7.5_p1-r3-1.xpak MD5 SHA1 size ;-) ...                        [ ok ]
>>> Running pre-merge checks for dev-db/mysql-5.6.38
 * mysql-5.6.38-2.xpak MD5 SHA1 size ;-) ...                             [ ok ]
>>> Emerging binary (1 of 30) sys-libs/zlib-1.2.11-r1::gentoo
>>> Installing (1 of 30) sys-libs/zlib-1.2.11-r1::gentoo
>>> Emerging binary (2 of 30) app-arch/bzip2-1.0.6-r8::gentoo
>>> Installing (2 of 30) app-arch/bzip2-1.0.6-r8::gentoo
>>> Emerging binary (3 of 30) dev-lang/python-exec-2.4.5::gentoo
>>> Installing (3 of 30) dev-lang/python-exec-2.4.5::gentoo
>>> Emerging binary (4 of 30) dev-db/mysql-init-scripts-2.2-r2::gentoo
>>> Installing (4 of 30) dev-db/mysql-init-scripts-2.2-r2::gentoo
>>> Emerging binary (5 of 30) dev-libs/libffi-3.2.1::gentoo
>>> Installing (5 of 30) dev-libs/libffi-3.2.1::gentoo
>>> Emerging binary (6 of 30) sys-apps/sandbox-2.10-r4::gentoo
>>> Installing (6 of 30) sys-apps/sandbox-2.10-r4::gentoo
>>> Emerging binary (7 of 30) sys-process/procps-3.3.12-r1::gentoo
>>> Installing (7 of 30) sys-process/procps-3.3.12-r1::gentoo
>>> Emerging binary (8 of 30) sys-apps/file-5.32::gentoo
>>> Installing (8 of 30) sys-apps/file-5.32::gentoo
>>> Emerging binary (9 of 30) app-portage/portage-utils-0.64::gentoo
>>> Installing (9 of 30) app-portage/portage-utils-0.64::gentoo
>>> Emerging binary (10 of 30) media-libs/libpng-1.6.29::gentoo
>>> Installing (10 of 30) media-libs/libpng-1.6.29::gentoo
>>> Emerging binary (11 of 30) sys-apps/coreutils-8.28-r1::gentoo
>>> Installing (11 of 30) sys-apps/coreutils-8.28-r1::gentoo
>>> Emerging binary (12 of 30) dev-libs/openssl-1.0.2n::gentoo
>>> Failed to emerge dev-libs/openssl-1.0.2n, Log file:
>>>  '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/build.log'
>>> Jobs: 11 of 30 complete, 1 failed               Load avg: 0.50, 0.28, 0.14
>>> Extracting info
 * Package:    dev-libs/openssl-1.0.2n
 * Repository: gentoo
 * USE:        cpu_flags_x86_sse2 abi_x86_64 amd64 tls-heartbeat zlib kernel_linux elibc_glibc sslv3 asm userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv)
 * ERROR: dev-libs/openssl-1.0.2n::gentoo failed (setup phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=dev-libs/openssl-1.0.2n::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.0.2n::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/openssl-1.0.2n/homedir'
 * S: '/var/tmp/portage/dev-libs/openssl-1.0.2n/work/openssl-1.0.2n'
mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv)
 * ERROR: dev-libs/openssl-1.0.2n::gentoo failed:
 *   error processing environment
 *
 * Call stack:
 *   misc-functions.sh, line 17:  Called source '/var/tmp/portage/._portage_reinstall_.yKYvmB/bin/ebuild.sh'
 *           ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=dev-libs/openssl-1.0.2n::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.0.2n::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/openssl-1.0.2n/homedir'
 * S: '/var/tmp/portage/dev-libs/openssl-1.0.2n/work/openssl-1.0.2n'

 * Messages for package dev-db/mysql-init-scripts-2.2-r2:

 * To use the mysql-s6 script, you need to install the optional sys-apps/s6 package.
 * If you wish to use s6 logging support, comment out the log-error setting in your my.cnf
 * Starting with version 10.1.8, MariaDB includes an improved systemd unit named mariadb.service
 * You should prefer that unit over this package's mysqld.service.

 * Messages for package sys-apps/coreutils-8.25:

 * ERROR: sys-apps/coreutils-8.25::gentoo failed (prerm phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/coreutils-8.25::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/coreutils-8.25::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/work/coreutils-8.25'
 * The 'postrm' phase of the 'sys-apps/coreutils-8.25' package has failed
 * with exit value 1.
 *
 * The problem occurred while executing the ebuild file named
 * 'coreutils-8.25.ebuild' located in the '/var/db/pkg/sys-
 * apps/coreutils-8.25' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
 * ERROR: sys-apps/coreutils-8.25::gentoo failed (postrm phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-apps/coreutils-8.25::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/coreutils-8.25::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/temp/environment'.
 * Working directory: '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/homedir'
 * S: '/var/tmp/portage/._unmerge_/sys-apps/coreutils-8.25/work/coreutils-8.25'

 * Messages for package sys-apps/coreutils-8.28-r1:

 * Make sure you run 'hash -r' in your active shells.
 * You should also re-source your shell settings for LS_COLORS
 *   changes, such as: source /etc/profile
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/openssl-1.0.2n:

 * ERROR: dev-libs/openssl-1.0.2n::gentoo failed (setup phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=dev-libs/openssl-1.0.2n::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.0.2n::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/openssl-1.0.2n/homedir'
 * S: '/var/tmp/portage/dev-libs/openssl-1.0.2n/work/openssl-1.0.2n'
 * ERROR: dev-libs/openssl-1.0.2n::gentoo failed:
 *   error processing environment
 *
 * Call stack:
 *   misc-functions.sh, line 17:  Called source '/var/tmp/portage/._portage_reinstall_.yKYvmB/bin/ebuild.sh'
 *           ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=dev-libs/openssl-1.0.2n::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.0.2n::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.0.2n/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/openssl-1.0.2n/homedir'
 * S: '/var/tmp/portage/dev-libs/openssl-1.0.2n/work/openssl-1.0.2n'

 * Regenerating GNU info directory index...
 * Processed 88 info files.
Now to me it looks as if the system requires version 2.25 of glibc (the currently installed version is sys-libs/glibc-2.23-r4) which is not yet installed where it says

Code: Select all

mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv)
Unfortunately trying to emerge this version of glibc also fails as follows:

Code: Select all

emerge --oneshot --ask =sys-libs/glibc-2.25-r9-1

These are the packages that would be merged, in order:

Calculating dependencies... done!
[binary     U  ] sys-libs/glibc-2.25-r9-1 [2.23-r4]

!!! The following installed packages are masked:
- sys-devel/binutils-2.28-r2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Michał Górny <mgorny@gentoo.org>, Andreas K. Hüttel <dilfridge@gentoo.org>,
# Matthias Maier <tamiko@gentoo.org> (21 May 2017)
# 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.

- sys-kernel/hardened-sources-4.8.17-r2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Anthony G. Basile <blueness@gentoo.org> (27 Aug 2017)
# Upstream is no longer providing public patches

- app-vim/pam-syntax-20060424::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Patrice Clement <monsieurp@gentoo.org> (19 Dec 2017)
# A slightly better syntax file for PAM configuration files is shipped with Vim
# since version 8.0. The one we package is old and out of date.
# Masked for removal in 30 days. See bug 578278.

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
>>> Running pre-merge checks for sys-libs/glibc-2.25-r9
 * glibc-2.25-r9-1.xpak MD5 SHA1 size ;-) ...                            [ ok ]
mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv)
 * ERROR: sys-libs/glibc-2.25-r9::gentoo failed (pretend phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.25-r9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.25-r9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.25-r9/homedir'
 * S: '/var/tmp/portage/sys-libs/glibc-2.25-r9/work/glibc-2.25'
mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv)
 * ERROR: sys-libs/glibc-2.25-r9::gentoo failed:
 *   error processing environment
 *
 * Call stack:
 *   misc-functions.sh, line 17:  Called source '/usr/lib/portage/python2.7/ebuild.sh'
 *           ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.25-r9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.25-r9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.25-r9/homedir'
 * S: '/var/tmp/portage/sys-libs/glibc-2.25-r9/work/glibc-2.25'

 * Messages for package sys-libs/glibc-2.25-r9:

 * ERROR: sys-libs/glibc-2.25-r9::gentoo failed (pretend phase):
 *   error processing environment
 *
 * Call stack:
 *   ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.25-r9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.25-r9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.25-r9/homedir'
 * S: '/var/tmp/portage/sys-libs/glibc-2.25-r9/work/glibc-2.25'
 * ERROR: sys-libs/glibc-2.25-r9::gentoo failed:
 *   error processing environment
 *
 * Call stack:
 *   misc-functions.sh, line 17:  Called source '/usr/lib/portage/python2.7/ebuild.sh'
 *           ebuild.sh, line 539:  Called die
 * The specific snippet of code:
 *      __preprocess_ebuild_env || \
 *              die "error processing environment"
 *
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.25-r9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.25-r9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.25-r9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.25-r9/homedir'
 * S: '/var/tmp/portage/sys-libs/glibc-2.25-r9/work/glibc-2.25'
I hope I have not manoeuvred the system into a deadlock situation with no escape. What's my best course of action resolving this situation?

Many thanks and regrads,

Atom2
Last edited by Atom2 on Mon Dec 25, 2017 10:37 pm, edited 1 time in total.
Top
NeddySeagoon
Administrator
Administrator
User avatar
Posts: 56104
Joined: Sat Jul 05, 2003 9:37 am
Location: 56N 3W

  • Quote

Post by NeddySeagoon » Mon Dec 25, 2017 9:59 pm

Atom2,

Code: Select all

mv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by mv) 
thats the minimum glibc required and glibc-2.25-r9 is marked stable.
I hope I have not manoeuvred the system into a deadlock situation with no escape.
If you can do that, I'll buy you a beer, several beers even :)

You probably can't use emerge at all now since it appears your mv command is broken.
You need a binary glibc-2.25-r9 and a way of installing it, probably without using portage.

Read Fix My Gentoo from end to end.
It sounds like you can build glibc-2.25-r9 elsewhere, so you can make your own binary tarball.
If not you can get it from here then apply the Install steps

Alternalely you can dowgrade coreutils

Code: Select all

$ equery b mv
 * Searching for mv ... 
sys-apps/coreutils-8.28-r1 (/bin/mv)
as its coreutils that provides mv.
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Top
Atom2
Apprentice
Apprentice
Posts: 185
Joined: Mon Aug 01, 2011 9:16 am

SOLVED: glibc woes

  • Quote

Post by Atom2 » Mon Dec 25, 2017 10:37 pm

NeddySeagoon,
first of all thanks for your quick reply.
NeddySeagoon wrote:
I hope I have not manoeuvred the system into a deadlock situation with no escape.
If you can do that, I'll buy you a beer, several beers even :)
There's no need to buy me a beer. With all the combined great knwoledge here, I was sure that there was a way out.
NeddySeagoon wrote:You probably can't use emerge at all now since it appears your mv command is broken.
You need a binary glibc-2.25-r9 and a way of installing it, probably without using portage.
That was my first thought as well, but it seemed not to work. So after I had posted my question, I sat down and thought for a moment and concluded as follows:

the mv binary was unable to do its job due to an incorrect library. So what if I used another mv command. My first idea was to fool the emerge command by using busybox's mv and portage's env directory to setup a bash function referring back to the busybox mv command instead which I assumed would then be used during the emerge command. That, unfortunately, however was a dead end.

So the other option that came to mind was, why not use the old mv command that refers back to the old glibc. So I copied the old mv command over from another system, renamed the new mv to mv.old and copied the old mv command instead into /bin (the rename of the new mv binary to mv.old had to be done with busybox' mv command obviously).

I then fired off emerge for glibc and it went further, but again choked with yet another command: This time it was the sort command. So I redid the same thing with sort (copied the old glibc aware sort binary from another system, renamed the new to sort.old and put the old in its place).

Up to the next emerge of glibc - and that went through without any issues. Finally, now that the new glibc was in place, I deleted the old mv and sort command and undid the rename from sort.old and mv.old to sort and mv respectively.

After that I was back in business. In any case, I'll keep your link Fix My Gentoo in mind. It appears to be good reading ...

Many thanks again for your support.

Best regards,

Atom2
Top
Post Reply

3 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic