The above mentioned ebuild results in grep being unusable. Once installed, all subsequent builds will fail on a hardened, pax enabled system, since grep is called by any configure script Reproducible: Always Steps to Reproduce: 1. emerge sys-apps/grep-2.5.3-r1 2. run grep Actual Results: "grep: error while loading shared libraries: cannot make segment writable for relocation: Permission denied" paxctl -m /usr/bin/grep makes grep usable again. /bin/fgrep and /bin/egrep are not affected by this bug.
Sorry, should read: paxctl -m /bin/grep makes grep usable again
emerge --info please.
Can you try to use the stable version of grep?
(In reply to comment #3) > Can you try to use the stable version of grep? > I have difficulties to reproduce the situation at all, after I somehow lost the gcc-4.3.2 p1.1 from xake toolchain. When I re-emerged this version, and then re-emerged grep, the problem was gone. However, if you look at the grep makefile and sources, you would not wonder that it could trigger such instabilities (egrep and fgrep ok, but grep shows textrels). egrep and fgrep are one-line programs : #include "grep.c"
Soo uhh, yeah.
