libtool-patches
[Top][All Lists]
Advanced

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

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


From: Ralf Wildenhues
Subject: proposed autobuild_mode naming scheme (was: autobuild logs for Libtool)
Date: Sun, 22 Aug 2010 20:44:57 +0200
User-agent: Mutt/1.5.20 (2010-04-22)

* Ralf Wildenhues wrote on Sun, Aug 22, 2010 at 08:38:19PM CEST:
> configure: autobuild mode... default
[...]

Autobuild uses a few strings to categorize log results: package version,
$build, $host, hostname, time and date, and a so-called "mode" which my
patch sets with the $autobuild_mode variable.

I will be using something like the following values for $autobuild_mode.
Suggestions and additions welcome, I think we could profit from a
common, recognizable scheme: that way, when different people all mail
their results to the autobuild site, results become more easily
comparable.

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),
- 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++
- 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
- 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)
- pmake/gmake
             setting MAKE=pmake and running the build with $MAKE rather
             than the native make.

So, for example, using GCC on AIX 5.2 with the system ld and
runtimelinking, $host would be powerpc-aix53-.., my autobuild_mode would
be
  gcc-native-rtl

I'm not yet sure whether and when to leave out the compiler and binutils
vendor strings; on some systems there is one canonical choice and there
would be no need to distinguish.  Not sure if the vendor one would
always be the best default though.

Additions welcome.

Cheers,
Ralf



reply via email to

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