RepoMirrors/musl
1
0
Fork 0
mirror of git://git.musl-libc.org/musl synced 2024-12-25 08:02:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
b418ea1b66
musl/configure

765 lines
23 KiB
Plaintext
Raw Normal View History

initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#!/bin/sh
usage () {
cat <<EOF
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
Usage: $0 [OPTION]... [VAR=VALUE]... [TARGET]
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
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.
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
Configuration:
--srcdir=DIR source directory [detected]
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
Installation directories:
--prefix=PREFIX main installation prefix [/usr/local/musl]
--exec-prefix=EPREFIX installation prefix for executable files [PREFIX]
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--libdir=DIR library files for the linker [PREFIX/lib]
--includedir=DIR include files for the C compiler [PREFIX/include]
--syslibdir=DIR location for the dynamic linker [/lib]
System types:
--target=TARGET configure to run on target TARGET [detected]
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
--host=HOST same as --target
follow standard configure behavior for cross compile prefix the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
2016-04-29 23:50:33 +00:00
--build=BUILD build system type; used only to infer cross-compiling
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
Optional features:
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
--enable-optimize=... optimize listed components for speed over size [auto]
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
--enable-debug build with debugging information [disabled]
--enable-warnings build with recommended warnings flags [disabled]
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
--enable-visibility use global visibility options to optimize PIC [auto]
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
--enable-wrapper=... build given musl toolchain wrapper [auto]
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
--disable-shared inhibit building shared library [enabled]
--disable-static inhibit building static library [enabled]
Some influential environment variables:
CC C compiler command [detected]
CFLAGS C compiler flags [-Os -pipe ...]
support configuring cross compiling with CROSS_COMPILE prefix variable
2012-08-15 02:50:16 +00:00
CROSS_COMPILE prefix for cross compiler and tools [none]
add LIBCC (compiler runtime) logic and override to configure this should both fix the issue with ARM needing -lgcc_eh (although that's really a bug in the libgcc build process that's causing considerable bloat, which should be fixed) and make it easier to build musl using clang/llvm in place of gcc. unfortunately I don't know a good way to detect and support pcc's -lpcc since it's not in pcc's default library search path...
2012-09-10 19:30:52 +00:00
LIBCC compiler runtime library [detected]
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
Use these variables to override the choices made by configure.
EOF
exit 0
}
# Helper functions
make configure store its command line in config.mak for easy re-run proper shell quoting and pretty-printing (avoiding ugly gratuitous quoting and bad quoting style) is included.
2013-08-16 22:19:47 +00:00
quote () {
tr '\n' ' ' <<EOF | grep '^[-[:alnum:]_=,./:]* $' >/dev/null 2>&1 && { echo "$1" ; return 0 ; }
$1
EOF
fix two bugs in sed code configure uses to save command line one place where semicolon (non-portable) was still used in place of separate -e options (copied over from an old version of this code), and use of a literal slash in the bracket expression for the final command, despite slash being used as the delimiter for the s command.
2013-08-20 17:51:46 +00:00
printf %s\\n "$1" | sed -e "s/'/'\\\\''/g" -e "1s/^/'/" -e "\$s/\$/'/" -e "s#^'\([-[:alnum:]_,./:]*\)=\(.*\)\$#\1='\2#"
make configure store its command line in config.mak for easy re-run proper shell quoting and pretty-printing (avoiding ugly gratuitous quoting and bad quoting style) is included.
2013-08-16 22:19:47 +00:00
}
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
echo () { printf "%s\n" "$*" ; }
fail () { echo "$*" ; exit 1 ; }
fnmatch () { eval "case \"\$2\" in $1) return 0 ;; *) return 1 ;; esac" ; }
cmdexists () { type "$1" >/dev/null 2>&1 ; }
trycc () { test -z "$CC" && cmdexists "$1" && CC=$1 ; }
fix "configure --prefix=" and improve path/arg handling in configure previously, empty string was treated as "use default". this is apparently not compatible with standard configure semantics where an empty prefix puts everything under /. the new logic should be a lot cleaner and not suffer from such issues.
2012-11-08 22:20:50 +00:00
stripdir () {
while eval "fnmatch '*/' \"\${$1}\"" ; do eval "$1=\${$1%/}" ; done
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
}
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
trycppif () {
printf "checking preprocessor condition %s... " "$1"
fix invalid C in new trycppif tests in configure script an empty program is not valid and would be reasonable grounds for the compiler to give an error, which would break these tests.
2013-07-19 00:37:19 +00:00
echo "typedef int x;" > "$tmpc"
echo "#if $1" >> "$tmpc"
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
echo "#error yes" >> "$tmpc"
echo "#endif" >> "$tmpc"
if $CC $2 -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "false\n"
return 1
else
printf "true\n"
return 0
fi
}
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
tryflag () {
printf "checking whether compiler accepts %s... " "$2"
echo "typedef int x;" > "$tmpc"
configure: work around compilers that merely warn for unknown options some compilers (such as clang) accept unknown options without error, but then print warnings on each invocation, cluttering the build output and burying meaningful warnings. this patch makes configure's tryflag and tryldflag functions use additional options to turn the unknown-option warnings into errors, if available, but only at check time. these options are not output in config.mak to avoid the risk of spurious build breakage; if they work, they will have already done their job at configure time.
2015-05-28 03:52:22 +00:00
if $CC $CFLAGS_TRY $2 -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
printf "yes\n"
eval "$1=\"\${$1} \$2\""
eval "$1=\${$1# }"
return 0
else
printf "no\n"
return 1
fi
}
add configure check for gnu linker hash style setting some broken distro-provided toolchains have modified gcc to produce only "gnu hash" dynamic hash table by default. as this is unsupported by musl, that results in a non-working libc.so. we detect and switch this on in configure rather than hard-coding it in the Makefile because it's not supported by old binutils versions, but that might not even be relevant since old binutils versions already fail from -Bsymbolic-functions being missing. at some point I may review whether this should just go in the Makefile...
2012-06-07 00:45:52 +00:00
tryldflag () {
printf "checking whether linker accepts %s... " "$2"
avoid linking main program in linker tests it's possible that the user has provided a compiler that does not have any libc to link to, so linking a main program is a bad idea. instead, generate an empty shared library with no dependencies.
2012-06-07 04:23:58 +00:00
echo "typedef int x;" > "$tmpc"
configure: work around compilers that merely warn for unknown options some compilers (such as clang) accept unknown options without error, but then print warnings on each invocation, cluttering the build output and burying meaningful warnings. this patch makes configure's tryflag and tryldflag functions use additional options to turn the unknown-option warnings into errors, if available, but only at check time. these options are not output in config.mak to avoid the risk of spurious build breakage; if they work, they will have already done their job at configure time.
2015-05-28 03:52:22 +00:00
if $CC $LDFLAGS_TRY -nostdlib -shared "$2" -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
add configure check for gnu linker hash style setting some broken distro-provided toolchains have modified gcc to produce only "gnu hash" dynamic hash table by default. as this is unsupported by musl, that results in a non-working libc.so. we detect and switch this on in configure rather than hard-coding it in the Makefile because it's not supported by old binutils versions, but that might not even be relevant since old binutils versions already fail from -Bsymbolic-functions being missing. at some point I may review whether this should just go in the Makefile...
2012-06-07 00:45:52 +00:00
printf "yes\n"
eval "$1=\"\${$1} \$2\""
eval "$1=\${$1# }"
return 0
else
printf "no\n"
return 1
fi
}
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
# Beginning of actual script
add configure check for gnu linker hash style setting some broken distro-provided toolchains have modified gcc to produce only "gnu hash" dynamic hash table by default. as this is unsupported by musl, that results in a non-working libc.so. we detect and switch this on in configure rather than hard-coding it in the Makefile because it's not supported by old binutils versions, but that might not even be relevant since old binutils versions already fail from -Bsymbolic-functions being missing. at some point I may review whether this should just go in the Makefile...
2012-06-07 00:45:52 +00:00
CFLAGS_C99FSE=
CFLAGS_AUTO=
work around gcc 4.8's generation of self-referential mem* functions at -O3
2013-08-01 21:12:23 +00:00
CFLAGS_MEMOPS=
allow libc itself to be built with stack protector enabled this was already essentially possible as a result of the previous commits changing the dynamic linker/thread pointer bootstrap process. this commit mainly adds build system infrastructure: configure no longer attempts to disable stack protector. instead it simply determines how so the makefile can disable stack protector for a few translation units used during early startup. stack protector is also disabled for memcpy and memset since compilers (incorrectly) generate calls to them on some archs to implement struct initialization and assignment, and such calls may creep into early initialization. no explicit attempt to enable stack protector is made by configure at this time; any stack protector option supported by the compiler can be passed to configure in CFLAGS, and if the compiler uses stack protector by default, this default is respected.
2015-04-14 00:13:10 +00:00
CFLAGS_NOSSP=
configure: work around compilers that merely warn for unknown options some compilers (such as clang) accept unknown options without error, but then print warnings on each invocation, cluttering the build output and burying meaningful warnings. this patch makes configure's tryflag and tryldflag functions use additional options to turn the unknown-option warnings into errors, if available, but only at check time. these options are not output in config.mak to avoid the risk of spurious build breakage; if they work, they will have already done their job at configure time.
2015-05-28 03:52:22 +00:00
CFLAGS_TRY=
add configure check for gnu linker hash style setting some broken distro-provided toolchains have modified gcc to produce only "gnu hash" dynamic hash table by default. as this is unsupported by musl, that results in a non-working libc.so. we detect and switch this on in configure rather than hard-coding it in the Makefile because it's not supported by old binutils versions, but that might not even be relevant since old binutils versions already fail from -Bsymbolic-functions being missing. at some point I may review whether this should just go in the Makefile...
2012-06-07 00:45:52 +00:00
LDFLAGS_AUTO=
configure: work around compilers that merely warn for unknown options some compilers (such as clang) accept unknown options without error, but then print warnings on each invocation, cluttering the build output and burying meaningful warnings. this patch makes configure's tryflag and tryldflag functions use additional options to turn the unknown-option warnings into errors, if available, but only at check time. these options are not output in config.mak to avoid the risk of spurious build breakage; if they work, they will have already done their job at configure time.
2015-05-28 03:52:22 +00:00
LDFLAGS_TRY=
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
OPTIMIZE_GLOBS=
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
srcdir=
fix "configure --prefix=" and improve path/arg handling in configure previously, empty string was treated as "use default". this is apparently not compatible with standard configure semantics where an empty prefix puts everything under /. the new logic should be a lot cleaner and not suffer from such issues.
2012-11-08 22:20:50 +00:00
prefix=/usr/local/musl
exec_prefix='$(prefix)'
bindir='$(exec_prefix)/bin'
libdir='$(prefix)/lib'
includedir='$(prefix)/include'
syslibdir='/lib'
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
tools=
tool_libs=
follow standard configure behavior for cross compile prefix the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
2016-04-29 23:50:33 +00:00
build=
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
target=
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
optimize=auto
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
debug=no
fix "configure --prefix=" and improve path/arg handling in configure previously, empty string was treated as "use default". this is apparently not compatible with standard configure semantics where an empty prefix puts everything under /. the new logic should be a lot cleaner and not suffer from such issues.
2012-11-08 22:20:50 +00:00
warnings=no
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
visibility=auto
fail configure on --enable-shared if -Bsymbolic-functions doesn't work previously, a warning was issued in this case no matter what, even if --disable-shared was used. now, the default for --enable-shared is changed from "yes" to "auto", and the warning is issued by default, but becomes an error if --enable-shared is used, and the test is suppressed completely if --disable-shared is used.
2014-06-10 16:11:12 +00:00
shared=auto
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
static=yes
add configure check for broken gcc 4.9.0 and possibly other versions this is gcc bug #61144. the broken compiler is detected, but the user must manually work around it. this is partly to avoid complex logic for adding workaround CFLAGS and attempting to recheck with them, and partly for the sake of letting the user know the compiler is broken (since the workaround will result in less-efficient code production). some refactoring was also needed to move the check for gcc outside of the check for whether to build the compiler wrapper.
2014-05-19 14:33:28 +00:00
wrapper=auto
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
gcc_wrapper=no
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
clang_wrapper=no
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
for arg ; do
case "$arg" in
make configure accept -h as an alias for --help
2016-02-03 02:14:09 +00:00
--help|-h) usage ;;
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
--srcdir=*) srcdir=${arg#*=} ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
--prefix=*) prefix=${arg#*=} ;;
--exec-prefix=*) exec_prefix=${arg#*=} ;;
--bindir=*) bindir=${arg#*=} ;;
--libdir=*) libdir=${arg#*=} ;;
--includedir=*) includedir=${arg#*=} ;;
--syslibdir=*) syslibdir=${arg#*=} ;;
--enable-shared|--enable-shared=yes) shared=yes ;;
--disable-shared|--enable-shared=no) shared=no ;;
--enable-static|--enable-static=yes) static=yes ;;
--disable-static|--enable-static=no) static=no ;;
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
--enable-optimize) optimize=yes ;;
--enable-optimize=*) optimize=${arg#*=} ;;
--disable-optimize) optimize=no ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
--enable-debug|--enable-debug=yes) debug=yes ;;
--disable-debug|--enable-debug=no) debug=no ;;
--enable-warnings|--enable-warnings=yes) warnings=yes ;;
--disable-warnings|--enable-warnings=no) warnings=no ;;
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
--enable-visibility|--enable-visibility=yes) visibility=yes ;;
--disable-visibility|--enable-visibility=no) visibility=no ;;
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
--enable-wrapper|--enable-wrapper=yes) wrapper=detect ;;
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
--enable-wrapper=all) wrapper=yes ; gcc_wrapper=yes ; clang_wrapper=yes ;;
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
--enable-wrapper=gcc) wrapper=yes ; gcc_wrapper=yes ;;
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
--enable-wrapper=clang) wrapper=yes ; clang_wrapper=yes ;;
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
--disable-wrapper|--enable-wrapper=no) wrapper=no ;;
--enable-gcc-wrapper|--enable-gcc-wrapper=yes) wrapper=yes ; gcc_wrapper=yes ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
--disable-gcc-wrapper|--enable-gcc-wrapper=no) wrapper=no ;;
fix redundant processing of --build flag in configure script The --build flag is listed in two case statement entries in configure, which causes the second entry to be ignored. This patch removes it from the first entry. Signed-off-by: Michael LeMay <michael.lemay@intel.com>
2016-05-04 03:29:42 +00:00
--enable-*|--disable-*|--with-*|--without-*|--*dir=*) ;;
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
--host=*|--target=*) target=${arg#*=} ;;
follow standard configure behavior for cross compile prefix the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
2016-04-29 23:50:33 +00:00
--build=*) build=${arg#*=} ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
-* ) echo "$0: unknown option $arg" ;;
CC=*) CC=${arg#*=} ;;
CFLAGS=*) CFLAGS=${arg#*=} ;;
CPPFLAGS=*) CPPFLAGS=${arg#*=} ;;
LDFLAGS=*) LDFLAGS=${arg#*=} ;;
support configuring cross compiling with CROSS_COMPILE prefix variable
2012-08-15 02:50:16 +00:00
CROSS_COMPILE=*) CROSS_COMPILE=${arg#*=} ;;
add LIBCC (compiler runtime) logic and override to configure this should both fix the issue with ARM needing -lgcc_eh (although that's really a bug in the libgcc build process that's causing considerable bloat, which should be fixed) and make it easier to build musl using clang/llvm in place of gcc. unfortunately I don't know a good way to detect and support pcc's -lpcc since it's not in pcc's default library search path...
2012-09-10 19:30:52 +00:00
LIBCC=*) LIBCC=${arg#*=} ;;
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
*=*) ;;
follow standard configure behavior for cross compile prefix the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
2016-04-29 23:50:33 +00:00
*) build=$arg ; target=$arg ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
esac
done
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
for i in srcdir prefix exec_prefix bindir libdir includedir syslibdir ; do
fix "configure --prefix=" and improve path/arg handling in configure previously, empty string was treated as "use default". this is apparently not compatible with standard configure semantics where an empty prefix puts everything under /. the new logic should be a lot cleaner and not suffer from such issues.
2012-11-08 22:20:50 +00:00
stripdir $i
done
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
#
# Get the source dir for out-of-tree builds
#
if test -z "$srcdir" ; then
srcdir="${0%/configure}"
stripdir srcdir
fi
abs_builddir="$(pwd)" || fail "$0: cannot determine working directory"
abs_srcdir="$(cd $srcdir && pwd)" || fail "$0: invalid source directory $srcdir"
test "$abs_srcdir" = "$abs_builddir" && srcdir=.
test "$srcdir" != "." -a -f Makefile -a ! -h Makefile && fail "$0: Makefile already exists in the working directory"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
# Get a temp filename we can use
#
i=0
set -C
while : ; do i=$(($i+1))
tmpc="./conf$$-$PPID-$i.c"
fix error in configure script using >/dev/null in noclobber mode
2012-11-19 04:15:47 +00:00
2>|/dev/null > "$tmpc" && break
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
test "$i" -gt 50 && fail "$0: cannot create temporary file $tmpc"
done
set +C
trap 'rm "$tmpc"' EXIT INT QUIT TERM HUP
follow standard configure behavior for cross compile prefix the standard configure interface, which our configure script tries to implement, identifies cross compiling (build != host) and searches for the properly-prefixed cross tools. our script was not doing that, forcing users to explicitly provide either CC or a CROSS_COMPILE tool prefix, and the more common choice, just providing CC, was incomplete because the Makefile would still invoke the native ar and ranlib programs. this happened to work when building on ELF-based systems with GNU binutils, but could easily fail when cross-compiling from dissimilar systems. like before, and like the standard configure behavior, an explicit CC or CROSS_COMPILE variable on the command line or in the environment overrides the automatic prefixing.
2016-04-29 23:50:33 +00:00
#
# Check whether we are cross-compiling, and set a default
# CROSS_COMPILE prefix if none was provided.
#
test "$target" && \
test "$target" != "$build" && \
test -z "$CROSS_COMPILE" && \
CROSS_COMPILE="$target-"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
# Find a C compiler to use
#
printf "checking for C compiler... "
support configuring cross compiling with CROSS_COMPILE prefix variable
2012-08-15 02:50:16 +00:00
trycc ${CROSS_COMPILE}gcc
trycc ${CROSS_COMPILE}c99
trycc ${CROSS_COMPILE}cc
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
printf "%s\n" "$CC"
test -n "$CC" || { echo "$0: cannot find a C compiler" ; exit 1 ; }
add configure check for working compiler without this, broken choices of CC/CPPFLAGS/CFLAGS don't show up until late in the configure process where they are confusingly reported as a different failure such as incorrect long double type.
2014-05-12 18:22:57 +00:00
printf "checking whether C compiler works... "
echo "typedef int x;" > "$tmpc"
if output=$($CC $CPPFLAGS $CFLAGS -c -o /dev/null "$tmpc" 2>&1) ; then
printf "yes\n"
else
printf "no; compiler output follows:\n%s\n" "$output"
exit 1
fi
configure: work around compilers that merely warn for unknown options some compilers (such as clang) accept unknown options without error, but then print warnings on each invocation, cluttering the build output and burying meaningful warnings. this patch makes configure's tryflag and tryldflag functions use additional options to turn the unknown-option warnings into errors, if available, but only at check time. these options are not output in config.mak to avoid the risk of spurious build breakage; if they work, they will have already done their job at configure time.
2015-05-28 03:52:22 +00:00
#
# Figure out options to force errors on unknown flags.
#
tryflag CFLAGS_TRY -Werror=unknown-warning-option
tryflag CFLAGS_TRY -Werror=unused-command-line-argument
tryldflag LDFLAGS_TRY -Werror=unknown-warning-option
tryldflag LDFLAGS_TRY -Werror=unused-command-line-argument
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
# Need to know if the compiler is gcc or clang to decide which toolchain
# wrappers to build.
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
printf "checking for C compiler family... "
cc_ver="$(LC_ALL=C $CC -v 2>&1)"
cc_family=unknown
if fnmatch '*gcc\ version*' "$cc_ver" ; then
cc_family=gcc
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
elif fnmatch '*clang\ version*' "$cc_ver" ; then
cc_family=clang
add configure check for broken gcc 4.9.0 and possibly other versions this is gcc bug #61144. the broken compiler is detected, but the user must manually work around it. this is partly to avoid complex logic for adding workaround CFLAGS and attempting to recheck with them, and partly for the sake of letting the user know the compiler is broken (since the workaround will result in less-efficient code production). some refactoring was also needed to move the check for gcc outside of the check for whether to build the compiler wrapper.
2014-05-19 14:33:28 +00:00
fi
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
echo "$cc_family"
add configure check for broken gcc 4.9.0 and possibly other versions this is gcc bug #61144. the broken compiler is detected, but the user must manually work around it. this is partly to avoid complex logic for adding workaround CFLAGS and attempting to recheck with them, and partly for the sake of letting the user know the compiler is broken (since the workaround will result in less-efficient code production). some refactoring was also needed to move the check for gcc outside of the check for whether to build the compiler wrapper.
2014-05-19 14:33:28 +00:00
#
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
# Figure out toolchain wrapper to build
add configure check for broken gcc 4.9.0 and possibly other versions this is gcc bug #61144. the broken compiler is detected, but the user must manually work around it. this is partly to avoid complex logic for adding workaround CFLAGS and attempting to recheck with them, and partly for the sake of letting the user know the compiler is broken (since the workaround will result in less-efficient code production). some refactoring was also needed to move the check for gcc outside of the check for whether to build the compiler wrapper.
2014-05-19 14:33:28 +00:00
#
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
if test "$wrapper" = auto -o "$wrapper" = detect ; then
build: fix musl-targeting toolchain test the old test was broken in that it would never fail on a toolchains built without dynamic linking support, leading to the wrapper script possibly being installed on compilers that do not support it. in addition, the new test is portable across compilers: the old test only worked on GCC. the new test works by testing whether the toolchain libc defines __GLIBC__: most non-musl Linux libc's do define this for compatibility even when they are not glibc, so this is a safe bet to check for musl. in addition, the compiler runtime would need to have a somewhat glibc-compatible ABI in the first place, so any non-glibc compatible libc's compiler runtime might not work. it is safer to disable these cases by default and have the user enable the wrappers manually there using --enable-wrapper if they certain it works.
2015-06-28 21:08:20 +00:00
echo "#include <stdlib.h>" > "$tmpc"
echo "#if ! __GLIBC__" >> "$tmpc"
echo "#error no" >> "$tmpc"
echo "#endif" >> "$tmpc"
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
printf "checking for toolchain wrapper to build... "
build: fix musl-targeting toolchain test the old test was broken in that it would never fail on a toolchains built without dynamic linking support, leading to the wrapper script possibly being installed on compilers that do not support it. in addition, the new test is portable across compilers: the old test only worked on GCC. the new test works by testing whether the toolchain libc defines __GLIBC__: most non-musl Linux libc's do define this for compatibility even when they are not glibc, so this is a safe bet to check for musl. in addition, the compiler runtime would need to have a somewhat glibc-compatible ABI in the first place, so any non-glibc compatible libc's compiler runtime might not work. it is safer to disable these cases by default and have the user enable the wrappers manually there using --enable-wrapper if they certain it works.
2015-06-28 21:08:20 +00:00
if test "$wrapper" = auto && ! $CC -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
echo "none"
elif test "$cc_family" = gcc ; then
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
gcc_wrapper=yes
build: fix musl-targeting toolchain test the old test was broken in that it would never fail on a toolchains built without dynamic linking support, leading to the wrapper script possibly being installed on compilers that do not support it. in addition, the new test is portable across compilers: the old test only worked on GCC. the new test works by testing whether the toolchain libc defines __GLIBC__: most non-musl Linux libc's do define this for compatibility even when they are not glibc, so this is a safe bet to check for musl. in addition, the compiler runtime would need to have a somewhat glibc-compatible ABI in the first place, so any non-glibc compatible libc's compiler runtime might not work. it is safer to disable these cases by default and have the user enable the wrappers manually there using --enable-wrapper if they certain it works.
2015-06-28 21:08:20 +00:00
echo "gcc"
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
elif test "$cc_family" = clang ; then
clang_wrapper=yes
echo "clang"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
else
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
echo "none"
if test "$wrapper" = detect ; then
fail "$0: could not find an appropriate toolchain wrapper"
fi
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
fi
fi
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
if test "$gcc_wrapper" = yes ; then
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
tools="$tools obj/musl-gcc"
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
tool_libs="$tool_libs lib/musl-gcc.specs"
fi
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
if test "$clang_wrapper" = yes ; then
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
tools="$tools obj/musl-clang obj/ld.musl-clang"
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
fi
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
# Find the target architecture
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
printf "checking target system type... "
use $CC rather than "$CC" in configure script this is necessary to allow $CC with arguments in it
2012-10-19 03:02:53 +00:00
test -n "$target" || target=$($CC -dumpmachine 2>/dev/null) || target=unknown
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
printf "%s\n" "$target"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
# Convert to just ARCH
#
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
case "$target" in
improve configure's target arch matching most notably, it was failing to match sh4-*, etc., but in general the explicit matching of hyphens for some archs was problematic because it failed to accept simply the musl-style arch name (without a gcc-style tuple) as an input. the original motivation of matching hyphens was to prevent incorrectly identifying a 64-bit arch as the corresponding 32-bit arch (e.g. mips* matching mips64) but this is easily fixed by simply checking (and for now, rejecting as unsupported) the relevant 64-bit archs.
2014-02-28 18:12:40 +00:00
# Catch these early to simplify matching for 32-bit archs
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
arm*) ARCH=arm ;;
add aarch64 port This adds complete aarch64 target support including bigendian subarch. Some of the long double math functions are known to be broken otherwise interfaces should be fully functional, but at this point consider this port experimental. Initial work on this port was done by Sireesh Tripurari and Kevin Bortis.
2015-03-10 21:18:41 +00:00
aarch64*) ARCH=aarch64 ;;
add arch tuple matching for nt32 and nt64 in configure the nt32 and nt64 archs will be provided by the midipix project for building musl on top of its posix-like syscall layer for windows. at present the needed arch files are in a separate repository, but having the tuple matching in the upstream configure script should make it possible to overlay the arch files without needing any further patching.
2016-02-19 05:10:23 +00:00
i?86-nt32*) ARCH=nt32 ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
i?86*) ARCH=i386 ;;
make configure accept alternate gcc tuples for x32 the previous pattern required "x32" to be used as the second field of the gcc tuple, which is usually reserved for vendor use and not appropriate as an ABI specifier. with this change, putting "x32" at the end of the tuple, the way ABI specifiers are normally done, is also permitted.
2014-03-17 21:38:22 +00:00
x86_64-x32*|x32*|x86_64*x32) ARCH=x32 ;;
add arch tuple matching for nt32 and nt64 in configure the nt32 and nt64 archs will be provided by the midipix project for building musl on top of its posix-like syscall layer for windows. at present the needed arch files are in a separate repository, but having the tuple matching in the upstream configure script should make it possible to overlay the arch files without needing any further patching.
2016-02-19 05:10:23 +00:00
x86_64-nt64*) ARCH=nt64 ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
x86_64*) ARCH=x86_64 ;;
configure: handle mipsisa64* triplet as a mips64 target the gnu config.sub script recognizes several mipsisa64* cpu types that musl supports as mips64 targets.
2016-08-24 10:40:10 +00:00
mips64*|mipsisa64*) ARCH=mips64 ;;
improve configure's target arch matching most notably, it was failing to match sh4-*, etc., but in general the explicit matching of hyphens for some archs was problematic because it failed to accept simply the musl-style arch name (without a gcc-style tuple) as an input. the original motivation of matching hyphens was to prevent incorrectly identifying a 64-bit arch as the corresponding 32-bit arch (e.g. mips* matching mips64) but this is easily fixed by simply checking (and for now, rejecting as unsupported) the relevant 64-bit archs.
2014-02-28 18:12:40 +00:00
mips*) ARCH=mips ;;
microblaze*) ARCH=microblaze ;;
add or1k (OpenRISC 1000) architecture port With the exception of a fenv implementation, the port is fully featured. The port has been tested in or1ksim, the golden reference functional simulator for OpenRISC 1000. It passes all libc-test tests (except the math tests that requires a fenv implementation). The port assumes an or1k implementation that has support for atomic instructions (l.lwa/l.swa). Although it passes all the libc-test tests, the port is still in an experimental state, and has yet experienced very little 'real-world' use.
2014-07-17 19:09:10 +00:00
or1k*) ARCH=or1k ;;
add powerpc64 port
2016-05-01 00:18:17 +00:00
powerpc64*) ARCH=powerpc64 ;;
improve configure's target arch matching most notably, it was failing to match sh4-*, etc., but in general the explicit matching of hyphens for some archs was problematic because it failed to accept simply the musl-style arch name (without a gcc-style tuple) as an input. the original motivation of matching hyphens was to prevent incorrectly identifying a 64-bit arch as the corresponding 32-bit arch (e.g. mips* matching mips64) but this is easily fixed by simply checking (and for now, rejecting as unsupported) the relevant 64-bit archs.
2014-02-28 18:12:40 +00:00
powerpc*) ARCH=powerpc ;;
sh[1-9bel-]*|sh|superh*) ARCH=sh ;;
fix configure build/host/target terminology usage
2012-06-03 20:22:13 +00:00
unknown) fail "$0: unable to detect target arch; try $0 --target=..." ;;
*) fail "$0: unknown or unsupported target \"$target\"" ;;
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
esac
#
# Try to get a conforming C99 freestanding environment
#
tryflag CFLAGS_C99FSE -std=c99
tryflag CFLAGS_C99FSE -nostdinc
tryflag CFLAGS_C99FSE -ffreestanding \
|| tryflag CFLAGS_C99FSE -fno-builtin
tryflag CFLAGS_C99FSE -fexcess-precision=standard \
configure: only use -ffloat-store on i386 this option is expensive and only used on old gcc's that lack -fexcess-precision=standed, but it's not needed on non-i386 archs where floating point does not have excess precision anyway. if musl ever supports m68k, i think it will need to be special-cased too. i'm not aware of any other archs with excess precision.
2012-07-04 03:53:05 +00:00
|| { test "$ARCH" = i386 && tryflag CFLAGS_C99FSE -ffloat-store ; }
add -frounding-math to build
2012-05-05 21:18:31 +00:00
tryflag CFLAGS_C99FSE -frounding-math
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
add attribute((may_alias)) checking in configure this will be needed for upcoming commits to the string/mem functions to correct their unannounced use of aliasing violations for word-at-a-time search, fill, and copy operations.
2013-08-27 21:33:47 +00:00
#
# We may use the may_alias attribute if __GNUC__ is defined, so
# if the compiler defines __GNUC__ but does not provide it,
# it must be defined away as part of the CFLAGS.
#
printf "checking whether compiler needs attribute((may_alias)) suppression... "
cat > "$tmpc" <<EOF
typedef int
#ifdef __GNUC__
__attribute__((__may_alias__))
#endif
x;
EOF
remove unneeded -I options from configure test for may_alias attribute this test does not include anything, so the -I options are not useful and are just a maintenance burden if paths change.
2016-01-28 00:01:21 +00:00
if $CC $CFLAGS_C99FSE $CPPFLAGS $CFLAGS \
add attribute((may_alias)) checking in configure this will be needed for upcoming commits to the string/mem functions to correct their unannounced use of aliasing violations for word-at-a-time search, fill, and copy operations.
2013-08-27 21:33:47 +00:00
-c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "no\n"
else
printf "yes\n"
CFLAGS_C99FSE="$CFLAGS_C99FSE -D__may_alias__="
fi
prevent user CFLAGS overrides from exposing executable stack the option to suppress executable stack tagging was placed in CFLAGS, which is treated as optional and overridable by the build system. if a user replaces CFLAGS after configure has run, it could get lost, resulting in a libc.so that's flagged as needing executable stack, which would cause the kernel to map the initial stack as executable. move -Wa,--noexecstack to CFLAGS_C99FSE, the make variable used for mandatory compiler options.
2015-10-23 04:01:01 +00:00
#
# The GNU toolchain defaults to assuming unmarked files need an
# executable stack, potentially exposing vulnerabilities in programs
# linked with such object files. Fix this.
#
tryflag CFLAGS_C99FSE -Wa,--noexecstack
allow libc itself to be built with stack protector enabled this was already essentially possible as a result of the previous commits changing the dynamic linker/thread pointer bootstrap process. this commit mainly adds build system infrastructure: configure no longer attempts to disable stack protector. instead it simply determines how so the makefile can disable stack protector for a few translation units used during early startup. stack protector is also disabled for memcpy and memset since compilers (incorrectly) generate calls to them on some archs to implement struct initialization and assignment, and such calls may creep into early initialization. no explicit attempt to enable stack protector is made by configure at this time; any stack protector option supported by the compiler can be passed to configure in CFLAGS, and if the compiler uses stack protector by default, this default is respected.
2015-04-14 00:13:10 +00:00
#
# Check for options to disable stack protector, which needs to be
# disabled for a few early-bootstrap translation units. If not found,
# this is not an error; we assume the toolchain does not do ssp.
#
tryflag CFLAGS_NOSSP -fno-stack-protector
work around gcc 4.8's generation of self-referential mem* functions at -O3
2013-08-01 21:12:23 +00:00
#
# Check for options that may be needed to prevent the compiler from
# generating self-referential versions of memcpy,, memmove, memcmp,
# and memset. Really, we should add a check to determine if this
# option is sufficient, and if not, add a macro to cripple these
# functions with volatile...
#
tryflag CFLAGS_MEMOPS -fno-tree-loop-distribute-patterns
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
#
remove optimization-inhibiting behavior from configure's --enable-debug this behavior turned out to be counter-intuitive to users and in any case it's unnecessary. optimization can be disabled explicitly using the --disable-optimize option, or both can be achieved without any enable/disable options by passing CFLAGS="-O0 -g".
2014-06-20 20:10:48 +00:00
# Enable debugging if requessted.
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
#
remove optimization-inhibiting behavior from configure's --enable-debug this behavior turned out to be counter-intuitive to users and in any case it's unnecessary. optimization can be disabled explicitly using the --disable-optimize option, or both can be achieved without any enable/disable options by passing CFLAGS="-O0 -g".
2014-06-20 20:10:48 +00:00
test "$debug" = yes && CFLAGS_AUTO=-g
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
Build process uses script to add CFI directives to x86 asm Some functions implemented in asm need to use EBP for purposes other than acting as a frame pointer. (Notably, it is used for the 6th argument to syscalls with 6 arguments.) Without frame pointers, GDB can only show backtraces if it gets CFI information from a .debug_frame or .eh_frame ELF section. Rather than littering our asm with ugly .cfi directives, use an awk script to insert them in the right places during the build process, so GDB can keep track of where the current stack frame is relative to the stack pointer. This means GDB can produce beautiful stack traces at any given point when single-stepping through asm functions. Additionally, when registers are saved on the stack and later overwritten, emit ..cfi directives so GDB will know where they were saved relative to the stack pointer. This way, when you look back up the stack from within an asm function, you can still reliably print the values of local variables in the caller. If this awk script were to understand every possible wild and crazy contortion that an asm programmer can do with the stack and registers, and always emit the exact ..cfi directives needed for GDB to know what the register values were in the preceding stack frame, it would necessarily be as complex as a full x86 emulator. That way lies madness. Hence, we assume that the stack pointer will _only_ ever be adjusted using push/pop or else add/sub with a constant. We do not attempt to detect every possible way that a register value could be saved for later use, just the simple and common ways. Thanks to Szabolcs Nagy for suggesting numerous improvements to this code.
2015-07-10 13:03:24 +00:00
#
# Preprocess asm files to add extra debugging information if debug is
# enabled, our assembler supports the needed directives, and the
# preprocessing script has been written for our architecture.
#
printf "checking whether we should preprocess assembly to add debugging information... "
if fnmatch '-g*|*\ -g*' "$CFLAGS_AUTO $CFLAGS" &&
test -f "tools/add-cfi.$ARCH.awk" &&
printf ".file 1 \"srcfile.s\"\n.line 1\n.cfi_startproc\n.cfi_endproc" | $CC -g -x assembler -c -o /dev/null 2>/dev/null -
then
ADD_CFI=yes
else
ADD_CFI=no
fi
printf "%s\n" "$ADD_CFI"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
# Possibly add a -O option to CFLAGS and select modules to optimize with
# -O3 based on the status of --enable-optimize and provided CFLAGS.
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
printf "checking for optimization settings... "
case "x$optimize" in
xauto)
if fnmatch '-O*|*\ -O*' "$CFLAGS_AUTO $CFLAGS" ; then
printf "using provided CFLAGS\n" ;optimize=no
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
else
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
printf "using defaults\n" ; optimize=yes
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
fi
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
;;
xsize|xnone) printf "minimize size\n" ; optimize=size ;;
xno|x) printf "disabled\n" ; optimize=no ;;
*) printf "custom\n" ;;
esac
test "$optimize" = no || tryflag CFLAGS_AUTO -Os || tryflag CFLAGS_AUTO -O2
do not include math modules in the default -O3 optimization set it's not clear that -O3 helps them, and gcc seems to have floating point optimization bugs that introduce additional failures when -O3 is used on some of these files.
2013-07-25 03:21:45 +00:00
test "$optimize" = yes && optimize="internal,malloc,string"
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
if fnmatch 'no|size' "$optimize" ; then :
else
printf "components to be optimized for speed:"
while test "$optimize" ; do
case "$optimize" in
*,*) this=${optimize%%,*} optimize=${optimize#*,} ;;
*) this=$optimize optimize=
esac
printf " $this"
case "$this" in
*/*.c) ;;
*/*) this=$this*.c ;;
*) this=$this/*.c ;;
esac
OPTIMIZE_GLOBS="$OPTIMIZE_GLOBS $this"
done
OPTIMIZE_GLOBS=${OPTIMIZE_GLOBS# }
printf "\n"
fi
# Always try -pipe
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
tryflag CFLAGS_AUTO -pipe
#
get rid of eh_frame bloat if needed for debugging, it will be output in the .debug_frame section instead, where it is not part of the loaded program and where the strip command is free to strip it.
2012-08-29 13:36:02 +00:00
# If debugging is disabled, omit frame pointer. Modern GCC does this
# anyway on most archs even when debugging is enabled since the frame
# pointer is no longer needed for debugging.
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
if fnmatch '-g*|*\ -g*' "$CFLAGS_AUTO $CFLAGS" ; then :
else
tryflag CFLAGS_AUTO -fomit-frame-pointer
fi
get rid of eh_frame bloat if needed for debugging, it will be output in the .debug_frame section instead, where it is not part of the loaded program and where the strip command is free to strip it.
2012-08-29 13:36:02 +00:00
#
# Modern GCC wants to put DWARF tables (used for debugging and
# unwinding) in the loaded part of the program where they are
# unstrippable. These options force them back to debug sections (and
# cause them not to get generated at all if debugging is off).
#
tryflag CFLAGS_AUTO -fno-unwind-tables
tryflag CFLAGS_AUTO -fno-asynchronous-unwind-tables
have configure check/add -ffunction-sections and -fdata-sections based on patch by Denys Vlasenko. the original intent for using these options was to enable linking optimizations. these are immediately available for static linking applications to libc.a, and will also be used for linking libc.so in a subsequent commit. in addition to the original motives, this change works around a whole class of toolchain bugs where the compiler generates relative address expressions using a weak symbol and the assembler "optimizes out" the relocation which should result by using the weak definition. (see gas pr 18561 and gcc pr 66609, 68178, etc. for examples.) by having different functions and data objects in their own sections, all relative address expressions are cross-section and thus cannot be resolved to constants until link time. this allows us to retain support for affected compiler/assembler versions without invasive and fragile source-level workarounds.
2015-11-04 18:24:11 +00:00
#
# Attempt to put each function and each data object in its own
# section. This both allows additional size optimizations at link
# time and works around a dangerous class of compiler/assembler bugs
# whereby relative address expressions are constant-folded by the
# assembler even when one or more of the symbols involved is
# replaceable. See gas pr 18561 and gcc pr 66609, 68178, etc.
#
tryflag CFLAGS_AUTO -ffunction-sections
tryflag CFLAGS_AUTO -fdata-sections
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
# On x86, make sure we don't have incompatible instruction set
# extensions enabled by default. This is bad for making static binaries.
# We cheat and use i486 rather than i386 because i386 really does not
# work anyway (issues with atomic ops).
configure: check for -march and -mtune passed via CC Some build environments pass -march and -mtune as part of CC, therefore update configure to check both CC and CFLAGS before making the decision to fall back to generic -march and -mtune options for x86. Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
2015-04-21 17:34:05 +00:00
# Some build environments pass -march and -mtune options via CC, so
# check both CC and CFLAGS.
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
#
if test "$ARCH" = "i386" ; then
configure: check for -march and -mtune passed via CC Some build environments pass -march and -mtune as part of CC, therefore update configure to check both CC and CFLAGS before making the decision to fall back to generic -march and -mtune options for x86. Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
2015-04-21 17:34:05 +00:00
fnmatch '-march=*|*\ -march=*' "$CC $CFLAGS" || tryldflag CFLAGS_AUTO -march=i486
fnmatch '-mtune=*|*\ -mtune=*' "$CC $CFLAGS" || tryldflag CFLAGS_AUTO -mtune=generic
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
fi
treat invalid C as an error even if warnings aren't enabled.
2012-12-12 04:28:31 +00:00
#
# Even with -std=c99, gcc accepts some constructs which are constraint
# violations. We want to treat these as errors regardless of whether
# other purely stylistic warnings are enabled -- especially implicit
# function declarations, which are a dangerous programming error.
#
tryflag CFLAGS_AUTO -Werror=implicit-function-declaration
tryflag CFLAGS_AUTO -Werror=implicit-int
tryflag CFLAGS_AUTO -Werror=pointer-sign
tryflag CFLAGS_AUTO -Werror=pointer-arith
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
if test "x$warnings" = xyes ; then
tryflag CFLAGS_AUTO -Wall
tryflag CFLAGS_AUTO -Wno-parentheses
tryflag CFLAGS_AUTO -Wno-uninitialized
tryflag CFLAGS_AUTO -Wno-missing-braces
tryflag CFLAGS_AUTO -Wno-unused-value
tryflag CFLAGS_AUTO -Wno-unused-but-set-variable
tryflag CFLAGS_AUTO -Wno-unknown-pragmas
configure: suppress bogus pointer-int cast warnings
2014-01-08 02:11:46 +00:00
tryflag CFLAGS_AUTO -Wno-pointer-to-int-cast
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
fi
fix syntax errors in configure script
2015-04-23 02:11:48 +00:00
if test "x$visibility" = xauto ; then
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
# This test checks toolchain support for several things:
# - the -include option
# - the attributes/pragmas used in vis.h
# - linking code that takes the address of protected symbols
eliminate protected-visibility data in libc.so with vis.h preinclude some newer binutils versions print scary warnings about protected data because most gcc versions fail to produce the right address references/relocations for such data that might be subject to copy relocations. originally vis.h explicitly assigned default visibility to all public data symbols to avoid this issue, but commit b8dda24fe1caa901a99580f7a52defb95aedb67c removed this treatment for stdin/out/err to work around a gcc 3.x bug, and since they don't actually need it (because taking their addresses is not valid C). instead, a check for the gcc 3.x bug is added to the configure check for vis.h preinclude support; this feature will simply be disabled when using a buggy version of gcc.
2015-09-29 02:44:05 +00:00
# - gcc 3.x bug that wrongly claims declarations mismatch
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
printf "checking whether global visibility preinclude works... "
eliminate protected-visibility data in libc.so with vis.h preinclude some newer binutils versions print scary warnings about protected data because most gcc versions fail to produce the right address references/relocations for such data that might be subject to copy relocations. originally vis.h explicitly assigned default visibility to all public data symbols to avoid this issue, but commit b8dda24fe1caa901a99580f7a52defb95aedb67c removed this treatment for stdin/out/err to work around a gcc 3.x bug, and since they don't actually need it (because taking their addresses is not valid C). instead, a check for the gcc 3.x bug is added to the configure check for vis.h preinclude support; this feature will simply be disabled when using a buggy version of gcc.
2015-09-29 02:44:05 +00:00
cat > "$tmpc" <<EOF
__attribute__((__visibility__("default")))
extern struct a *const x;
typedef struct a b;
extern b *const x;
b *const x;
int (*fp)(void);
int foo(void) { }
int bar(void) { fp = foo; return foo(); }
EOF
fix regression in configure script with new visibility option commit de2b67f8d41e08caa56bf6540277f6561edb647f introduced a regression by adding a -include option to CFLAGS_AUTO which did not work without additional -I options. this broke subsequent trycppif tests and caused x86_64 to be misdetected as x32, among other issues. simply using the full relative pathname to vis.h rather than -I is the cleanest way to fix the problem.
2015-04-20 22:14:19 +00:00
if $CC $CFLAGS_C99FSE $CPPFLAGS $CFLAGS \
fix global visibility (vis.h) support for out-of-tree builds commit 2f853dd6b9a95d5b13ee8f9df762125e0588df5d failed to change the test for -include vis.h support to use $srcdir, so vis.h was always disabled by configure for out-of-tree builds.
2016-01-20 19:43:37 +00:00
-DSHARED -fPIC -I$srcdir/src/internal -include vis.h \
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
-nostdlib -shared -Wl,-Bsymbolic-functions \
-o /dev/null "$tmpc" >/dev/null 2>&1 ; then
visibility=yes
else
visibility=no
fi
printf "%s\n" "$visibility"
fi
fix syntax errors in configure script
2015-04-23 02:11:48 +00:00
if test "x$visibility" = xyes ; then
make configure check for visibility preinclude compatible with pcc pcc does not search for -include relative to the working directory unless -I. is used. rather than adding -I., which could be problematic if there's extra junk in the top-level directory, switch back to the old method (reverting commit 60ed988fd6c67b489d7cc186ecaa9db4e5c25b8c) of using -include vis.h and relying on -I./src/internal being present on the command line (which the Makefile guarantees). to fix the breakage that was present in trycppif checks with the old method, $CFLAGS_AUTO is removed from the command line passed to trycppif; this is valid since $CFLAGS_AUTO should not contain options that alter compiler semantics or ABI, only optimizations, warnings, etc.
2015-04-22 05:41:00 +00:00
CFLAGS_AUTO="$CFLAGS_AUTO -include vis.h"
add optional global visibility override this is implemented via the build system and does not affect source files. the idea is to use protected or hidden visibility to prevent the compiler from pessimizing function calls within a shared (or position-independent static) libc in the form of overhead setting up for a call through the PLT. the ld-time symbol binding via the -Bsymbolic-functions option already optimized out the PLT itself, but not the code in the caller needed to support a call through the PLT. on some archs this overhead can be substantial; on others it's trivial.
2015-04-20 02:05:29 +00:00
CFLAGS_AUTO="${CFLAGS_AUTO# }"
fi
use same object files for libc.a and libc.so if compiler produces PIC now that .lo and .o files differ only by whether -fPIC is passed (and no longer at the source level based on the SHARED macro), it's possible to use the same object files for both static and shared libc when the compiler would produce PIC for the static files anyway. this happens if the user has included -fPIC in their CFLAGS or if the compiler has been configured to produce PIE by default. we use the .lo files for both, and still append -fPIC to the CFLAGS, rather than using the .o files so that libc.so does not break catastrophically if the user later removes -fPIC from CFLAGS in config.mak or on the make command line. this also ensures that we get full -fPIC in case -fpic, -fPIE, or some other lesser-PIC option was passed in CFLAGS.
2016-01-26 00:57:38 +00:00
# Determine if the compiler produces position-independent code (PIC)
# by default. If so, we don't need to compile separate object files
# for libc.a and libc.so.
if trycppif __PIC__ "$CFLAGS_C99FSE $CPPFLAGS $CFLAGS" ; then
pic_default=yes
else
pic_default=no
fi
have configure check/add linker options to reduce size lost to padding based on patch by Denys Vlasenko. sorting sections and common data symbols by alignment acts as an approximation for optimal packing, which the linker does not actually support.
2015-11-05 02:39:13 +00:00
# Reduce space lost to padding for alignment purposes by sorting data
# objects according to their alignment reqirements. This approximates
# optimal packing.
tryldflag LDFLAGS_AUTO -Wl,--sort-section,alignment
tryldflag LDFLAGS_AUTO -Wl,--sort-common
have configure check/add --gc-sections linker option this allowing the linker to drop certain weak definitions that are only used as dummies for static linking. they could be eliminated for shared library builds using the preprocessor instead, but we are trying to transition to using the same object files for shared and static libc, so a link-time solution is preferable.
2015-11-05 02:40:36 +00:00
# When linking shared library, drop dummy weak definitions that were
# replaced by strong definitions from other translation units.
tryldflag LDFLAGS_AUTO -Wl,--gc-sections
make configure try to disable stack protector in theory we could support stack protector in the libc itself, and users wanting to experiment with such usage could add -fstack-protector to CFLAGS intentionally. but to avoid breakage in the default case, override broken distro-patched gcc that forces stack protector on.
2012-06-07 02:00:08 +00:00
# Some patched GCC builds have these defaults messed up...
add gnu hash support in the dynamic linker based on the patches contributed by boris brezillon.
2012-08-25 21:13:28 +00:00
tryldflag LDFLAGS_AUTO -Wl,--hash-style=both
add configure check for gnu linker hash style setting some broken distro-provided toolchains have modified gcc to produce only "gnu hash" dynamic hash table by default. as this is unsupported by musl, that results in a non-working libc.so. we detect and switch this on in configure rather than hard-coding it in the Makefile because it's not supported by old binutils versions, but that might not even be relevant since old binutils versions already fail from -Bsymbolic-functions being missing. at some point I may review whether this should just go in the Makefile...
2012-06-07 00:45:52 +00:00
try to suppress linking libc.so if there are undefined symbols this is always an error and usually results from failure to find/link the compiler runtime library, but it could also result from implementation errors in libc, using functions that don't (yet) exist. either way the resulting libc.so will crash mysteriously at runtime. the crash happens too early to produce a meaningful error, so these crashes are very confusing to users and waste a lot of debugging time. this commit should ensure that they do not happen.
2015-09-22 15:45:40 +00:00
# Prevent linking if there are undefined symbols; if any exist,
# libc.so will crash at runtime during relocation processing.
# The common way this can happen is failure to link the compiler
# runtime library; implementation error is also a possibility.
tryldflag LDFLAGS_AUTO -Wl,--no-undefined
work around toolchains with broken visibility in libgcc/libpcc
2015-11-08 01:23:49 +00:00
# Avoid exporting symbols from compiler runtime libraries. They
# should be hidden anyway, but some toolchains including old gcc
# versions built without shared library support and pcc are broken.
tryldflag LDFLAGS_AUTO -Wl,--exclude-libs=ALL
don't suppress shared libc when linker lacks -Bsymbolic-functions previous work overhauling the dynamic linker made it so that linking libc with -Bsymbolic-functions was no longer mandatory, but the configure logic that forced --disable-shared when ld failed to accept the option was left in place. this commit removes the hard-coded -Bsymbolic-functions from the Makefile and changes the configure test to one that simply adds it to the auto-detected LDFLAGS on success.
2016-01-31 05:40:33 +00:00
# Linking with -Bsymbolic-functions is no longer mandatory for
# the dynamic linker to work, but enable it if it works as
# a linking optimization.
tryldflag LDFLAGS_AUTO -Wl,-Bsymbolic-functions
check for ld support of -Bsymbolic-functions; disable shared if not avail this issue affects the last gpl2 version of binutils, which some people are still using out of aversion to gpl3. musl requires -Bsymbolic-functions because it's the only way to make a libc.so that's able to operate prior to dynamic linking but that still behaves correctly with respect to global vars that may be moved to the main program via copy relocations.
2012-06-07 04:32:22 +00:00
add LIBCC (compiler runtime) logic and override to configure this should both fix the issue with ARM needing -lgcc_eh (although that's really a bug in the libgcc build process that's causing considerable bloat, which should be fixed) and make it easier to build musl using clang/llvm in place of gcc. unfortunately I don't know a good way to detect and support pcc's -lpcc since it's not in pcc's default library search path...
2012-09-10 19:30:52 +00:00
# Find compiler runtime library
test -z "$LIBCC" && tryldflag LIBCC -lgcc && tryldflag LIBCC -lgcc_eh
test -z "$LIBCC" && tryldflag LIBCC -lcompiler_rt
further pcc fixes in configure -lpcc only works if -nostdlib is not passed, so it's useless. instead, use -print-file-name to look up the full pathname for libpcc.a, and check whether that succeeds before trying to link with the result. also, silence pcc's junk printed on stdout during tests.
2012-10-26 22:15:51 +00:00
test -z "$LIBCC" && try_libcc=`$CC -print-file-name=libpcc.a 2>/dev/null` \
&& tryldflag LIBCC "$try_libcc"
add LIBCC (compiler runtime) logic and override to configure this should both fix the issue with ARM needing -lgcc_eh (although that's really a bug in the libgcc build process that's causing considerable bloat, which should be fixed) and make it easier to build musl using clang/llvm in place of gcc. unfortunately I don't know a good way to detect and support pcc's -lpcc since it's not in pcc's default library search path...
2012-09-10 19:30:52 +00:00
printf "using compiler runtime libraries: %s\n" "$LIBCC"
disable dynamic linking on mips for now (broken)
2012-07-12 18:24:10 +00:00
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
# Figure out arch variants for archs with variants
SUBARCH=
make configure check for visibility preinclude compatible with pcc pcc does not search for -include relative to the working directory unless -I. is used. rather than adding -I., which could be problematic if there's extra junk in the top-level directory, switch back to the old method (reverting commit 60ed988fd6c67b489d7cc186ecaa9db4e5c25b8c) of using -include vis.h and relying on -I./src/internal being present on the command line (which the Makefile guarantees). to fix the breakage that was present in trycppif checks with the old method, $CFLAGS_AUTO is removed from the command line passed to trycppif; this is valid since $CFLAGS_AUTO should not contain options that alter compiler semantics or ABI, only optimizations, warnings, etc.
2015-04-22 05:41:00 +00:00
t="$CFLAGS_C99FSE $CPPFLAGS $CFLAGS"
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
configure: check for __ILP32__ if arch is x86_64 otherwise a multilib compiler used with -mx32 will not be detected properly.
2014-03-19 21:31:00 +00:00
if test "$ARCH" = "x86_64" ; then
trycppif __ILP32__ "$t" && ARCH=x32
fi
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
if test "$ARCH" = "arm" ; then
trycppif __ARMEB__ "$t" && SUBARCH=${SUBARCH}eb
fix detection of arm hardfloat it turns out that __SOFTFP__ does not indicate the ABI in use but rather that fpu instructions are not to be used at all. this is specified in ARM's documentation so I'm unclear on how I previously got the wrong idea. unfortunately, this resulted in the 0.9.12 release producing a dynamic linker with the wrong name. fortunately, there do not yet seem to be any public toolchain builds using the wrong name. the __ARM_PCS_VFP macro does not seem to be official from ARM, and in fact it was missing from the very earliest gcc versions (around 4.5.x) that added -mfloat-abi=hard. it would be possible on such versions to perform some ugly linker-based tests instead in hopes that the linker will reject ABI-mismatching object files, if there is demand for supporting such versions. I would probably prefer to document which versions are broken and warn users to manually add -D__ARM_PCS_VFP if using such a version. there's definitely an argument to be made that the fenv macros should be exposed even in -mfloat-abi=softfp mode. for now, I have chosen not to expose them in this case, since the math library will not necessarily have the capability to raise exceptions (it depends on the CFLAGS used to compile it), and since exceptions are officially excluded from the ARM EABI, which the plain "arm" arch aims to follow.
2013-08-16 21:09:07 +00:00
trycppif __ARM_PCS_VFP "$t" && SUBARCH=${SUBARCH}hf
work around regression building for armhf with clang (compiler bug) commit e4355bd6bec89688e8c739cd7b4c76e675643dca moved the math asm from external source files to inline asm, but unfortunately, all current releases of clang use the wrong inline asm constraint codes for float and double ("w" and "P" instead of "t" and "w", respectively). this patch adds detection for the bug in configure, and, for now, just disables the affected asm on broken clang versions.
2016-02-19 01:20:07 +00:00
# Versions of clang up until at least 3.8 have the wrong constraint codes
# for floating point operands to inline asm. Detect this so the affected
# source files can just disable the asm.
if test "$cc_family" = clang ; then
printf "checking whether clang's vfp asm constraints work... "
echo 'float f(float x) { __asm__("":"+t"(x)); return x; }' > "$tmpc"
if $CC $CFLAGS_C99FSE $CPPFLAGS $CFLAGS -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "yes\n"
else
printf "no\n"
CFLAGS_AUTO="$CFLAGS_AUTO -DBROKEN_VFP_ASM"
CFLAGS_AUTO="${CFLAGS_AUTO# }"
fi
fi
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
fi
add aarch64 port This adds complete aarch64 target support including bigendian subarch. Some of the long double math functions are known to be broken otherwise interfaces should be fully functional, but at this point consider this port experimental. Initial work on this port was done by Sireesh Tripurari and Kevin Bortis.
2015-03-10 21:18:41 +00:00
if test "$ARCH" = "aarch64" ; then
trycppif __AARCH64EB__ "$t" && SUBARCH=${SUBARCH}_be
fi
mips: add mips-sf subarch support (soft-float) Userspace emulated floating-point (gcc -msoft-float) is not compatible with the default mips abi (assumes an FPU or in kernel emulation of it). Soft vs hard float abi should not be mixed, __mips_soft_float is checked in musl's configure script and there is no runtime check. The -sf subarch does not save/restore floating-point registers in setjmp/longjmp and only provides dummy fenv implementation.
2014-02-24 22:16:29 +00:00
if test "$ARCH" = "mips" ; then
add support for mips and mips64 r6 isa mips32r6 and mips64r6 are actually new isas at both the asm source and opcode levels (pre-r6 code cannot run on r6) and thus need to be treated as a new subarch. the following changes are made, some of which yield code generation improvements for non-r6 targets too: - add subarch logic in configure script and reloc.h files for dynamic linker name. - suppress use of .set mips2 asm directives (used to allow mips2 atomic instructions on baseline mips1 builds; the kernel has to emulate them on mips1) except when actually needed. they cause wrong instruction encodings on r6, and pessimize inlining on at least some compilers. - only hard-code sync instruction encoding on mips1. - use "ZC" constraint instead of "m" constraint for llsc memory operands on r6, where the ll/sc instructions no longer accept full 16-bit offsets. - only hard-code rdhwr instruction encoding with .word on targets (pre-r2) where it may need trap-and-emulate by the kernel. otherwise, just use the instruction mnemonic, and allow an arbitrary destination register to be used.
2016-04-03 10:42:37 +00:00
trycppif "__mips_isa_rev >= 6" "$t" && SUBARCH=${SUBARCH}r6
mips: add mips-sf subarch support (soft-float) Userspace emulated floating-point (gcc -msoft-float) is not compatible with the default mips abi (assumes an FPU or in kernel emulation of it). Soft vs hard float abi should not be mixed, __mips_soft_float is checked in musl's configure script and there is no runtime check. The -sf subarch does not save/restore floating-point registers in setjmp/longjmp and only provides dummy fenv implementation.
2014-02-24 22:16:29 +00:00
trycppif "_MIPSEL || __MIPSEL || __MIPSEL__" "$t" && SUBARCH=${SUBARCH}el
trycppif __mips_soft_float "$t" && SUBARCH=${SUBARCH}-sf
fi
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
add mips64 port patch by Mahesh Bodapati and Jaydeep Patil of Imagination Technologies.
2016-03-06 17:41:56 +00:00
if test "$ARCH" = "mips64" ; then
add mips n32 port (ILP32 ABI for mips64) based on patch submitted by Jaydeep Patil, with minor changes.
2016-04-18 05:19:13 +00:00
trycppif "_MIPS_SIM != _ABI64" "$t" && ARCH=mipsn32
add support for mips and mips64 r6 isa mips32r6 and mips64r6 are actually new isas at both the asm source and opcode levels (pre-r6 code cannot run on r6) and thus need to be treated as a new subarch. the following changes are made, some of which yield code generation improvements for non-r6 targets too: - add subarch logic in configure script and reloc.h files for dynamic linker name. - suppress use of .set mips2 asm directives (used to allow mips2 atomic instructions on baseline mips1 builds; the kernel has to emulate them on mips1) except when actually needed. they cause wrong instruction encodings on r6, and pessimize inlining on at least some compilers. - only hard-code sync instruction encoding on mips1. - use "ZC" constraint instead of "m" constraint for llsc memory operands on r6, where the ll/sc instructions no longer accept full 16-bit offsets. - only hard-code rdhwr instruction encoding with .word on targets (pre-r2) where it may need trap-and-emulate by the kernel. otherwise, just use the instruction mnemonic, and allow an arbitrary destination register to be used.
2016-04-03 10:42:37 +00:00
trycppif "__mips_isa_rev >= 6" "$t" && SUBARCH=${SUBARCH}r6
add mips64 port patch by Mahesh Bodapati and Jaydeep Patil of Imagination Technologies.
2016-03-06 17:41:56 +00:00
trycppif "_MIPSEL || __MIPSEL || __MIPSEL__" "$t" && SUBARCH=${SUBARCH}el
trycppif __mips_soft_float "$t" && SUBARCH=${SUBARCH}-sf
fi
add powerpc soft-float support Some PowerPC CPUs (e.g. Freescale MPC85xx) have a completely different instruction set for floating point operations (SPE). Executing regular PowerPC floating point instructions results in "Illegal instruction" errors. Make it possible to run these devices in soft-float mode.
2016-01-25 12:20:52 +00:00
if test "$ARCH" = "powerpc" ; then
make configure check for unsupported (SPE) powerpc hard-float models the SPE ABI may be compatible with soft-float, but actually making it work requires some additional work, so for now it's best to make sure broken builds don't happen.
2016-03-06 22:11:29 +00:00
trycppif "__NO_FPRS__ && !_SOFT_FLOAT" "$t" && fail \
"$0: error: compiler's floating point configuration is unsupported"
add powerpc soft-float support Some PowerPC CPUs (e.g. Freescale MPC85xx) have a completely different instruction set for floating point operations (SPE). Executing regular PowerPC floating point instructions results in "Illegal instruction" errors. Make it possible to run these devices in soft-float mode.
2016-01-25 12:20:52 +00:00
trycppif _SOFT_FLOAT "$t" && SUBARCH=${SUBARCH}-sf
fi
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
test "$ARCH" = "microblaze" && trycppif __MICROBLAZEEL__ "$t" \
&& SUBARCH=${SUBARCH}el
add powerpc64 port
2016-05-01 00:18:17 +00:00
if test "$ARCH" = "powerpc64" ; then
trycppif "_CALL_ELF == 2" "$t" || fail "$0: error: unsupported powerpc64 ABI"
trycppif __LITTLE_ENDIAN__ "$t" && SUBARCH=${SUBARCH}le
trycppif _SOFT_FLOAT "$t" && fail "$0: error: soft-float not supported on powerpc64"
fi
add nofpu subarchs to the sh arch, and properly detect compiler's fpu config
2014-02-28 04:18:42 +00:00
if test "$ARCH" = "sh" ; then
suppress sh assembler rejection of instructions based on isa level we need access to all instructions in order for runtime selection of atomic model to work correctly. without this patch, some versions of gcc instruct gas to reject instructions outside the target isa level.
2015-10-15 21:21:07 +00:00
tryflag CFLAGS_AUTO -Wa,--isa=any
add nofpu subarchs to the sh arch, and properly detect compiler's fpu config
2014-02-28 04:18:42 +00:00
trycppif __BIG_ENDIAN__ "$t" && SUBARCH=${SUBARCH}eb
fix superh nofpu check on old gcc versions As far as gcc3 knows, sh4 is the only processor version that can have an FPU, so it indicates the FPU's presence by defining __SH4__. This is not defined if there is no FPU, even if the processor really is an SH4. Starting with gcc4, there is support for the sh2a processor, which has an FPU but is not an SH4. gcc4 therefore additionally defines __SH_FPU_ANY__ when there is an FPU, but still doesn't define __SH4__ for an FPU-less sh4. Therefore, to support all gcc versions, we must look at both preprocessor symbols.
2014-04-28 02:13:59 +00:00
if trycppif "__SH_FPU_ANY__ || __SH4__" "$t" ; then
add nofpu subarchs to the sh arch, and properly detect compiler's fpu config
2014-02-28 04:18:42 +00:00
# Some sh configurations are broken and replace double with float
# rather than using softfloat when the fpu is present but only
# supports single precision. Reject them.
printf "checking whether compiler's double type is IEEE double... "
fix copy-and-paste error in configure's IEEE double check for sh
2014-02-28 04:55:04 +00:00
echo 'typedef char dblcheck[(int)sizeof(double)-5];' > "$tmpc"
add nofpu subarchs to the sh arch, and properly detect compiler's fpu config
2014-02-28 04:18:42 +00:00
if $CC $CFLAGS_C99FSE $CPPFLAGS $CFLAGS -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
printf "yes\n"
else
printf "no\n"
fail "$0: error: compiler's floating point configuration is unsupported"
fi
else
SUBARCH=${SUBARCH}-nofpu
fi
add sh fdpic subarch variants with this commit it should be possible to produce a working static-linked fdpic libc and application binaries for sh. the changes in reloc.h are largely unused at this point since dynamic linking is not supported, but the CRTJMP macro is used one place outside of dynamic linking, in __unmapself.
2015-09-12 03:22:19 +00:00
if trycppif __SH_FDPIC__ "$t" ; then
SUBARCH=${SUBARCH}-fdpic
fi
add nofpu subarchs to the sh arch, and properly detect compiler's fpu config
2014-02-28 04:18:42 +00:00
fi
superh port
2013-10-05 10:13:18 +00:00
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
test "$SUBARCH" \
&& printf "configured for %s variant: %s\n" "$ARCH" "$ARCH$SUBARCH"
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
allow subarch-specific asm, including asm specific to the default the default subarch is the one whose full name is just the base arch name, with no suffixes. normally, either the asm in the default subarch is suitable for all subarch variants, or separate asm is mandatory for each variant. however, in the case of asm which is purely for optimization purposes, it's possible to have asm that only works (or only performs well) on the default subarch, and not any othe the other variants. thus, I have added a mechanism to give a name to the default variant, for example "armel" for the default, little-endian arm. further such default-subarch names can be added in the future as needed.
2013-08-11 07:27:35 +00:00
case "$ARCH$SUBARCH" in
arm) ASMSUBARCH=el ;;
*) ASMSUBARCH=$SUBARCH ;;
esac
protect against long double type mismatches (mainly powerpc for now) check in configure to be polite (failing early if we're going to fail) and in vfprintf.c since that is the point at which a mismatching type would be extremely dangerous.
2013-08-02 23:34:22 +00:00
#
# Some archs (powerpc) have different possible long double formats
# that the compiler can be configured for. The logic for whether this
# is supported is in bits/float.h; in general, it is not. We need to
# check for mismatches here or code in printf, strotd, and scanf will
# be dangerously incorrect because it depends on (1) the macros being
# correct, and (2) IEEE semantics.
#
printf "checking whether compiler's long double definition matches float.h... "
echo '#include <float.h>' > "$tmpc"
echo '#if LDBL_MANT_DIG == 53' >> "$tmpc"
echo 'typedef char ldcheck[9-(int)sizeof(long double)];' >> "$tmpc"
echo '#endif' >> "$tmpc"
add arch/generic include fallback to build rules this sets the stage for the first phase of the bits deduplication. bits headers which are identical for "most" archs will be moved to arch/generic/bits.
2016-01-28 00:31:15 +00:00
if $CC $CFLAGS_C99FSE \
-I$srcdir/arch/$ARCH -I$srcdir/arch/generic -I$srcdir/include \
$CPPFLAGS $CFLAGS -c -o /dev/null "$tmpc" >/dev/null 2>&1 ; then
protect against long double type mismatches (mainly powerpc for now) check in configure to be polite (failing early if we're going to fail) and in vfprintf.c since that is the point at which a mismatching type would be extremely dangerous.
2013-08-02 23:34:22 +00:00
printf "yes\n"
else
printf "no\n"
fail "$0: error: unsupported long double type"
fi
make configure attempt to catch broken floating point CFLAGS/defaults
2016-02-17 18:53:54 +00:00
#
# Some build systems globally pass in broken CFLAGS like -ffast-math
# for all packages. On recent GCC we can detect this and error out
# early rather than producing a seriously-broken math library.
#
partly revert detection of broken float in configure commit 80fbaac4cd1930e9545a5d36bf46ae49011d2ce8 broke all soft-float archs, where gcc defines __GCC_IEC_559==0 because rounding modes and exception flags are not supported. for now, just check for __FAST_MATH__ as an indication of broken float. this won't detect all possible misconfigurations but it probably catches the most common one.
2016-02-18 04:09:33 +00:00
if trycppif "__FAST_MATH__" \
make configure attempt to catch broken floating point CFLAGS/defaults
2016-02-17 18:53:54 +00:00
"$CFLAGS_C99FSE $CPPFLAGS $CFLAGS" ; then
fail "$0: error: compiler has broken floating point; check CFLAGS"
fi
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
printf "creating config.mak... "
make configure store its command line in config.mak for easy re-run proper shell quoting and pretty-printing (avoiding ugly gratuitous quoting and bad quoting style) is included.
2013-08-16 22:19:47 +00:00
cmdline=$(quote "$0")
for i ; do cmdline="$cmdline $(quote "$i")" ; done
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
exec 3>&1 1>config.mak
cat << EOF
make configure store its command line in config.mak for easy re-run proper shell quoting and pretty-printing (avoiding ugly gratuitous quoting and bad quoting style) is included.
2013-08-16 22:19:47 +00:00
# This version of config.mak was generated by:
# $cmdline
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
# Any changes made here will be lost if configure is re-run
ARCH = $ARCH
add build system support for arch endian & float abi variants
2013-07-19 00:30:58 +00:00
SUBARCH = $SUBARCH
allow subarch-specific asm, including asm specific to the default the default subarch is the one whose full name is just the base arch name, with no suffixes. normally, either the asm in the default subarch is suitable for all subarch variants, or separate asm is mandatory for each variant. however, in the case of asm which is purely for optimization purposes, it's possible to have asm that only works (or only performs well) on the default subarch, and not any othe the other variants. thus, I have added a mechanism to give a name to the default variant, for example "armel" for the default, little-endian arm. further such default-subarch names can be added in the future as needed.
2013-08-11 07:27:35 +00:00
ASMSUBARCH = $ASMSUBARCH
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
srcdir = $srcdir
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
prefix = $prefix
exec_prefix = $exec_prefix
bindir = $bindir
libdir = $libdir
includedir = $includedir
syslibdir = $syslibdir
CC = $CC
keep user-provided CFLAGS/LDFLAGS separate from those added by configure this way, overriding these variables on the make command line (or just re-passing the originally-passed values when invoking make) won't suppress use of the flags added by configure.
2015-11-02 21:58:14 +00:00
CFLAGS = $CFLAGS
CFLAGS_AUTO = $CFLAGS_AUTO
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
CFLAGS_C99FSE = $CFLAGS_C99FSE
work around gcc 4.8's generation of self-referential mem* functions at -O3
2013-08-01 21:12:23 +00:00
CFLAGS_MEMOPS = $CFLAGS_MEMOPS
allow libc itself to be built with stack protector enabled this was already essentially possible as a result of the previous commits changing the dynamic linker/thread pointer bootstrap process. this commit mainly adds build system infrastructure: configure no longer attempts to disable stack protector. instead it simply determines how so the makefile can disable stack protector for a few translation units used during early startup. stack protector is also disabled for memcpy and memset since compilers (incorrectly) generate calls to them on some archs to implement struct initialization and assignment, and such calls may creep into early initialization. no explicit attempt to enable stack protector is made by configure at this time; any stack protector option supported by the compiler can be passed to configure in CFLAGS, and if the compiler uses stack protector by default, this default is respected.
2015-04-14 00:13:10 +00:00
CFLAGS_NOSSP = $CFLAGS_NOSSP
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
CPPFLAGS = $CPPFLAGS
keep user-provided CFLAGS/LDFLAGS separate from those added by configure this way, overriding these variables on the make command line (or just re-passing the originally-passed values when invoking make) won't suppress use of the flags added by configure.
2015-11-02 21:58:14 +00:00
LDFLAGS = $LDFLAGS
LDFLAGS_AUTO = $LDFLAGS_AUTO
support configuring cross compiling with CROSS_COMPILE prefix variable
2012-08-15 02:50:16 +00:00
CROSS_COMPILE = $CROSS_COMPILE
add LIBCC (compiler runtime) logic and override to configure this should both fix the issue with ARM needing -lgcc_eh (although that's really a bug in the libgcc build process that's causing considerable bloat, which should be fixed) and make it easier to build musl using clang/llvm in place of gcc. unfortunately I don't know a good way to detect and support pcc's -lpcc since it's not in pcc's default library search path...
2012-09-10 19:30:52 +00:00
LIBCC = $LIBCC
enhance build process to allow selective -O3 optimization the motivation for this patch is that the vast majority of libc is code that does not benefit at all from optimizations, but that certain components like string/memory operations can be major performance bottlenecks. at the same time, the old -falign-*=1 options are removed, since they were only beneficial for avoiding bloat when global -O3 was used, and in that case, they may have prevented some of the performance gains. to be the most useful, this patch will need further tuning. in particular, research is needed to determine which components should be built with -O3 by default, and it may be desirable to remove the hard-coded -O3 and instead allow more customization of the optimization level used for selected modules.
2013-07-23 01:22:04 +00:00
OPTIMIZE_GLOBS = $OPTIMIZE_GLOBS
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
ALL_TOOLS = $tools
TOOL_LIBS = $tool_libs
Build process uses script to add CFI directives to x86 asm Some functions implemented in asm need to use EBP for purposes other than acting as a frame pointer. (Notably, it is used for the 6th argument to syscalls with 6 arguments.) Without frame pointers, GDB can only show backtraces if it gets CFI information from a .debug_frame or .eh_frame ELF section. Rather than littering our asm with ugly .cfi directives, use an awk script to insert them in the right places during the build process, so GDB can keep track of where the current stack frame is relative to the stack pointer. This means GDB can produce beautiful stack traces at any given point when single-stepping through asm functions. Additionally, when registers are saved on the stack and later overwritten, emit ..cfi directives so GDB will know where they were saved relative to the stack pointer. This way, when you look back up the stack from within an asm function, you can still reliably print the values of local variables in the caller. If this awk script were to understand every possible wild and crazy contortion that an asm programmer can do with the stack and registers, and always emit the exact ..cfi directives needed for GDB to know what the register values were in the preceding stack frame, it would necessarily be as complex as a full x86 emulator. That way lies madness. Hence, we assume that the stack pointer will _only_ ever be adjusted using push/pop or else add/sub with a constant. We do not attempt to detect every possible way that a register value could be saved for later use, just the simple and common ways. Thanks to Szabolcs Nagy for suggesting numerous improvements to this code.
2015-07-10 13:03:24 +00:00
ADD_CFI = $ADD_CFI
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
EOF
test "x$static" = xno && echo "STATIC_LIBS ="
test "x$shared" = xno && echo "SHARED_LIBS ="
build: overhaul wrapper script system for multiple wrapper support this overhauls part of the build system in order to support multiple toolchain wrapper scripts, as opposed to solely the musl-gcc wrapper as before. it thereby replaces --enable-gcc-wrapper with --enable-wrapper=..., which has the options 'auto' (the default, detect whether to use wrappers), 'all' (build and install all wrappers), 'no' (don't build any) and finally the options named after the individual compiler scripts (currently only 'gcc' is available) to build and install only that wrapper. the old --enable-gcc-wrapper is removed from --help, but still available. it also modifies the wrappers to use the C compiler specified to the build system as 'inner' compiler, when applicable. as wrapper detection works by probing this compiler, it may not work with any other.
2015-06-28 21:08:19 +00:00
test "x$cc_family" = xgcc && echo 'WRAPCC_GCC = $(CC)'
add musl-clang, a wrapper for system clang installs musl-clang allows the user to compile musl-powered programs using their already existent clang install, without the need of a special cross compiler. it achieves this by wrapping around both the system clang install and the linker and passing them special flags to re-target musl at runtime. it does only affect invocations done through the special musl-clang wrapper script, so that the user setup remains fully intact otherwise. the clang wrapper consists of the compiler frontend wrapper script, musl-clang, and the linker wrapper script, ld.musl-clang. musl-clang makes sure clang invokes ld.musl-clang to link objects; neither script needs to be in PATH for the wrapper to work.
2015-06-28 21:08:21 +00:00
test "x$cc_family" = xclang && echo 'WRAPCC_CLANG = $(CC)'
use same object files for libc.a and libc.so if compiler produces PIC now that .lo and .o files differ only by whether -fPIC is passed (and no longer at the source level based on the SHARED macro), it's possible to use the same object files for both static and shared libc when the compiler would produce PIC for the static files anyway. this happens if the user has included -fPIC in their CFLAGS or if the compiler has been configured to produce PIE by default. we use the .lo files for both, and still append -fPIC to the CFLAGS, rather than using the .o files so that libc.so does not break catastrophically if the user later removes -fPIC from CFLAGS in config.mak or on the make command line. this also ensures that we get full -fPIC in case -fpic, -fPIE, or some other lesser-PIC option was passed in CFLAGS.
2016-01-26 00:57:38 +00:00
test "x$pic_default" = xyes && echo 'AOBJS = $(LOBJS)'
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
exec 1>&3 3>&-
support out-of-tree build this change adds support for building musl outside of the source tree. the implementation is similar to autotools where running configure in a different directory creates config.mak in the current working directory and symlinks the makefile, which contains the logic for creating all necessary directories and resolving paths relative to the source directory. to support both in-tree and out-of-tree builds with implicit make rules, all object files are now placed into a separate directory.
2015-11-18 20:07:32 +00:00
test "$srcdir" = "." || ln -sf $srcdir/Makefile .
initial commit of configure script this script is not based on autoconf; however it attempts to follow the same interface contracts for ease of integration with build systems. it is also not necessary to use musl. manually written config.mak files are still supported, as is building without any config.mak at all as long as you are happy with the default options and you supply at least ARCH on the command line to make.
2012-05-05 03:24:51 +00:00
printf "done\n"
Reference in New Issue Copy Permalink