[SciPy-dev] FTBFS on Debian

Ondrej Certik ondrej@certik...
Mon Apr 14 07:48:15 CDT 2008


On Mon, Apr 14, 2008 at 1:36 PM, Robert Kern <robert.kern@gmail.com> wrote:
> On Mon, Apr 14, 2008 at 6:22 AM, David Cournapeau
>
> <david@ar.media.kyoto-u.ac.jp> wrote:
>
> > Robert Kern wrote:
>  >  >
>  >  > This problem is almost always caused by LDFLAGS being set. LDFLAGS
>  >  > *overrides* all of the Fortran link flags.
>  >  >
>  >  >
>  >
>  >  That's what I thought first, but then why gcc still uses -shared ? Why
>  >  only gfortran ?
>
>  As we've discussed before, this overriding behavior only exists
>  because we need some way to override Fortran compiler flags since the
>  code will always be a little bit out of date with respect to the
>  various new versions of the Fortran compilers that we support. C
>  extensions are left alone because the link flags are almost always
>  correct because the C compiler is almost always the one used to build
>  Python itself.

Wow, indeed, this solves the problem:

$ svn di
Index: debian/rules
===================================================================
--- debian/rules	(revision 5013)
+++ debian/rules	(working copy)
@@ -8,6 +8,8 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1

+unexport LDFLAGS
+
 PYVERS:= $(shell pyversions -v -r debian/control)
 BASE=$(shell pwd)/debian
 #debian_patches= umfpack signals viewer sandbox  #fft python23 amd64

Thanks a lot Robert!

This would take me hours until I'd figure it out...

Ondrej


More information about the Scipy-dev mailing list