Re: [Lzip-bug] build issues - AIX and not gcc

[Antonio Diaz Diaz]

Michael Felt wrote:
> I stand corrected - "not working" should be "warns about". Many gnu
> projects silently ignore these "standard" arguments. And frankly, I do
> not know if one way is "better" than the other. Eye of the beholder.

I personally prefer the warnings. They make easier to know what options 
are not used and can be removed.


> And, more directly - it starts by always assuming CXX=g++ - even with
> CXX set to something else in the environment:

Setting environment variables for configure is deprecated because 
running configure in varying environments can be extremely dangerous. 
The configure script of lzip implements the method recommended by 
autoconf to pass variables[1][2].

In any case, './configure CXX=<your_compiler>' is guaranteed to work.

[1]http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Defining-Variables.html
Variables not defined in a site shell script can be set in the 
environment passed to configure. However, some packages may run 
configure again during the build, and the customized values of these 
variables may be lost. In order to avoid this problem, you should set 
them in the configure command line, using ‘VAR=value’. For example:

     ./configure CC=/usr/local2/bin/gcc

[2]http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Setting-Output-Variables.html
Indeed, while configure can notice the definition of CC in ‘./configure 
CC=bizarre-cc’, it is impossible to notice it in ‘CC=bizarre-cc 
./configure’, which, unfortunately, is what most users do.


> As the issue is that $< is not expanded to foo.cc I would assume that
> .cc is not in the "OEM" make RULES.

Maybe your make does not recognize $< in normal rules like the rule for 
main.o. I find this an annoying limitation of some makes because using 
$< is less error prone than repeating the name of the prerequisite.


Best regards,
Antonio.