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

darlingm at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |---

--- Comment #4 from darlingm at gmail dot com ---
The commit that broke combined builds is:
binutils # 35eafcc71b8a54330704656fb6df0b5d6665ed15 Fri Jul 4 12:59:42 2014
+0930 | Rename configure.in to configure.ac (HEAD)

If I run binutils # 35eafcc combined with gcc # 09853ca {Jul 4 15:56:27 2014},
I get the same error regarding "gas/as-new not existing".

If I move binutils to its parent, # 82b57a9, combined with the same gcc, it
builds just fine.  (I was using "configure --disable-multilib" and CFLAGS &
CXXFLAGS being "-Wno-error=unused-value -Wno-error=strict-overflow
-Wno-error=maybe-uninitialized".  Not sure if these 3 were all needed for gcc
4.9.2 to "backwards compile" gcc between 4.8.3 and 4.8.4, but I picked these 3
up along the way binary searching for the problem.)

I can move gcc a few ways in either direction with no effect.  It all depends
on which side if this binutils commit it's on.

Binutils # 35eafcc renamed 6 configure.in files to configure.ac (in bfd,
binutils, gas, gprof, ld, and opcodes).  It updated binutils calls to these
files with the new extension.  But, there was never a corresponding change to
gcc to use the new extension.  And, it left 3 configure.in files with the old
extension (in etc, readline, and readline/examples/rlfe).

Fixing the gcc calls to binutils configure files is much easier with all of
binutils configure.in files renamed to configure.ac.  So, I submitted a patch
to binutils to rename the 3 remaining configure.in files, and update all
references to them within binutils.  And, I submitted a patch to gcc to fix all
references to binutils configure.in files to the new extension.

I also noticed gcc renamed its configure.in files to configure.ac some time
ago.  But, a few references to configure.in remained in error messages and
documentation.  The gcc patch I submitted fixes these references.

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

_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils

Reply via email to