mod_php-4.3.0-r1 builds successfully, but the PEAR installer segfaults. My
CFLAGS are the usual, mcpu/mtune = ultrasparc, -O3, -pipe, and -fomit-frame-pointer.
[root@isengard mod_php]# ebuild mod_php-4.3.0-r1.ebuild install
>>> md5 ;-) php-4.3.0.tar.bz2
>>> Checking php-4.3.0.tar.bz2's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that mod_php is already compiled; skipping.
>>> (clean to force compilation)
>>> Install mod_php-4.3.0-r1 into /usr/obj/portage/mod_php-4.3.0-r1/image/
Installing PEAR environment:
make: *** [install-pear-installer] Segmentation fault
make: *** [install-pear] Error 2
!!! ERROR: dev-php/mod_php-4.3.0-r1 failed.
!!! Function src_install, Line 211, Exitcode 2
!!! (no error message)
I tried merging an ebuild off the forums, and that too segfaulted, with no valid
information as to why. So I decided to un-prelink everything and remove ccache
on my system. I figure with prelink, I'll wait until the elfutils option is
fixed and merge the newer prelink toolset before using that again. Lo and
behold, mod_php-4.3.0-r1 merges fine.
So it seems more testing may need to be done with either ccache and/or prelink.
Maybe it was the older prelink tools causing the problem, I dunno. More input
if I discover anything else of relevance.
This is due to LD_PRELOAD being used with prelinking, a very unstable
combination. You are right this is prelink's fault.
prelink your system and use portage-2.0.47, does that fix it?
Also does it fail if you emerge it with -sandbox in your FEATURES or if you
build it manually?
Well, I was using the older prelink ebuild that used libelf. The newest prelink
requires elfutils, and elfutils hasn't compiled properly on my sparc system due
to -Werror being passed to GCC, and thus, warnings killing off the build.
Comments in the elfutils bugreport include information for stripping out
-Werror, and I will attempt that patch after attempting elfutils by itself, as a
newer post states the ebuild is updated, which may indicate the original problem
If elfutils works properly, I will merge the newest prelink and prelink my
system. as for testing mod_php-4.3.0--r1, I already installed it after removing
prelink, but I can rebuild it again to verify.
This error is indeed linked to prelink. It appears prelink is not 100%
functional yet on sparc, so I plan to keep it uninstalled for the time being.
This pretty much resolves this bug, but an eye should be kept open for other
similar errors that may be related to prelink.
Prelink issue with mod_php on some platforms.