Re: [gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
Nikos Chantziaras wrote: > > "as" is part of binutils, not gcc. binutils is a critical package, so > you shouldn't have downgraded glibc. Ups :-( Ok, I got the system (nearly) running again by copying /lib and /usr/lib from another working system, and copying the /usr/i686-pc-linux-gnu/binutils-bin directory (which was called "i486..." instead of "i686..." on the other system, generating some "not found" errors). Apache, Postfix, Bind and all that were running again then; leaving some Perl-related problems only (mailgraph/rrdtool, spamassassin...). Tried "perl-cleaner --reallyall", went until >>> Emerging (53 of 60) dev-python/subunit-1.2.0-r1::gentoo and then changing mode of /var/tmp/portage/dev-python/subunit-1.2.0-r1/work/subunit-1.2.0-abi_x86_32.x86-python2_7/scripts/subunit2junitxml from 644 to 755 changing mode of /var/tmp/portage/dev-python/subunit-1.2.0-r1/work/subunit-1.2.0-abi_x86_32.x86-python2_7/scripts/subunit2pyunit from 644 to 755 changing mode of /var/tmp/portage/dev-python/subunit-1.2.0-r1/work/subunit-1.2.0-abi_x86_32.x86-python2_7/scripts/tap2subunit from 644 to 755 * python3_5: running distutils-r1_run_phase distutils-r1_python_compile python3.5 setup.py build python3.5: error while loading shared libraries: libpython3.5m.so.1.0: cannot open shared object file: No such file or directory * ERROR: dev-python/subunit-1.2.0-r1::gentoo failed (compile phase): * (no error message) Don't really know why *perl* need *python* :-) Ok, libpython3.5m.so.1.0 is only in /usr/lib228 (the /usr/lib directory which I saved while glibc 2.28 was installed); in /usr/lib, there is only libpython2.7 and 3.6... will reinstall python now first... hope it works. Busy weekend this time :-( -Matt
Re: [gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
Matthias Hanft wrote: >> > I *do* have another working Gentoo system (with the old glibc 2.27 and > Apache 2.4.38 and all binutils and all that - everything is still fine > there). Can I use this just to copy some files (libs) to the "sick" > system? Just until I can re-emerge everything into a consistent state > there? I now have copied /lib and /usr/lib from the other system to the "sick" system (and made a backup copy of the glibc-228 /lib and /usr/lib, of course). Now it works "a little bit" more than before, but it's still inconsistent, for example # rndc reload rndc: error while loading shared libraries: libisccfg.so.1203: cannot open shared object file: No such file or directory libisccfg.so seems to be a part of the bind package, but I still cannot emerge anything because "C compiler not working". A simple test: $ gcc -o hello hello.c In file included from hello.c:3: /usr/include/stdio.h: In function 'main': /usr/include/stdio.h:33:10: fatal error: stddef.h: No such file or directory #include ^~ compilation terminated. stddef.h is in /usr/include/linux, but is it obviously not found. Do I have *any* chance to get this system working again? Meanwhile, I would find it great to get a working system even *without* Apache! I have made a "quickpkg" out of glibc 2.28 before downgrading to 2.27. Can I just untar it and have my 2.28 libraries again (any everything except Apache will run)? Or what's the best I can do? (Without installing everything from scratch...) -Matt
[gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
On 13/04/2019 17:38, Matthias Hanft wrote: Despite gcc was *not* recompiled after the glibc upgrade, it now tells $ gcc -o hello hello.c /usr/lib/gcc/i686-pc-linux-gnu/8.2.0/../../../../i686-pc-linux-gnu/bin/as: /lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/binutils/i686-pc-linux-gnu/2.31.1/libbfd-2.31.1.gentoo-sys-devel-binutils-st.so) Argh!!! "as" is part of binutils, not gcc. binutils is a critical package, so you shouldn't have downgraded glibc. However, you can try to "quickpgk --include-config y binutils" in another system and copy the packages directory over to the current one. Then "emerge -a1K binutils" to emerge from the binary package.
Re: [gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
Matthias Hanft wrote: > > So it seems that I cannot emerge "patch" because I need to patch > "patch" :-( Am I stuck now??? What to do?? I copied "/usr/bin/patch" from another (glibc-2.27) Gentoo system. Patching now works, but at every emerge (for example, binutils), I get something like checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking whether the C compiler works... no configure: error: in `/var/tmp/portage/sys-devel/patch-2.7.6-r3/work/patch-2.7.6': configure: error: C compiler cannot create executables See `config.log' for more details Despite gcc was *not* recompiled after the glibc upgrade, it now tells $ gcc -o hello hello.c /usr/lib/gcc/i686-pc-linux-gnu/8.2.0/../../../../i686-pc-linux-gnu/bin/as: /lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/binutils/i686-pc-linux-gnu/2.31.1/libbfd-2.31.1.gentoo-sys-devel-binutils-st.so) Argh!!! I *do* have another working Gentoo system (with the old glibc 2.27 and Apache 2.4.38 and all binutils and all that - everything is still fine there). Can I use this just to copy some files (libs) to the "sick" system? Just until I can re-emerge everything into a consistent state there? -Matt
Re: [gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
Nikos Chantziaras schrieb: > > See which packages were built against the new glib. Do: >$ qlop -l -d 2days > See which packages were emerged AFTER glibc 2.28. Are they critical > packages? If not, downgrade glibc anyway. Then rebuild those packages. I didn't consider those packages as critical (gcc was *not* built after the glibc upgrade!), so I succeeded to downgrade glibc at last. But now "emerge -1 apache" doesn't work because "patch" is needed, and "patch" is still looking for glibc 2.28. And "emerge -1 patch" seems to need the new glibc anyway: * patch-2.7.6.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking patch-2.7.6.tar.xz to >>> /var/tmp/portage/sys-devel/patch-2.7.6-r3/work >>> Source unpacked in /var/tmp/portage/sys-devel/patch-2.7.6-r3/work >>> Preparing source in >>> /var/tmp/portage/sys-devel/patch-2.7.6-r3/work/patch-2.7.6 ... * Applying patch-2.7.6-fix-test-suite.patch ... patch: /lib/libc.so.6: version `GLIBC_2.28' not found (required by patch) [ !! ] * ERROR: sys-devel/patch-2.7.6-r3::gentoo failed (prepare phase): * patch -p1 failed with /var/tmp/portage/sys-devel/patch-2.7.6-r3/files/patch-2.7.6-fix-test-suite.patch So it seems that I cannot emerge "patch" because I need to patch "patch" :-( Am I stuck now??? What to do?? -Matt
[gentoo-user] Re: Apache not starting after upgrading Apache/glibc...
On 13/04/2019 15:20, Matthias Hanft wrote: Now "admin-panic" is heavily arising. HELP! What can I do?? See which packages were built against the new glib. Do: $ qlop -l -d 2days See which packages were emerged AFTER glibc 2.28. Are they critical packages? If not, downgrade glibc anyway. Then rebuild those packages. I forgot how to downgrade glibc though :-/ Years ago, this happened to me. After than, I *NEVER* allow new versions of glibc to be emerged together with other packages. I always exclude it, let everything else update, then I make a binary package of glibc (quickpkg glibc) and only then do I emerge the new glibc so I can downgrade again from the binary package (but again, I forgot how to do that now...)
