On Thursday, February 19, 2015 at 1:22:12 PM UTC-8, Michael Orlitzky wrote: > > Libc was an extreme example -- gd/dvipng are more mundane. Sage ships a > gd spkg, and sage uses dvipng but doesn't ship an spkg for it. The > problem? dvipng links against gd. But since dvipng comes from my system, > it links against the system gd. When running within sage, we mangle > LD_LIBRARY_PATH to allow us to use all of our bundled libraries. As a > result, dvipng tries to load sage's gd (WRONG) instead of my system's > (RIGHT), and it segfaults. >
That's just a bug. Executables that were built to link against $SAGE_local/lib should run in the SAGE environment. Executables that were not should run in a normal system environment, i.e., be started by sage-native-execute. Before that really helps, we should first merge http://trac.sagemath.org/ticket/14414 though (hint...) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
