How to compile and install only one compile in GCC?
Peng Yu
pengyu.ut@gmail.com
Wed Sep 2 14:48:00 GMT 2009
Hi,
I think that we have been talking about different configure files. I
found the following two configure files. You were talking about the
first one. But I were talking about the second one.
$ ls gcc-4.3.4/gcc/configure
gcc-4.3.4/gcc/configure
$ ls gcc-4.3.4/configure
gcc-4.3.4/configure
Question: If I want to install any compile in GCC, I should go to the
directory 'gcc' then run configure, right? What is the usage of the
second configure file?
Regards,
Peng
On Wed, Sep 2, 2009 at 8:06 AM, Miguel Lordelo<miguellordelo@gmail.com> wrote:
> Hmmm....strange that there is no enable-languages option written, but if you
> take a look at:
> http://gcc.gnu.org/install/configure.html
>
> You will see probabily more options then the listeted once...If I would be
> in you position I would try to use this option just to try if the option is
> available and if it works...but I'm quite shure that it will work!
>
> Chears,
> ML
>
> On Wed, Sep 2, 2009 at 2:55 PM, Peng Yu <pengyu.ut@gmail.com> wrote:
>>
>> On Wed, Sep 2, 2009 at 7:26 AM, Tim Prince<n8tm@aol.com> wrote:
>> > Peng Yu wrote:
>> >
>> >>
>> >> I downloaded gcc-4.3.4. But I don't see how to install only one
>> >> compiler, for example, gcj. Can somebody point me how to do it?
>> >>
>> > Won't work without C. Did you miss the configure option
>> > --enable-languages='c java' ?
>> >
>>
>> I checked again. But I still don't see such option. I only see
>> "--enable-FEATURE[=ARG] include FEATURE [ARG=yes]". Is it what you
>> refer to?
>>
>> $ ./configure --help
>> `configure' configures this package 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'.
>>
>> 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
>>
>> System types:
>> --build=BUILD configure for building on BUILD [guessed]
>> --host=HOST cross-compile to build programs to run on HOST [BUILD]
>> --target=TARGET configure for building compilers for TARGET [HOST]
>>
>> Optional Features:
>> --disable-FEATURE do not include FEATURE (same as
>> --enable-FEATURE=no)
>> --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
>> --enable-libada build libada directory
>> --enable-libssp build libssp directory
>> --enable-stage1-languages[=all] choose additional languages to build
>> during
>> stage1. Mostly useful for compiler development.
>> --enable-objc-gc enable use of Boehm's garbage collector with the
>> GNU Objective-C runtime
>> --enable-bootstrap enable bootstrapping [yes if native build]
>> --enable-serial-[{host,target,build}-]configure
>> force sequential configuration of
>> sub-packages for the host, target or build
>> machine, or all sub-packages
>> --enable-maintainer-mode enable make rules and dependencies not useful
>> (and sometimes confusing) to the casual installer
>> --enable-stage1-checking[=all] choose additional checking for stage1
>> of the compiler
>> --enable-werror enable -Werror in bootstrap stage2 and later
>>
>> Optional Packages:
>> --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
>> --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
>> --with-build-libsubdir=DIR Directory where to find libraries for build
>> system
>> --with-mpfr-dir=PATH this option has been REMOVED
>> --with-mpfr=PATH specify prefix directory for installed MPFR
>> package.
>> Equivalent to --with-mpfr-include=PATH/include
>> plus --with-mpfr-lib=PATH/lib
>> --with-mpfr-include=PATH
>> specify directory for installed MPFR include files
>> --with-mpfr-lib=PATH specify directory for the installed MPFR library
>> --with-gmp-dir=PATH this option has been REMOVED
>> --with-gmp=PATH specify prefix directory for the installed
>> GMP package.
>> Equivalent to --with-gmp-include=PATH/include
>> plus --with-gmp-lib=PATH/lib
>> --with-gmp-include=PATH specify directory for installed GMP include files
>> --with-gmp-lib=PATH specify directory for the installed GMP library
>> --with-build-sysroot=SYSROOT
>> use sysroot as the system root during the build
>> --with-debug-prefix-map='A=B C=D ...'
>> map A to B, C to D ... in debug information
>> --with-build-time-tools=PATH
>> use given path to find target tools during the
>> build
>> --with-datarootdir use datarootdir as the data root directory.
>> --with-docdir install documentation in this directory.
>> --with-pdfdir install pdf in this directory.
>> --with-htmldir install html in this directory.
>>
>> 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>
>> CXX C++ compiler command
>> CXXFLAGS C++ compiler flags
>> AR AR for the host
>> AS AS for the host
>> DLLTOOL DLLTOOL for the host
>> LD LD for the host
>> LIPO LIPO for the host
>> NM NM for the host
>> RANLIB RANLIB for the host
>> STRIP STRIP for the host
>> WINDRES WINDRES for the host
>> WINDMC WINDMC for the host
>> OBJCOPY OBJCOPY for the host
>> OBJDUMP OBJDUMP for the host
>> CC_FOR_TARGET
>> CC for the target
>> CXX_FOR_TARGET
>> CXX for the target
>> GCC_FOR_TARGET
>> GCC for the target
>> GCJ_FOR_TARGET
>> GCJ for the target
>> GFORTRAN_FOR_TARGET
>> GFORTRAN for the target
>> AR_FOR_TARGET
>> AR for the target
>> AS_FOR_TARGET
>> AS for the target
>> DLLTOOL_FOR_TARGET
>> DLLTOOL for the target
>> LD_FOR_TARGET
>> LD for the target
>> LIPO_FOR_TARGET
>> LIPO for the target
>> NM_FOR_TARGET
>> NM for the target
>> OBJDUMP_FOR_TARGET
>> OBJDUMP for the target
>> RANLIB_FOR_TARGET
>> RANLIB for the target
>> STRIP_FOR_TARGET
>> STRIP for the target
>> WINDRES_FOR_TARGET
>> WINDRES for the target
>> WINDMC_FOR_TARGET
>> WINDMC for the target
>>
>> Use these variables to override the choices made by `configure' or to help
>> it to find libraries and programs with nonstandard names/locations.
>
>
More information about the Gcc-help
mailing list