From 055e646bfc1fc0b06ac61ee88f1d31b1698f287f Mon Sep 17 00:00:00 2001 From: Danie Roux Date: Sun, 8 Sep 2013 02:04:43 +0200 Subject: coreutils: Guard against compiler not supporting __builtin_stpncpy_chk From https://lists.macosforge.org/pipermail/macports-dev/2011-July/015263.html: 5) Building with a compiler that doesn't support newer __builtins If your port uses MacPorts compilers rather than the default compiler, you may run into trouble with string functions. You'll see errors at link time about undefined __builtin_* functions. If this happens, you may want to compile with -D_FORTIFY_SOURCE=0 to tell the headers to use unfortified versions which do not use compiler builtins. --- pkgs/tools/misc/coreutils/default.nix | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pkgs/tools/misc/coreutils/default.nix b/pkgs/tools/misc/coreutils/default.nix index da3e8d09a23..c4066c89d1d 100644 --- a/pkgs/tools/misc/coreutils/default.nix +++ b/pkgs/tools/misc/coreutils/default.nix @@ -59,6 +59,9 @@ let NIX_LDFLAGS = stdenv.lib.optionalString selinuxSupport "-lsepol"; + makeFlags = stdenv.lib.optionalString stdenv.isDarwin + "CFLAGS=-D_FORTIFY_SOURCE=0"; + meta = { homepage = http://www.gnu.org/software/coreutils/; description = "The basic file, shell and text manipulation utilities of the GNU operating system"; -- cgit 1.4.1