This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configure.{in -> ac} rename (commit 35eafcc71b) broke in-tree binutils building of gcc


Sorry to be sending this message 3 times, just wanted to put a message
on the 3 related patches submitted.

See updated (to current trunk/master) gcc patch from one I submitted
on May 24 at: https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01461.html
See updated (to current trunk/master) binutils-gdb patch from one I
submitted on May 24 at:
https://sourceware.org/ml/binutils/2015-07/msg00146.html

Both attached to this email for convenience.

They rename the left over configure.in files to configure.ac in
binutils-gdb.  (Some were missed when the others were changed.)

They update all references (even in documentation) to configure.in to
configure.ac in both binutils-gdb and gcc -- so combined builds work
great again.


On Wed, Jul 15, 2015 at 2:32 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 15.07.15 at 03:20, <amodra@gmail.com> wrote:
>> On Tue, Jul 14, 2015 at 10:13:06AM +0100, Jan Beulich wrote:
>>> (there doesn't seem
>>> to be a fix for this in gcc trunk either, which I originally expected I could
>>> simply backport).
>>
>> The configure.in->configure.ac rename happened over a year ago so I
>> guess this shows that not too many people use combined binutils+gcc
>> builds nowadays.  I've always found combined binutils+gcc builds not
>> worth the bother compared to simply building and installing binutils
>> first, as Jim suggests.
>
> That doesn't work well when you want to specifically avoid
> installing, instead running directly from the build tree.
>
> Jan
>

Attachment: gcc.combined.build.patch.updated
Description: Binary data

Attachment: binutils-gdb.combined.build.patch.updated
Description: Binary data


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]