Hmmm, but that would replicate the fairly complicated Python code that it already uses to determine the proper flags.
For the moment, I've fixed it by doing an "unset LDFLAGS" in the spkg-install file, but I think it's still a Sage bug to export empty LDFLAGS if the user hasn't set them that way. There's a difference between an empty value and "not defined", after all. Bill On Monday, September 23, 2013 11:19:43 PM UTC-7, Felix Salfelder wrote: > > On Mon, Sep 23, 2013 at 02:21:39PM -0700, Bill Janssen wrote: > > I was trying to compile the Python+Fortran Assimulo package on Sage > (5.11) > > on OS X, and I couldn't figure out why the gfortran link step kept > failing > > -- the correct linker flags for shared libraries weren't being used. > Turns > > out that the "fcompiler" support in Numpy's distutils will *always* look > at > > LDFLAGS and use them instead of the carefully determined > platform-specific > > flags. > > > > And there's this code in sage-env: > > > > if [ "$LDFLAGS" = "" ]; then > > LDFLAGS="" && export LDFLAGS > > fi > > > > So the empty LDFLAGS setting was always clobbering the carefully > determined > > platform-specific flags. > > > > Not sure this is a good thing... > > While it does not exactly make sense to export empty LDFLAGS in case > they are empty already, this shouldn't affect the spkg. the correct > place to figure out appropriate flags for the Assimulo build system is > its spkg-install file/program (you may want to *append* global LDFLAGS, > maybe...). > > regards > felix > -- 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/groups/opt_out.
