summary refs log tree commit diff
path: root/configure
Commit message (Collapse)AuthorAgeFilesLines
* S/390: Port of lock elision to System/zDominik Vogt2014-05-091-0/+2
| | | | | | | | | | Added support for TX lock elision of pthread mutexes on s390 and s390x. This may improve lock scaling of existing programs on TX capable systems. The lock elision code is only built with --enable-lock-elision=yes and then requires a GCC version supporting the TX builtins. With lock elision default mutexes are elided via __builtin_tbegin, if the cpu supports transactions. By default lock elision is not enabled and the elision code is not built.
* nscd: Make SELinux checks dynamic.Carlos O'Donell2014-04-141-30/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SELinux team has indicated to me that glibc's SELinux checks in nscd are not being carried out as they would expect the API to be used today. They would like to move away from static header defines for class and permissions and instead use dynamic checks at runtime that provide an answer which is dependent on the runtime status of SELinux i.e. more dynamic. The following patch is a minimal change that moves us forward in this direction. It does the following: * Stop checking for SELinux headers that define NSCD__SHMEMHOST. Check only for the presence or absence of the library. * Don't encode the specific SELinux permission constants into a table at build time, and instead use the symbolic name for the permission as expected. * Lookup the "What do we do if we don't know this permission?" policy and use that if we find SELinux's policy is older than the glibc policy e.g. we make a request for a permission that SELinux doesn't know about. * Lastly, translate the class and permission and then make the permission check. This is done every time we lookup a permission, and this is the expected way to use the API. SELinux will optimize this for us, and we expect the network latencies to hide these extra library calls. Tested on x86, x86-64, and via Fedora Rawhide since November 2013. See: https://sourceware.org/ml/libc-alpha/2014-04/msg00179.html
* PowerPC: define _CALL_ELF if compiler does notAdhemerval Zanella2014-04-061-2/+6
| | | | | | | | | | | | This patch makes the configure adds -D_CALL_ELF=1 when compiler does not define _CALL_ELF (versions before powerpc64le support). It cleans up compiler warnings on old compiler where _CALL_ELF is not defined on powerpc64(be) builds. It does by add a new config.make variable for configure-deduced CPPFLAGS and accumulate into that (confix-extra-cppflags). It also generalizes libc_extra_cflags so it accumulates in sysdeps configure fragmenets.
* stop supporting bash-1.xMike Frysinger2014-03-131-9/+0
| | | | | We've stopped supporting toolchain packages older than 2009, so punting bash-1.x is reasonable when bash-2 was released almost 20 years ago.
* delete ksh checksMike Frysinger2014-03-131-56/+0
| | | | Nothing in the tree uses ksh anymore, so punt these checks.
* Use __ehdr_start, when available, for rtld to get its own headers.Roland McGrath2014-03-131-0/+38
|
* Set AUTOCONF variable when maintainer-mode is not usedAllan McRae2013-12-161-0/+2
| | | | | Fixes build issue introduced in 8894bad3 when configure.ac is altered and maintainer-mode is not enabled.
* Add --enable-maintainer-mode configure optionAllan McRae2013-12-161-16/+30
| | | | | | | | | Autoconf is tested for and run if needed only when --enable-maintainer-mode is used on configure. This results in the autom4te.cache directory only being written in the source directory during configure if automatic autoconf usage is requested. Fixes BZ #14120.
* Accept make versions 4.0 and greaterMarc-Antoine Perennou2013-10-311-1/+1
|
* rename configure.in to configure.acMike Frysinger2013-10-301-1/+1
| | | | | | | Autoconf has been deprecating configure.in for quite a long time. Rename all our configure.in and preconfigure.in files to .ac. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* PowerPC LE configuryAlan Modra2013-10-041-2/+2
| | | | | | | | | | | http://sourceware.org/ml/libc-alpha/2013-08/msg00096.html This adds the basic configury bits for powerpc64le and powerpcle. * configure.in: Map powerpc64le and powerpcle to base_machine/machine. * configure: Regenerate. * nptl/shlib-versions: Powerpc*le starts at 2.18. * shlib-versions: Likewise.
* Remove --disable-versioning.Joseph Myers2013-09-041-95/+0
|
* configure: add missing quotes in $build_pt_chown testMike Frysinger2013-08-251-1/+1
| | | | Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* CVE-2013-2207, BZ #15755: Disable pt_chown.Carlos O'Donell2013-07-211-0/+16
| | | | | | | | | | | | | | | | | | | | | | | The helper binary pt_chown tricked into granting access to another user's pseudo-terminal. Pre-conditions for the attack: * Attacker with local user account * Kernel with FUSE support * "user_allow_other" in /etc/fuse.conf * Victim with allocated slave in /dev/pts Using the setuid installed pt_chown and a weak check on whether a file descriptor is a tty, an attacker could fake a pty check using FUSE and trick pt_chown to grant ownership of a pty descriptor that the current user does not own. It cannot access /dev/pts/ptmx however. In most modern distributions pt_chown is not needed because devpts is enabled by default. The fix for this CVE is to disable building and using pt_chown by default. We still provide a configure option to enable hte use of pt_chown but distributions do so at their own risk.
* Fix lock elision help text in INSTALL and configureSiddhesh Poyarekar2013-07-041-2/+1
|
* Add a configure option to enable lock elision and disable by defaultAndi Kleen2013-07-021-0/+16
| | | | Can be enabled with --enable-lock-elision=yes at configure time.
* Require GCC 4.4 or later to build glibc.Joseph Myers2013-06-261-1/+1
|
* Fix loop construction to functions callsAdhemerval Zanella2013-06-201-0/+33
| | | | | | Check wheter the compiler has the option -fno-tree-loop-distribute-patterns to inhibit loop transformation to library calls and uses it on memset and memmove default implementation to avoid recursive calls.
* Sort sysd-rules-patterns by descending pattern length.Roland McGrath2013-06-171-1/+1
|
* Configuring for i386 is no longer supported.Carlos O'Donell2013-04-171-10/+1
| | | | | | | | | | | | | | | | | We no longer support configuring for i386, nor do we elide such a configuration to i686. Configuring with i386-* is a failure, and we provide an example of how to fix that. --- 2013-04-17 Carlos O'Donell <carlos@redhat.com> * configure.in: Remove i386 configure warning. Remove i386 case. * configure: Regenerate. * sysdeps/i386/configure.in: Raise error if config_machine is i386. Add example to error message. * sysdeps/i386/configure: Regenerate.
* i386: Fail at configure time for i386 builds.Carlos O'Donell2013-04-061-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change does two things: * Treats a target i386-* as if it were i686. * Fails configure if the user is generating code for i386. We no longer support i386 code-generation because the i386 lacks the atomic operations we need in glibc. You can still configure for i386-*, but you get i686 code. You can't build with --march=i386, --mtune=i386 or a compiler that defaults to i386 code-generation. I've added two i386 entries in the master todo list to discuss merging and renaming: http://sourceware.org/glibc/wiki/Development_Todo/Master#i386 The failure modes are fail-safe here. You compile for i386, get i686, and try to run on i386 and it fails. The configure log has a warning saying we elided to i686. There is no situation that I can see where we run into any serious problems. The patch makes the current state better in that we get less confused users and we build successfully in more default configurations. The next enhancement would be to add --march=i?86 as suggested in #c20 of BZ#10062 for any i?86-* builds, which would solve the problem of a 32-bit compiler that defaults to i386 code-gen and glibc configured for i686-* target. Which previously failed at build time, and now will fail at configure time (requires adding --march=i686). Updated NEWS with BZ #10060 and #10062. No regressions. --- 2013-04-06 Carlos O'Donell <carlos@redhat.com> [BZ #10060, #10062] * aclocal.m4 (LIBC_COMPILER_BUILTIN_INLINED): New macro. * sysdeps/i386/configure.in: Use LIBC_COMPILER_BUILTIN_INLINED and fail configure if __sync_val_compare_and_swap is not inlined. * sysdeps/i386/configure: Regenerate. * configure.in: Build for i686 when configured for i386. * configure: Regenerate. * README: Remove i386 reference.
* Move system-specific settings out of toplevel configure.in and config.make.in.Joseph Myers2013-03-201-18/+2
|
* Add support for rtld directory different from slib directoryAndreas Schwab2013-03-191-0/+2
|
* Don't bother checking for $CC option to accept ISO C89.Thomas Schwinge2013-01-251-90/+5
|
* configure: Default to CPP="$CC -E" unless overridden.Thomas Schwinge2013-01-251-167/+6
|
* Fix multiarch handling in sysdeps generation.Roland McGrath2013-01-111-4/+10
|
* Add --enable-hardcoded-path-in-tests configure optionH.J. Lu2013-01-111-0/+14
|
* Remove some old cruft variables from configure.Roland McGrath2013-01-101-2/+3
|
* Fix C++ header directory detection for non-standard paths.Adam Conrad2012-11-241-6/+5
| | | | | | Stop assuming specific path layouts for C++ headers, and instead use an autodetection method that looks for paths with '/[cg]++' in the g++ include list.
* Properly check linker -z XXX supportH.J. Lu2012-11-211-60/+80
|
* Fix ifunc configure check for 64-bit targetsAndreas Schwab2012-11-181-2/+6
|
* Support --with-pkgversion and --with-bugurl.Joseph Myers2012-11-091-0/+66
|
* BZ#14743: Move clock_* symbols from librt to libc.Roland McGrath2012-10-241-0/+7
|
* change ifunc assembly test to a link testMike Frysinger2012-10-241-105/+116
| | | | | | | | | | | | | The test currently tests the binutils frontend support which passes for all versions of binutils we currently require (2.20+). It doesn't test the backend which is required for ifunc to actually work, and which most targets don't yet support. Change the assembly code so that when we link it, we get a file that has ifunc relocations if the backend supports it. That way we can test to see if binutils supports everything we need. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* drop -q flag when using grepMike Frysinger2012-10-241-3/+3
| | | | | | We don't currently want to rely on the -q option to grep. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* Remove relics of support for configuring in the source directory.Joseph Myers2012-10-191-8/+2
|
* Use $CXX not cc1plus to locate C++ headers.Joseph Myers2012-10-101-3/+2
|
* Clean up conditionalize of ld.so.cache support.Roland McGrath2012-10-031-0/+4
|
* Remove $(have-cpp-asm-debuginfo) checkH.J. Lu2012-09-151-2/+0
|
* Improve C++ header location detection (bug 13966)Allan McRae2012-09-061-6/+4
|
* Check for gawk >= 3.0 (bug 13412)Allan McRae2012-09-021-44/+64
|
* Add --disable-build-nscd configure option.Roland McGrath2012-08-221-0/+15
|
* BZ#13696: Add --disable-nscd configure option.Roland McGrath2012-08-221-0/+20
|
* Fix sed configure check for newer sed --version output.Dmitry V. Levin2012-08-221-1/+1
|
* Make sysheaders available in config.make.Roland McGrath2012-08-171-0/+2
|
* Get rid of ASM_TYPE_DIRECTIVE{,_PREFIX}.Marek Polacek2012-08-021-38/+2
|
* configure.in <sysdeps resolving>: Correct printing Implies_before.Thomas Schwinge2012-07-231-1/+1
|
* Get rid of ASM_GLOBAL_DIRECTIVE.Marek Polacek2012-07-101-40/+5
|
* Respect --localstatedir for /var/db parent directory.Roland McGrath2012-06-221-0/+3
|
* Weaken PIE configure test to a compile test.Joseph Myers2012-05-301-9/+3
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-10-30 07:00:52 +0000