Lines Matching refs:build

17 build it in a separate build directory.  For example, if you have
19 directory '/src/gnu/glibc-build' to put the object files in.  This
20 allows removing the whole build directory in case an error occurs, which
28    Please note that even though you're building in a separate build
45 build system for particular files, such as for optimization and
91      example, you can't build a shared libc with old binutils.
94      With '--with-default-link', the build system does not use a custom
100      Use additional compiler flags CFLAGS to build the parts of the
103      contained in 'lib*_nonshared.a' libraries).  The build process will
116      Use additional compiler flags CFLAGS to build the early startup
129      Don't build shared libraries even if it is possible.  Not all
134      Don't build glibc programs and the testsuite as position
177      Don't build libraries with profiling information.  You may want to
228      to build without this option (for example, if building with a newer
230      with, so new warnings cause the build with '-Werror' to fail), you
271      remove it from the build completely.
277 '--build=BUILD-SYSTEM'
295      If you specify just '--build', 'configure' will get confused.
298      Specify a description, possibly including a build number or build
301      example, '--with-pkgversion='FooBar GNU/Linux glibc build 123''.
310    To build the library and related programs, type 'make'.  This will
324    To build and run test programs which exercise some of the library
346 files, as part of the build process.  You can build them manually with
352 build directory and add values as appropriate for your system.  The file
361 to use for programs run on the build system as part of compiling the
369 binaries of the GNU C Library.  The source and build directories must be
370 visible at the same locations on both the build system and HOSTNAME.
412 manual, type 'make install'.  This will build things, if necessary,
425    You must first build the library ('make'), optionally check it ('make
476 are supported by the GNU C Library, you can issue from your build
499 build the GNU C Library:
504      build the GNU C Library.
512      verified to work to build the GNU C Library.
544      You must use GNU 'binutils' (as and ld) to build the GNU C Library.
547      verified to work to build the GNU C Library.
563      verified to work to build the GNU C Library.
570      version 5.1.1 is the newest verified to work to build the GNU C
577      newest verified to work to build the GNU C Library.
582      the 'mtrace' program, to build the GNU C Library manual.  As of
584      to build the GNU C Library.
590      4.8 is the newest verified to work to build the GNU C Library.
594      Python is required to build the GNU C Library.  As of release time,
629      version verified to work to build the GNU C Library.
677 verified to work to build the GNU C Library.