I run a ~x86 system, most things compiled with gcc-3.4.
Recently I've emerged a new version of p7zip and it segfaults every
time I try to run it.
I looked at the makefile and saw that p7zip was statically linked (-static).
So I tried to compile it dynamically (w/o -static) and ... bam! , it works.
The makefile shows its linked only againts threads library.
I've got glibc compiled with nptlonly USE flag.
What could this segfault possibly mean?
Im trying to get the darn thing compiled with debug symbols but no
luck so far ...
The source is pretty strange, and I'm no guru over here.
PS: Shouldn't the ebuild make use of the 'static' USE flag anyway?
--
Regards
Karol Krzak
--
gentoo-user@gentoo.org mailing list
Recently I've emerged a new version of p7zip and it segfaults every
time I try to run it.
I looked at the makefile and saw that p7zip was statically linked (-static).
So I tried to compile it dynamically (w/o -static) and ... bam! , it works.
The makefile shows its linked only againts threads library.
I've got glibc compiled with nptlonly USE flag.
What could this segfault possibly mean?
Im trying to get the darn thing compiled with debug symbols but no
luck so far ...
The source is pretty strange, and I'm no guru over here.
PS: Shouldn't the ebuild make use of the 'static' USE flag anyway?
--
Regards
Karol Krzak
--
gentoo-user@gentoo.org mailing list