Dave Korn wrote:
>> # Values which can be overridden either system-wide or per package
>> +declare -x CC="gcc";
>> declare -x CFLAGS="-O2 -pipe ";
>> +declare -x CPP="cpp";
>> declare -x CPPFLAGS="";
>> +declare -x CXX="g++";
>> +declare -x CXXCPP="cpp";
>> declare -x CXXFLAGS="${CFLAGS}";
>> +declare -x F77="g77";
>> declare -x FFLAGS="${CFLAGS}";
>> +declare -x GCJ="gcj";
>> declare -x GCJFLAGS="${CFLAGS}";
>> declare -x LDFLAGS="-Wl,--enable-auto-import ";
>> declare -x LIBS="";
And then again... now I think of it, this is an obsolete and deprecated way
to drive autotools, isn't it? I thought that we're supposed to write
./configure CFLAGS="-g -O2" ...
these days, not
CFLAGS="-g -O2" ./configure ...
and similarly
make CFLAGS="-g -O2" ...
and not
CFLAGS="-g -O2" make ...
i.e., we're supposed to use variable assignment syntax but not actual
shell-level variables, only make or configure variables. It doesn't surprise
me that exporting similarly-named environment variables would break
specifically the one project that uses bootstrapping to build. Most packages
will get away with this usage still, but anything where CC != CC_FOR_TARGET is
also likely to end up using the wrong preprocessor, i.e. mightn't this break
cross-builds?
cheers,
DaveK
------------------------------------------------------------------------------
_______________________________________________
Cygwin-ports-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
