From: Paolo Bonzini <bonzini@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
binutils@sourceware.org, GCC Mailing List <gcc@gcc.gnu.org>,
DJ Delorie <dj@redhat.com>,
gdb@sourceware.org, newlib@sourceware.org, cygwin@cygwin.com
Subject: Re: Combined tree fails to build -- libtool version mismatch?
Date: Sat, 09 Jan 2010 18:06:00 -0000 [thread overview]
Message-ID: <4B48C5B2.6090607@gnu.org> (raw)
In-Reply-To: <6dc9ffc81001090748g533e9a6dl3e5481e2704a25a3@mail.gmail.com>
On 01/09/2010 04:48 PM, H.J. Lu wrote:
> On Sat, Jan 9, 2010 at 6:26 AM, Paolo Bonzini<bonzini@gnu.org> wrote:
>> On 01/09/2010 12:16 PM, Steven Bosscher wrote:
>>>
>>> This is with gcc SVN revision 155740, and src checked out yesterday
>>> (top of src/Changelog is the fix from Kaveh and FX for gcc PR42424).
>>>
>>> Not knowing a thing about libtool, I hope someone can tell me what's
>>> wrong here;-)
>>
>> src and gcc's libtool are out-of-sync (2.2.6 vs. 2.2.7a respectively). Since
>> gcc's files dominate, you have ltmain.sh from GCC but bfd's configure uses
>> src's libtool configuration.
>>
>> Binutils should adopt GCC's libtool.m4, ltmain.sh, lt~obsolete.m4,
>> ltoptions.m4, ltsugar.m4, ltversion.m4 and src should rerun autoconf on all
>> of its scripts (CCing gdb, newlib and cygwin mailing lists).
>>
>> DJ, can you add these files to the list that we get email about?
>
> Many files in the top directories between gcc and src are out of sync.
> You can do a diff on them to check it out.
I know (as hinted above build maintainers get emails about out-of-sync
email), but they do not break the build...
Paolo
next prev parent reply other threads:[~2010-01-09 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <571f6b511001090316h44fefc7k672f595117024475@mail.gmail.com>
2010-01-09 14:26 ` Paolo Bonzini
2010-01-09 15:48 ` H.J. Lu
2010-01-09 18:06 ` Paolo Bonzini [this message]
2010-01-09 18:14 ` Ralf Wildenhues
2010-01-11 19:09 ` DJ Delorie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B48C5B2.6090607@gnu.org \
--to=bonzini@gnu.org \
--cc=binutils@sourceware.org \
--cc=cygwin@cygwin.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=newlib@sourceware.org \
--cc=stevenb.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox