Lines Matching refs:build

35 @Theglibc{} cannot be compiled in the source directory.  You must build
36 it in a separate build directory.  For example, if you have unpacked
39 @file{/src/gnu/glibc-build} to put the object files in.  This allows
40 removing the whole build directory in case an error occurs, which is
50 Please note that even though you're building in a separate build
68 that may be overridden by the @glibcadj{} build system for particular
117 usable, but functionality may be lost---for example, you can't build a
121 With @code{--with-default-link}, the build system does not use a custom
127 Use additional compiler flags @var{cflags} to build the parts of the
130 in @file{lib*_nonshared.a} libraries).  The build process will
141 Use additional compiler flags @var{cflags} to build the early startup
154 @c Don't build static libraries.  Static libraries aren't that useful these
155 @c days, but we recommend you build them in case you need them.
158 Don't build shared libraries even if it is possible.  Not all systems
163 Don't build glibc programs and the testsuite as position independent
204 Don't build libraries with profiling information.  You may want to use
256 to build without this option (for example, if building with a newer
258 new warnings cause the build with @option{-Werror} to fail), you can
299 remove it from the build completely.
305 @item --build=@var{build-system}
308 @var{build-system} is different from @var{host-system}, @code{configure}
309 will prepare to cross-compile @theglibc{} from @var{build-system} to be used
323 If you specify just @samp{--build}, @code{configure} will get confused.
326 Specify a description, possibly including a build number or build
329 For example, @option{--with-pkgversion='FooBar GNU/Linux glibc build
339 To build the library and related programs, type @code{make}.  This will
353 To build and run test programs which exercise some of the library
375 manual, as Info files, as part of the build process.  You can build
381 @file{configparms} in your build directory and add values as appropriate
391 run on the build system as part of compiling the library.  You may need to
399 the newly built binaries of @theglibc{}.  The source and build
400 directories must be visible at the same locations on both the build
451 build things, if necessary, before installing them; however, you should
464 You must first build the library (@samp{make}), optionally check it
514 supported by @theglibc{}, you can issue from your build directory the command
537 build @theglibc{}:
544 to build @theglibc{}.
552 release time, GCC 12.1 is the newest compiler verified to work to build
586 You must use GNU @code{binutils} (as and ld) to build @theglibc{}.
589 verified to work to build @theglibc{}.
605 to build @theglibc{}.
614 to work to build @theglibc{}.
621 verified to work to build @theglibc{}.
627 @code{mtrace} program, to build the @glibcadj{} manual.  As of release
629 build @theglibc{}.
636 4.8 is the newest verified to work to build @theglibc{}.
641 Python is required to build @theglibc{}.  As of release time, Python
684 version verified to work to build @theglibc{}.
738 to work to build @theglibc{}.