Summary: | dev-lisp/lush-0.99 (libload "gsl/gsl") broken | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Philippe Trottier (RETIRED) <tchiwam> |
Component: | New packages | Assignee: | Gentoo Lisp Project <lisp> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2004.1 | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Philippe Trottier (RETIRED)
2004-06-28 10:39:11 UTC
We are trying to use gsl libraries with lush... but no success using the ebuilds... the same lush-0.99 compile from the tarball of lush.sf.net creates proper gsl-lush functions. Tried on those systems: Linux s1 2.6.4 #4 SMP Thu Mar 25 16:53:22 EET 2004 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux Linux flatdrum 2.6.7 #3 Mon Jun 21 17:24:45 EEST 2004 ppc 7450, altivec supported PowerBook3,3 GNU/Linux These have been tested on many ppc system, compiled all with gcc-3.3.4, started with 3.2.x, upgraded to 3.3.3 and then to 3.3.4 etc etc and all show a similar behavior. I was able to confim this problem. As a work around, you could try adding --without-bfd to the econf line in the ebuild such as follows: src_compile() { econf `use_with X X` \ --without-bfd \ || die "./configure failed" emake -j1 || die } (The above with use dlopen() etc. instead of libbfd) I built lush-0.99 /with/ BFD support outside of the emerge/ebuild environment and tried it with (libload "gsl/gsl") and it does function properly, so I suspect there is a problematic interaction with the sandbox library preloader. I have not investigated this further though. Same thing here, I just got the time to make one newer test. Since this tool is not anymore needed for us, I probably won't continue the follow up on this bug... It would be nice to fix it anyway as SANDBOX might be causing other not so easy to reproduce troubles while this one is systematic. added fix to lush-0.99 and added lush-1.0 with the same fix. |