Unix [Mac OS] VM config options?
jdougan at acm.org
Thu Jun 9 07:54:28 UTC 2005
Give the --help option to configure. Or read the autoconf files.
On a 3.7-b build kit I'm messing with:
`configure' configures this package to adapt to many kinds of systems.
Usage: config/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.
-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
-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 `..']
--prefix=PREFIX install architecture-independent files in PREFIX
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
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'.
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
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data
--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]
--x-includes=DIR X include files are in DIR
--x-libraries=DIR X library files are in DIR
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
--disable-FEATURE do not include FEATURE (same as
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
build static libraries [default=no]
build shared libraries [default=yes]
optimize for fast installation [default=yes]
--disable-libtool-lock avoid locking (might break parallel builds)
--disable-iconv disable iconv support default=enabled
--enable-mpg-mmx enable MMX support in Mpeg3Plugin default=no
--enable-mpg-pthreads enable pthread support in Mpeg3Plugin default=no
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-src=dir generated src directory default=src
--with-gnu-awk assume that awk is GNU gawk default=no
--with-gnu-as assume that as is the GNU assembler default=no
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-pic try to use only PIC/non-PIC objects [default=use
include additional configurations [automatic]
--without-rfb disable Remote FrameBuffer support default=enabled
--without-npsqueak disable browser plugin support default=enabled
--without-quartz disable MacOSX Window System support
--without-x disable X Window System support default=enabled
--with-x use the X Window System
--with-ffi=ffi use FFI support default=auto
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CPP C preprocessor
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CXXCPP C++ preprocessor
F77 Fortran 77 compiler command
FFLAGS Fortran 77 compiler flags
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
goran at krampe.se wrote:
>(cc-ing Ian directly this time, since I know following lists is a pain
>>--- goran at krampe.se wrote:
>>>... I was wondering - is there a documented list
>>>of all configure options when building?
>>In the same vein, I was curious if anyone had been
>>building the current VM under Mac OS 10.4.1? I
>>got some compiler errors when I tried last week,
>>but was not sure if this was due to ongoing work
>>on the VM.
>And then John M McIntosh <johnmci at smalltalkconsulting.com> wrote:
>>Are you talking building the os-x carbon xcode based VM?
>>Or building under unix?
>Wel, *I* was referring to unix - but I guess Brent was referring to
>>If under unix, get latest SVN tree, download latest beta etc of
>>follow unix build instructions.
>Yes, but are all the options to "../platforms/unix/config/configure"
>documented there? I know about the new 32/64 bit option, and I know
>there is a -without-X (or something like that) option, but I was
>wondering if there are more and if there is a list somewhere or if not -
>how I can easily find out.
>The answer may of course very well be "read the autoconf files" -
>whichever they are. :) Just thought I should ask first.
>And the reason again is that I am now maintaining a Squeak (and
>Squeak-beta) source distro module for Lunar Linux, which is a distro
>that builds everything from source (like Gentoo) and my current
>Squeak-beta module nicely asks if you want a 32 or 64 bit VM, so I
>wondered if I could perhaps ask more nice questions with good defaults
>PS. Lunar is really nice. Debian feels rather clunky now in
jdougan at acm.org
More information about the Vm-dev