| Summary: | eix gives a sigsegv while i'm trying to search for anything | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Maxim Chugunov <trogwar> |
| Component: | Third-Party Tools | Assignee: | Martin Väth <martin> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Maxim Chugunov
2007-08-06 20:22:31 UTC
Can you try with the latest eix version please? it is already the latest version: ~ # eix -V eix 0.9.9 (gcc-3.4.6, i686-pc-linux-gnu) ~ # ls -al /etc/make.profile lrwxrwxrwx 1 root root 38 Aug 1 14:29 /etc/make.profile -> /usr/portage/profiles/hardened/x86/2.6 Also tried going up to 0.9.10 - same problem. Downgrading to 0.8.8 brought an interesting thing - update-eix fails for the same reason: sigsegv and you can't do anything. It would not update the cash.. *** This bug has been marked as a duplicate of bug 146300 *** though the solution of changing the CXXFLAGS (and CFLAGS) flags to -02 or -01 didn't work in my case. The only way does work is when i'm compiling with vanila gcc... server ~ # gcc-config -l [1] i686-pc-linux-gnu-3.4.6 [2] i686-pc-linux-gnu-3.4.6-hardenednopie [3] i686-pc-linux-gnu-3.4.6-hardenednopiessp [4] i686-pc-linux-gnu-3.4.6-hardenednossp [5] i686-pc-linux-gnu-3.4.6-vanilla * [6] i686-pc-linux-gnu-4.1.2 I installed gcc-3.4.6-r2 with USE=hardened and kept to receive sigsev with CXXFLAGS=''. This time it was not std::unique() (for which I had built a workaround) but std::sort() which randomly caused the error (not very reproducable). I will not try to debug this any further, because I am rather sure that it is the compiler/library which is broken and not eix: Probably the failing of std::unique() and std::sort() are only symptoms of some other compiler-internal bug. However, when setting "CXXFLAGS=-O2" the error vanishes. Therefore, I almost cannot believe: (In reply to comment #5) > though the solution of changing the CXXFLAGS (and CFLAGS) flags to -02 or -01 > didn't work in my case. Already the fact that CXXFLAGS="" although CFLAGS is set in your emerge --info is somewhat strange; are you sure that you wanted this? Maybe for some reason you have 'export CXXFLAGS=""' in your shell startup scripts which overrides the setting in /etc/make.conf? Or maybe you use only shell variables and have forgotten to "export CXXFLAGS"? Can you really see the text "-O2" in the compiler calls when you emerge eix? (In reply to comment #6) found the problem... in make.conf parameters from CFLAGS weren't passing down to CXXFLAGS probably due to change from "(" to "{" brackets: CXXFLAGS="${CFLAGS}" is the correct version. My bad there... After changing that it does compile fine with -02 Tried with -03 - works fine. I guess it was a problem of a simple brackets. My apologies for you having to spend time on this.. |
