[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 135974] FFLAGS ignored on building project
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-01-03 20:09:09
Message-ID: 20070103200909.13074.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=135974         




------- Additional Comments From apaku gmx de  2007-01-03 21:09 -------
CFLAGS are flags to be set for gcc, i.e. the C Compiler. CXXFLAGS for the C++ \
Compiler and FFLAGS are meant to be used for the fortran compiler.

The intended way of doing things for autotools projects is to pass these flags to the \
configure call as environment variables and configure will put them (together with \
some other values for these flags) into the generated Makefile.

Unfortunately it seems the configure script doesn't do this for FFLAGS. Now kdevelop \
has absolutely no control over the configure script, its completely generated from \
autotools based on defaults and the macros you specify in configure.in.in or \
configure.ac (or whatever you use).

As for the upstream report: I have no account for autotools bugzilla and I don't even \
know where it is. I have no idea about autotools except some basic stuff and I \
certainly don't have the time to hunt down a bug I can't easily reproduce because I \
have no idea about fortran either. Sorry.

As for what kdevelop does behind the scenes: You can see that in the output windows, \
i.e. it just runs FFLAGS="Whatever you set them to" configure <configure flags that \
you have set>. You should have the same problem (i.e. missing you FFLAGS values in \
the generated Makefile's) if you run configure from a shell.

Andreas


[prev in list] [next in list] [prev in thread] [next in thread]