diff options
author | Florian Weimer <fweimer@redhat.com> | 2018-08-17 11:44:39 +0200 |
---|---|---|
committer | Florian Weimer <fweimer@redhat.com> | 2018-08-17 11:44:39 +0200 |
commit | 6413fcde4fe0272eee469aaf41c8bb1d6e6a270f (patch) | |
tree | 5d9ed44268cebf689da7fceafa88371b524a8027 /INSTALL | |
parent | 93a2584cd2ffb2a6e4b17682ba250889059f5d8b (diff) | |
download | glibc-6413fcde4fe0272eee469aaf41c8bb1d6e6a270f.tar glibc-6413fcde4fe0272eee469aaf41c8bb1d6e6a270f.tar.gz glibc-6413fcde4fe0272eee469aaf41c8bb1d6e6a270f.tar.bz2 glibc-6413fcde4fe0272eee469aaf41c8bb1d6e6a270f.zip |
Add --with-nonshared-cflags option to configure
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -90,6 +90,22 @@ if 'CFLAGS' is specified it must enable optimization. For example: library will still be usable, but functionality may be lost--for example, you can't build a shared libc with old binutils. +'--with-nonshared-cflags=CFLAGS' + Use additional compiler flags CFLAGS to build the parts of the + library which are always statically linked into applications and + libraries even with shared linking (that is, the object files + contained in 'lib*_nonshared.a' libraries). The build process will + automatically use the appropriate flags, but this option can be + used to set additional flags required for building applications and + libraries, to match local policy. For example, if such a policy + requires that all code linked into applications must be built with + source fortification, + '--with-nonshared-cflags=-Wp,-D_FORTIFY_SOURCE=2' will make sure + that the objects in 'libc_nonshared.a' are compiled with this flag + (although this will not affect the generated code in this + particular case and potentially change debugging information and + metadata only). + '--disable-shared' Don't build shared libraries even if it is possible. Not all systems support shared libraries; you need ELF support and |