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
