Re: proposed autobuild_mode naming scheme (was: autobuild logs for Libtool)

[Gary V. Vaughan]

Some other possible additions:

On 23 Aug 2010, at 09:45, Gary V. Vaughan wrote:
>> Here's the scheme:
>> 
>> $autobuild_mode is
>> 
>> - either 'default' (when the user forgets, or knows no better ;-)
>> 
>> or a hyphen-separated string denoting:
>> 
>> - the compiler vendor (gcc, llvm, clang, xl, hp, sun, sgi, dec, intel, pgi,
>> msvc),
> 
> Is the compiler version number interesting?  (or the os release number for
> native compilers with a hard to extract version string)
> 
>> - the binutils vendor (bfd or gold, native),
>> 
>> and then zero or more features from the following list, in that order,
>> and denoting that configure was passed the respective arguments:
>> 
>> - shared     --disable-static
>> - static     --disable-shared
>> - pic        --with-pic
>> - nonpic     --without-pic
>> - fast       --enable-fast-install
>> - nofast     --disable-fast-install
>> - rtl        runtimelinking on AIX (LDFLAGS=-Wl,-brtl)
>> - c++        CC=g++
> 
> I often run on machines with no f77,gfortran,gcj etc:
> 
> - nof77        test -z "${F77}"
> - nofc         test -z "${FC}"
> - nogcj        test -z "${GCJ}"
> - rc           test -n "${RC}"
> 
> (picking the "no"-ness to minimize the mode string length in the common case)
> 
>> - lto        CC='gcc -flto' CXX='gcc -flto' FC='gfortran -flto' 
>> F77='gfortran -flto'
>> - lto-plugin same as lto with gold, but also LDFLAGS=-fuse-linker-plugin
>>            (or '-O4 -use-gold-plugin' with llvm)
>> - ksh/ksh93/dash/...
>>            CONFIG_SHELL=/bin/ksh was set in the environment and
>>            /bin/ksh was used to call configure

Maybe split this into:

- ksh/ksh93/dash/...
                the shell that was actually used
- config:ksh/ksh93/dash/...
                whether CONFIG_SHELL was set (and what to?)

>> - debian-X.Y/gentoo-X.Y/rhel-X.Y/ubuntu-X.Y/...
>>            distribution (maybe including version) that was used
>>            (for those systems where $host is not distinguishing)
>> - ac-X.Y/am-X.Z
>>            Autoconf and Automake versions used (if interesting)

If we're using '-' as the mode string field delimiter, then something other than
'-' for a version separator seems prudent: maybe ':'?

>> - pmake/gmake
>>            setting MAKE=pmake and running the build with $MAKE rather
>>            than the native make.

I'd add the version here too, since gmake-3.79 vs gmake-3.81 can make a 
difference
in some circumstances.

And a few others that might also be useful:

- sitecache     whether a config.site cache was used
- localcache    whether a local config.cache was used
- vpath         using an out of tree build
- sed:<version> gnu or vendor sed (& version string)

Cheers,
-- 
Gary V. Vaughan (address@hidden)

PGP.sig
Description: This is a digitally signed message part