On Fri, Jun 23, 2006 at 11:43:39PM +0200, Felix Breuer wrote: > > The problem still surprises me, since *I* linked statically against Guile. > > In principle, this should precisely avoid problems of the kind you noticed. > > Could it be that TeXmacs somehow attempts to use the Guile which is > > on your system? Is there some active $GUILE_LOAD_PATH? > > There is no $GUILE_LOAD_PATH on any of the systems I tested on. > > I am quite puzzled myself. All I can do is make a wild guess: the > statically linked Guile tries to use the libc version on my system. My > libc is compiled with TLS support and for some reason Guile cannot > handle libc w/ TLS if it is statically linked. ./configure knows this > and issues a warning, that it won't be able to link Guile statically > (because I am running a libc w/ TLS).
But why would it use your libc? Isn't libc linked statically with the rest? > Maybe your libc is compiled --without-tls? What platform are you working > on? Redhat 9.0. I never recompiled libc myself (although I did compile my own version of gcc-2.95.3, which continues being better than g++-4.1.*). _______________________________________________ Texmacs-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/texmacs-dev
