* Bob Friesenhahn wrote on Tue, Feb 07, 2006 at 03:07:37AM CET:
> On Tue, 7 Feb 2006, Harlan Stenn wrote:
>
> >I'm talking about software packages that, on hot machines, take 30-45
> >minutes to do a "configure" run.
>
> I assure you that I have spent quite a bit of time watching configure
> run
Hi John, Matt,
> On Mon, 6 Feb 2006, John Calcote wrote:
>
> > You know, I've recently finished reading the manuals for m4, libtool,
> > autoconf, and automake. After 1000 pages of reading, I was frustrated to
> > walk away knowing very little more than I started with. I believe this
> > is prima
* Ralf Wildenhues wrote on Tue, Feb 07, 2006 at 07:08:37AM CET:
>
> You, the user, can still force variable assignments to be recorded even
> for non-precious variables by putting them on the configure command
> line:
>../source/configure FOO=bar
>
> So the bottom line is that you should alwa
Brian,
Thanks for the reply. I get this. I realize that you MAY set CFLAGS on
the command line if you wish - and you should - IF you have special
flags to set on the command line for a specific configuration or build.
My complaint was that the AC_PROG_CC macro just assumes you want -O2
(again - I
In one case, you are using valid shell command syntax to set a variable
for a specific run of a script or program (var=value ./program).
In the other case, you are passing a parameter to configure, which then
sets this variable for its own environment as it parses its parameter
list, and then co
When you override CFLAGS on the configure command line, you give
configure the opportunity to add more flags to the CFLAGS variable that
are then passed on to make. On the other hand, when you modify CFLAGS on
the make command line, you are overriding all settings provided to the
Makefile by the co
Brian,
Thanks for the reply. I get this. I realize that you MAY set CFLAGS on
the command line if you wish - and you should - IF you have special
flags to set on the command line for a specific configuration or build.
My complaint was that the AC_PROG_CC macro just assumes you want -O2
(again - I
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hi Ed,
>
> * Ed Hartnett wrote on Mon, Feb 06, 2006 at 04:42:01PM CET:
>>
>> I have a configure script which needs to know whether it is dealing
>> with the f95 distributed with gcc-4.x, or the g95, which is apparently
>> an independent project, which
"John Calcote" <[EMAIL PROTECTED]> writes:
> When you override CFLAGS on the configure command line, you give
> configure the opportunity to add more flags to the CFLAGS variable that
> are then passed on to make.
Yes, there are many broken configure scripts out there that do that.
Please don't s
My point exactly. The autoconf system should reserve a variable that is NOT the
user. Automake has such a facility - AM_CFLAGS. This variable should be
reserved for configure to add flags to the compiler command line based on
higher-level, user-specified options, such as --enable-debug, or
--wi
John Calcote wrote:
When you override CFLAGS on the configure command line, you give
configure the opportunity to add more flags to the CFLAGS variable that
are then passed on to make. On the other hand, when you modify CFLAGS on
the make command line, you are overriding all settings provided to
11 matches
Mail list logo
