[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ed] [PATCH] configure: respect user env settings

From: Mike Frysinger
Subject: Re: [Bug-ed] [PATCH] configure: respect user env settings
Date: Thu, 1 Jan 2009 17:49:13 -0500
User-agent: KMail/1.10.3 (Linux/2.6.28; KDE/4.1.3; x86_64; ; )

On Thursday 01 January 2009 08:47:18 Antonio Diaz Diaz wrote:
> Mike Frysinger wrote:
> > First we have to fix the locale otherwise some of the arg parsing may
> > fail.
> Agreed for LC_ALL, but why LANGUAGE?. It is not even mentioned in the
> bash manual.

i just copy & pasted what latest autoconf is generating.  i'd agree generally 
that only LC_ALL is needed.  maybe some non-posix conforming system needs 

> > Then we fix the toolchain related variables to respect the user build
> > settings.
> The GNU Coding Standards don't agree
> (http://www.gnu.org/prep/standards/html_node/Configuration.html):
> "Specifying variables as arguments to configure, like this:
>            ./configure CC=gcc
> is preferable to setting them in environment variables:
>            CC=gcc ./configure
> as it helps to recreate the same configuration later with config.status".

"preferable" is not the same thing as "must".  fact is, every autotooled 
package out there behaves this way (respects environment), and forcing this 
non-standard behavior in ed just makes ed a pita to easily integrate into 
packaging systems.

from `./configure --help` from any autoconf script:
Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags

plus, ed does not use a config.status script and autoconf has no problem 
whatsoever moving things from the environment to config.status.  so i imagine 
that's an outdated remark.

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]