autoconf
[Top][All Lists]
Advanced

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

Re: installation instructions on OpenBSD and FreeBSD


From: Akim Demaille
Subject: Re: installation instructions on OpenBSD and FreeBSD
Date: 15 Mar 2001 16:10:25 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)

| *** INSTALL.orig      Sun May 25 18:17:24 1997
| --- INSTALL   Sun Mar 11 16:49:42 2001
| ***************
| *** 119,124 ****
| --- 119,147 ----
|   you can use the `configure' options `--x-includes=DIR' and
|   `--x-libraries=DIR' to specify their locations.
|   
| + Particular Systems
| + ==================
| + 
| +    On FreeBSD, NetBSD, and OpenBSD, the compiler doesn't search include
| + files in /usr/local/include, and the linker doesn't search libraries in
| + /usr/local/lib.  Therefore some packages won't find other packages
| + installed earlier.  To overcome this problem, it is recommended to use
| + the following options:
| + 
| +      env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./configure
| + 

If people think this is a useful addition, why not, but I tend to
think the current text is already clear enough.  And a system specific
section seems not too good an idea to me.

    Compilers and Options
    =====================
    
       Some systems require unusual options for compilation or linking that
    the `configure' script does not know about.  Run `./configure --help'
    for details on some of the pertinent environment variables.
    
       You can give `configure' initial values for variables by setting
    them in the environment.  You can do that on the command line like this:
    
         ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
    
       *Note Environment Variables::, for more details.
    
The longest INSTALL is, the least chances we have that people read it,
so let us be brief, precise, and understandable.

| +    On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC
| + is not installed, it is recommended to use the following options in order
| + to use an ANSI C compiler:
| + 
| +      env CC="cc -Ae" ./configure
| + 

Hm, there are macros to do this.  I don't like this part, it is
configure which is about that, definitely not INSTALL nor the
installer.


| +    On BeOS, user installed software goes in /boot/home/config, not
| + /usr/local.  It is recommended to use the following options:
| + 
| +      CPPFLAGS=-I/boot/home/config/include LDFLAGS=-L/boot/home/config/lib \
| +      ./configure --prefix=/boot/home/config

My opinion is that ./configure --help is enough here.


| ~/src/ace % ./configure --help                                   nostromo 
16:08
| `configure' configures GNU Autoconf 2.49d to adapt to many kinds of systems.
| 
| Usage: ./configure [OPTION]... [VAR=VALUE]...
| 
| To assign environment variables (e.g., CC, CFLAGS...), specify them as
| VAR=VALUE.  See below for descriptions of some of the useful variables.
| 
| Defaults for the options are specified in brackets.
| 
| Configuration:
|   -h, --help              display this help and exit
|       --help=short        display options specific to this package
|       --help=recursive    display the short help of all the included packages
|   -V, --version           display version information and exit
|   -q, --quiet, --silent   do not print `checking...' messages
|       --cache-file=FILE   cache test results in FILE [disabled]
|   -C, --config-cache      alias for `--cache-file=config.cache'
|   -n, --no-create         do not create output files
|       --srcdir=DIR        find the sources in DIR [configure dir or `..']
| 
| Installation directories:
|   --prefix=PREFIX         install architecture-independent files in PREFIX
|                           [/usr/local]
|   --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
|                           [PREFIX]
| 
| By default, `make install' will install all the files in
| `/usr/local/bin', `/usr/local/lib' etc.  You can specify
| an installation prefix other than `/usr/local' using `--prefix',
| for instance `--prefix=$HOME'.

Right above in particular.

| 
| For better control, use the options below.
| 
| Fine tuning of the installation directories:
|   --bindir=DIR           user executables [EPREFIX/bin]
|   --sbindir=DIR          system admin executables [EPREFIX/sbin]
|   --libexecdir=DIR       program executables [EPREFIX/libexec]
|   --datadir=DIR          read-only architecture-independent data 
[PREFIX/share]
|   --sysconfdir=DIR       read-only single-machine data [PREFIX/etc]
|   --sharedstatedir=DIR   modifiable architecture-independent data [PREFIX/com]
|   --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
|   --libdir=DIR           object code libraries [EPREFIX/lib]
|   --includedir=DIR       C header files [PREFIX/include]
|   --oldincludedir=DIR    C header files for non-gcc [/usr/include]
|   --infodir=DIR          info documentation [PREFIX/info]
|   --mandir=DIR           man documentation [PREFIX/man]
| 
| Program names:
|   --program-prefix=PREFIX            prepend PREFIX to installed program names
|   --program-suffix=SUFFIX            append SUFFIX to installed program names
|   --program-transform-name=PROGRAM   run sed PROGRAM on installed program 
names
| 
| Report bugs to <address@hidden>.


BTW, note that properly written configure.in already have good data on
LDFLAGS and so on.

~/src/fileutils-4.0.37 % ./configure --help | tail -11           nostromo 16:10
Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  CPPFLAGS    C/C++ preprocessor flags, e.g. -I<include dir> if you have
              headers in a nonstandard directory <include dir>
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.




reply via email to

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