Re: gfortran FFLAGS without paths?
On Tue, Aug 18, 2009 at 05:17:25PM -0400, Aaron M. Ucko wrote:
> Thomas Weber <thomas.weber.mail@gmail.com> writes:
>
> > a) possible without crude hacks?
>
> Depends on what you consider to be a crude hack. ;-)
Nothing that needs severeal lines of script code and a 100+ token long
regexp :)
> AFAICT,
> debian/rules already has a hook for overriding FLIBS, so hard-coding
>
> fc_libs = "-lhdf5 -lz -lgfortranbegin -lgfortran -lm"
Yes, I saw that possibility later. Wouldn't
fc_libs = "-lgfortranbegin -lgfortran"
be enough, though?
> should have the desired effect, although it may need occasional tuning
> for newer gfortran versions.
That's one of the things I'm unsure of. Will the above work, if I use
e.g. g++-4.3 with gfortran-4.2? And if it doesn't work, will it at least
break in a clear way?
> > b) sensible?
>
> Yes, given that the relevant paths are already the default anyway;
> Octave's build system is just being paranoid, resulting in fragility.
I don't think Octave does anything special, it seems to use the default
AC_F77_LIBRARY_LDFLAGS macro. The problem is not so much the test but
the fact that later on, these values are used without being tested
again.
Anyway, I just wanted to ensure that I don't start doing something
entirely stupid, so thanks for your help.
thoma
Reply to: