bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/22880] New: ./configure stalls forever if CC=clang


From: bjornpagen at gmail dot com
Subject: [Bug binutils/22880] New: ./configure stalls forever if CC=clang
Date: Thu, 22 Feb 2018 22:49:01 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=22880

            Bug ID: 22880
           Summary: ./configure stalls forever if CC=clang
           Product: binutils
           Version: 2.30
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: bjornpagen at gmail dot com
  Target Milestone: 2.31
            Target: x86_64-gentoo-linux-musl

Created attachment 10843
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10843&action=edit
Here is my patch to fix the issue

Binutils 2.29 and 2.30 both do not pass ./configure with CC=clang. When
./configure is run, it stalls when it reaches "checking whether the compiler
driver understands Ada...", and does not continue.

I have also identified the cause. The bug is caused by a test for an edge case
for a gcc earlier than gcc-3. If this snippet of code is remove from
./configure, then the configure process continues as normal and binutils is
compiled flawlessly.

[...]
# There is a bug in old released versions of GCC which causes the
# driver to exit successfully when the appropriate language module
# has not been installed.  This is fixed in 2.95.4, 3.0.2, and 3.1.
# Therefore we must check for the error message as well as an
# unsuccessful exit.
# Other compilers, like HP Tru64 UNIX cc, exit successfully when
# given a .adb file, but produce no object file.  So we must check
# if an object file was really produced to guard against this.
errors=`(${CC} -c conftest.adb) 2>&1 || echo failure`
if test x"$errors" = x && test -f conftest.$ac_objext; then
  acx_cv_cc_gcc_supports_ada=yes
fi
[...]

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

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