[gentoo-user] updating glibc-2.3.5-r2: segmentation fault...

[gentoo-user] updating glibc-2.3.5-r2: segmentation fault...

[Jarry]

Hi,

I changed my USE flags (added "hardened hardenedphp lm_sensors)
and tried "emerge --update --deep --newuse world". Emerge wanted
to recompile 8 packages, but crushed during the second one
(glibc) with segmentation fault:
__________________________________________________________
/work/build-default-i686-pc-linux-gnu-linuxthreads/libc.so
/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/libc_nonshared.a
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld: BFD
2.16.1 assertion fail
/var/tmp/portage/binutils-2.16.1/work/binutils-2.16.1/bfd/elflink.c:2322
make[2]: ***
[/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/iconvdata/IBM891.so]
Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconvdata'
make[1]: *** [iconvdata/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
make: *** [all] Error 2

!!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
!!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
!!! (no error message)
______________________________________________________________

How can I fix it? Which of those 3 new USE flags could cause it?

Jarry

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Jarry]

Jarry wrote:

> I changed my USE flags (added "hardened hardenedphp lm_sensors)
> and tried "emerge --update --deep --newuse world". Emerge wanted
> to recompile 8 packages, but crushed during the second one
> (glibc) with segmentation fault:
> __________________________________________________________
> /work/build-default-i686-pc-linux-gnu-linuxthreads/libc.so
> /var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/libc_nonshared.a
> collect2: ld terminated with signal 11 [Segmentation fault]
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld: BFD
> 2.16.1 assertion fail
> /var/tmp/portage/binutils-2.16.1/work/binutils-2.16.1/bfd/elflink.c:2322
> make[2]: ***
> [/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/iconvdata/IBM891.so]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory
> `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconvdata'
> make[1]: *** [iconvdata/others] Error 2
> make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
> make: *** [all] Error 2
> 
> !!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
> !!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
> !!! (no error message)
> ______________________________________________________________


Show must go on. I removed those use-flags (hardened, hardenedphp
and lm_sensors), and tried to put my system to previous clean state
with "emerge --update --deep --newuse world". Now only 1 package has
to be recompiled: gcc-3.4.4-r1, but it fails with following error:
___________________________________________________________________
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c: In function
`psignal':
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:563: error:
argument "signo" doesn't match prototype
/usr/include/signal.h:141: error: prototype declaration
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:563: error:
argument "message" doesn't match prototype
/usr/include/signal.h:141: error: prototype declaration
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:568: warning:
comparison between signed and unsigned
make[1]: *** [strsignal.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/libiberty'
make: *** [all-libiberty] Error 2

!!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
!!! Function gcc_do_make, Line 1339, Exitcode 2
!!! emake failed with profiledbootstrap
____________________________________________________________________

Frankly, I really have no idea what to do now. If I include those flags
(hardened, hardenedphp and lm_sensors), compilation of glibc-2.3.5-r2
fails because of some segmentation error.

If I remove those use-flags, compilation of gcc-3.4.4-r1 fails because
of some other error. Does anybody have any idea how to get out of this
"circulus vitiosus"? Any tips would be really appreciated and welcomed...

Jarry

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Rumen Yotov]

[-- Attachment #1: Type: text/plain, Size: 3758 bytes --]

On Wed, 2006-02-15 at 20:16 +0100, Jarry wrote:
> Jarry wrote:
> 
> > I changed my USE flags (added "hardened hardenedphp lm_sensors)
> > and tried "emerge --update --deep --newuse world". Emerge wanted
> > to recompile 8 packages, but crushed during the second one
> > (glibc) with segmentation fault:
> > __________________________________________________________
> > /work/build-default-i686-pc-linux-gnu-linuxthreads/libc.so
> > /var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/libc_nonshared.a
> > collect2: ld terminated with signal 11 [Segmentation fault]
> > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld: BFD
> > 2.16.1 assertion fail
> > /var/tmp/portage/binutils-2.16.1/work/binutils-2.16.1/bfd/elflink.c:2322
> > make[2]: ***
> > [/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/iconvdata/IBM891.so]
> > Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > make[2]: Leaving directory
> > `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconvdata'
> > make[1]: *** [iconvdata/others] Error 2
> > make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
> > make: *** [all] Error 2
> > 
> > !!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
> > !!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
> > !!! (no error message)
> > ______________________________________________________________
> 
> 
> Show must go on. I removed those use-flags (hardened, hardenedphp
> and lm_sensors), and tried to put my system to previous clean state
> with "emerge --update --deep --newuse world". Now only 1 package has
> to be recompiled: gcc-3.4.4-r1, but it fails with following error:
> ___________________________________________________________________
> /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c: In function
> `psignal':
> /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:563: error:
> argument "signo" doesn't match prototype
> /usr/include/signal.h:141: error: prototype declaration
> /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:563: error:
> argument "message" doesn't match prototype
> /usr/include/signal.h:141: error: prototype declaration
> /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/libiberty/strsignal.c:568: warning:
> comparison between signed and unsigned
> make[1]: *** [strsignal.o] Error 1
> make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/libiberty'
> make: *** [all-libiberty] Error 2
> 
> !!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
> !!! Function gcc_do_make, Line 1339, Exitcode 2
> !!! emake failed with profiledbootstrap
> ____________________________________________________________________
> 
> Frankly, I really have no idea what to do now. If I include those flags
> (hardened, hardenedphp and lm_sensors), compilation of glibc-2.3.5-r2
> fails because of some segmentation error.
> 
> If I remove those use-flags, compilation of gcc-3.4.4-r1 fails because
> of some other error. Does anybody have any idea how to get out of this
> "circulus vitiosus"? Any tips would be really appreciated and welcomed...
> 
> Jarry
> 
Hi,
You shouldn't have used "hardened" unless you running a hardened system.
Could be done via (hardened + pic IIRC) using normal system profile or
w/o any special USE-flags, when using a "hardened" profile.
Check the output of: gcc-config -l (what profile is GCC using) and
switch to vanilla. Hope your toolchain isn't recompiled too.
IIRC 'hardened-php' isn't part of a real "hardened" system (you must be
using a hardened kernel too - hardened|selinux|rsbac-sources) it's only
a hardening patch for PHP.
HTH.Rumen

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3409 bytes --]

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Jarry]

Rumen Yotov wrote:

> You shouldn't have used "hardened" unless you running a hardened system.

Now I know, but I think it is too late. I wanted to switch to hardened,
so I thought I have to add those flag first, and update the whole system.
I did not thought it would end by reinstalling the system again...

> Check the output of: gcc-config -l (what profile is GCC using) and

obelix ~ # gcc-config -l
 [1] i686-pc-linux-gnu-3.4.4 *
 [2] i686-pc-linux-gnu-3.4.4-hardenednopie
 [3] i686-pc-linux-gnu-3.4.4-hardenednopiessp
 [4] i686-pc-linux-gnu-3.4.4-hardenednossp
 [5] i686-pc-linux-gnu-3.4.4-vanilla

> switch to vanilla. Hope your toolchain isn't recompiled too.

All I know is that I'm pretty stuck: with those hardened flags or
without them, I can not fix my system...

Jarry

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Rumen Yotov]

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Hi again,
On Wed, 2006-02-15 at 22:06 +0100, Jarry wrote:
> Rumen Yotov wrote:
> 
> > You shouldn't have used "hardened" unless you running a hardened system.
> 
> Now I know, but I think it is too late. I wanted to switch to hardened,
> so I thought I have to add those flag first, and update the whole system.
> I did not thought it would end by reinstalling the system again...
> 
> > Check the output of: gcc-config -l (what profile is GCC using) and
> 
> obelix ~ # gcc-config -l
>  [1] i686-pc-linux-gnu-3.4.4 *
>  [2] i686-pc-linux-gnu-3.4.4-hardenednopie
>  [3] i686-pc-linux-gnu-3.4.4-hardenednopiessp
>  [4] i686-pc-linux-gnu-3.4.4-hardenednossp
>  [5] i686-pc-linux-gnu-3.4.4-vanilla
> 
> > switch to vanilla. Hope your toolchain isn't recompiled too.
> 
Now run: "gcc-config 5" and check again with gcc-config -l that vanilla
is your default gcc profile.
> All I know is that I'm pretty stuck: with those hardened flags or
> without them, I can not fix my system...
> 
> Jarry
> 
Next try re-emerging GCC-3.4.4.
HTH.Rumen

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3409 bytes --]

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Jarry]

Rumen Yotov wrote:

> Now run: "gcc-config 5" and check again with gcc-config -l that vanilla
> is your default gcc profile.
> 
> Next try re-emerging GCC-3.4.4.

I tried. Changed to vanilla, verified, started re-emerging gcc, but it
failed without saying anything (frozen, after 4 hours of nothing-doing
I interrupted it). Then I tried "emerge --sync", that crushed too:

>>> Updating Portage cache:   52%Segmentation fault

I repeated it 3x, always the same: at 52% segfault. Seems my system
is pretty broken. I really did not know that just adding two use-flags
(hardened hardenedphp) can be so dangerous, even on "stable-only" system.
It seems I will spend one more nice weekend by reinstalling...   :-(

Jarry

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Rumen Yotov]

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

On Thu, 2006-02-16 at 19:25 +0100, Jarry wrote:
> Rumen Yotov wrote:
> 
> > Now run: "gcc-config 5" and check again with gcc-config -l that vanilla
> > is your default gcc profile.
> > 
> > Next try re-emerging GCC-3.4.4.
> 
> I tried. Changed to vanilla, verified, started re-emerging gcc, but it
> failed without saying anything (frozen, after 4 hours of nothing-doing
> I interrupted it). Then I tried "emerge --sync", that crushed too:
> 
> >>> Updating Portage cache:   52%Segmentation fault
> 
> I repeated it 3x, always the same: at 52% segfault. Seems my system
> is pretty broken. I really did not know that just adding two use-flags
> (hardened hardenedphp) can be so dangerous, even on "stable-only" system.
> It seems I will spend one more nice weekend by reinstalling...   :-(
> 
> Jarry
> 
Hi,
Have you compiled anything after compiling GCC with 'hardened'? (genlop)
Try with MAKEOPTS="-j1" in /etc/make.conf but not much hope.
Or better boot with install-CD chroot into your existing installation
and remerge GCC with sane CFLAGS. Quicker than complete reinstall.
Or check/search for a binary package for your arch & flags (not easy).
PS:first try recompiling the toolchain in that order:binutils,gcc,glibc.
HTH.Rumen

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3409 bytes --]

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Jarry]

Rumen Yotov wrote:

> Have you compiled anything after compiling GCC with 'hardened'? (genlop)

Negative, only gcc, then emerge failed trying to compile 2nd package -
glibc-2.3.5-r2. I tried to go back (removed those hardened-flags), and
could not compile gcc-3.4.4

> Try with MAKEOPTS="-j1" in /etc/make.conf but not much hope.

I do not know why, but it helped! I changed it from -j2 to -j1, and
emerge gcc without any problem! Then I switched back to -j2 and updated
my whole system without a problem:

emerge --update --deep --newuse world

Thanks a lot, man!

So now (I hope!) my system is in consistent state, as it was before
my little "experiment" with "hardened" and "hardenedphp" flags.
With one exception. When I now check:

 gcc-config -l
 [1] i686-pc-linux-gnu-3.4.4 *
 [2] i686-pc-linux-gnu-3.4.4-hardened
 [3] i686-pc-linux-gnu-3.4.4-hardenednopie
 [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.4-hardenednossp

Previously it was:
[1] i686-pc-linux-gnu-3.4.4 *
[2] i686-pc-linux-gnu-3.4.4-hardenednopie
[3] i686-pc-linux-gnu-3.4.4-hardenednopiessp
[4] i686-pc-linux-gnu-3.4.4-hardenednossp
[5] i686-pc-linux-gnu-3.4.4-vanilla

Do I have to make worry about that missing vanilla-profile?

Jarry

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Benno Schulenberg]

Jarry wrote:
> So now (I hope!) my system is in consistent state, as it was
> before my little "experiment" 

Well, you have had a kernel oops, and it looks like you may have had 
another (the emerge of gcc that did nothing for 4 hours), so... 
something doesn't seem quite right.  Keep watching your logs.

> With one exception. When I now check:
>
>  gcc-config -l
>  [1] i686-pc-linux-gnu-3.4.4 *
>  [2] i686-pc-linux-gnu-3.4.4-hardened
>  [3] i686-pc-linux-gnu-3.4.4-hardenednopie
>  [4] i686-pc-linux-gnu-3.4.4-hardenednopiessp
>  [5] i686-pc-linux-gnu-3.4.4-hardenednossp
>
> Previously it was:
> [1] i686-pc-linux-gnu-3.4.4 *
> [2] i686-pc-linux-gnu-3.4.4-hardenednopie
> [3] i686-pc-linux-gnu-3.4.4-hardenednopiessp
> [4] i686-pc-linux-gnu-3.4.4-hardenednossp
> [5] i686-pc-linux-gnu-3.4.4-vanilla
>
> Do I have to make worry about that missing vanilla-profile?

No.  Look closer: when using the "hardened" flag, the default 
compiler is the hardened one, when not using that flag, the default 
compiler is the vanilla one.

Benno
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)

[Benno Schulenberg]

Jarry wrote:
> Rumen Yotov wrote:
> > switch to vanilla. Hope your toolchain isn't recompiled too.
>
> All I know is that I'm pretty stuck: with those hardened flags or
> without them, I can not fix my system...

You have tried switching to the vanilla compiler?  (gcc-config 5, in 
your case)  Have you set your CFLAGS to absolute dead plain?  
(-march=... -O2 -pipe)  Have you tried emerging an older compiler?  
(gcc-3.3.6, for example, and use that one to recompile 3.4.4)

Benno
-- 
gentoo-user@gentoo.org mailing list