[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lzip-bug] build issues - AIX and not gcc
From: |
Antonio Diaz Diaz |
Subject: |
Re: [Lzip-bug] build issues - AIX and not gcc |
Date: |
Sat, 11 Feb 2017 01:07:59 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 |
Hello Michael,
Michael Felt wrote:
I know (i.e., just read) you are not a GNU project - so that explains
why the configure arguments are not working.
AFAICT, the configure arguments are working as expected. It just warns
about the options it does not recognize because it does not need them.
See 'configure --help':
-------------------------------------------------------------------------
Usage: configure [options]
Options: [defaults in brackets]
-h, --help display this help and exit
-V, --version output version information and exit
--srcdir=DIR find the sources in DIR [. or ..]
--prefix=DIR install into DIR [/usr/local]
--exec-prefix=DIR base directory for arch-dependent files [$(prefix)]
--bindir=DIR user executables directory [$(exec_prefix)/bin]
--datarootdir=DIR base directory for doc and data [$(prefix)/share]
--infodir=DIR info files directory [$(datarootdir)/info]
--mandir=DIR man pages directory [$(datarootdir)/man]
CXX=COMPILER C++ compiler to use [g++]
CPPFLAGS=OPTIONS command line options for the preprocessor []
CXXFLAGS=OPTIONS command line options for the C++ compiler
[-Wall -W -O2]
LDFLAGS=OPTIONS command line options for the linker []
-------------------------------------------------------------------------
However, assuming that CXX is c++ when g++ does not work - "is a bug".
Lzip's configure does not try to guess the name of the compiler. It
leaves the user specify it as in '/configure CXX=xlc++'. Making
configure guessing things is error prone and inefficient. Lzip can be
configured, built and tested in less time than it takes for gzip's
configure to run.
And I cannot explain why gnu make is needed - except perhaps .cc might
not be recognixed as an automatic "source" for .o by POSIX make. (Not a
bug of yours - just something to be aware of).
I think that requiring GNU make is more or less standard for GNU
packages because of the limitations in other makes.
Best regards,
Antonio.