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
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 c
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-
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
checki
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 critic
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.
6 matches
Mail list logo
