emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#31003: closed (Test failure on macOS with new Xcod


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#31003: closed (Test failure on macOS with new Xcode 9.3 command-line tools)
Date: Sun, 01 Apr 2018 20:39:01 +0000

Your message dated Sun, 1 Apr 2018 13:37:59 -0700
with message-id <address@hidden>
and subject line Re: bug#31003: Test failure on macOS with new Xcode 9.3 
command-line tools
has caused the debbugs.gnu.org bug report #31003,
regarding Test failure on macOS with new Xcode 9.3 command-line tools
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
31003: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31003
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Test failure on macOS with new Xcode 9.3 command-line tools Date: Sat, 31 Mar 2018 09:51:26 -0400
Building grep 3.1 on macOS 10.3.3 with the newly-released command-line tools for Xcode 9.3 causes a test failure:

-------8<-------------------------------------------------------------
FAIL: test-vasnprintf
=====================

FAIL test-vasnprintf (exit status: 132)
------>8--------------------------------------------------------------

gnulib-tests/test-suite.log carries no further information than that.

In configure.log, I find the following:

-------8<-------------------------------------------------------------
configure:7830: checking for vasnprintf
configure:7830: gcc -o conftest -g -O2   conftest.c  >&5
Undefined symbols for architecture x86_64:
  "_vasnprintf", referenced from:
      _main in conftest-b41cac.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
------>8--------------------------------------------------------------


I'm really wondering whether a grep 3.1 that fails this test is safe to keep using.

The exact same failure happens when building diffutils, and I have emailed address@hidden to report this.

I'm not sure if this is related or not, but config.log also has:

------>8--------------------------------------------------------------
configure:7830: checking for snprintf
configure:7830: gcc -o conftest -g -O2   conftest.c  >&5
conftest.c:86:6: warning: incompatible redeclaration of library function 'snprintf' [-Wincompatible-library-redeclaration]
char snprintf ();
     ^
conftest.c:86:6: note: 'snprintf' is a builtin with type 'int (char *, unsigned long, const char *, ...)'
1 warning generated.
------>8--------------------------------------------------------------

I'm also not sure if *this* is related or not, but I see the following compiler warning during build:

CC       openat.o
obstack.c:351:31: warning: incompatible pointer types initializing 'void
      (*)(void) __attribute__((noreturn))' with an _expression_ of type
      'void (void)' [-Wincompatible-pointer-types]
__attribute_noreturn__ void (*obstack_alloc_failed_handler) (void)
                              ^
1 warning generated.


-Charles


--- End Message ---
--- Begin Message --- Subject: Re: bug#31003: Test failure on macOS with new Xcode 9.3 command-line tools Date: Sun, 1 Apr 2018 13:37:59 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
Charles Diza wrote:

I'm really wondering whether a grep 3.1 that fails this test is safe to
keep using.

It's safe. This is an incompatibility that Apple deliberately introduced into macOS to try to make programs "safer". The incompatibility breaks the test programs in question but does not break grep or diffutils proper (nor does it make them any "safer"). We'll work around the incompatiblity in future versions. See the thread starting here:

https://lists.gnu.org/r/bug-gnulib/2017-07/msg00056.html


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]