From: Nick Clifton <nickc@redhat.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: Paolo Bonzini <bonzini@gnu.org>,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: sync toplevel between GCC and src
Date: Wed, 19 Aug 2009 07:24:00 -0000 [thread overview]
Message-ID: <4A8BA4A0.8040407@redhat.com> (raw)
In-Reply-To: <20090818184110.GC30742@gmx.de>
Hi Ralf,
> The merge of toplevel synced files from GCC to src
> <http://thread.gmane.org/gmane.comp.gnu.binutils/42983/focus=26485>
> still doesn't have one small nod that I would like from a src maintainer:
> ** adding target-newlib to noconfigdirs for powerpc-*-aix* and
> rs6000-*-aix*,
This is OK.
> ** adding target-libgloss to noconfigdirs for sh*-*-elf,
Also OK.
> - the files move from GPLv2 to GPLv3 header. Is that a problem for
> anything in src?
Not at all. In fact it is a good thing.
> - in Makefile.tpl, there are new settings for CXX and CXX_FOR_BUILD in
> POSTSTAGE1_HOST_EXPORTS, that might be responsible for
> <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40950>, and I would hate
> to just propagate this bug to src if it can be avoided.
Hmm, I see what you mean. Really we need some extra logic in the
definition of POSTSTAGE1_HOST_EXPORTS so that CXX and CXX_FOR_BUILD are
only defined if they were created in stage1. Not being an autogen
export I am not sure how easy this is to do.
My feeling though is that it is better to have the top level files in
sync, even if it does mean propagating this bug, as there is a
workaround (configuring with --enable-stage1-languages=c,c++).
Cheers
Nick
next prev parent reply other threads:[~2009-08-19 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 15:10 Ralf Wildenhues
2009-08-16 15:14 ` Ralf Wildenhues
2009-08-16 16:52 ` Paolo Bonzini
2009-08-16 17:15 ` Ralf Wildenhues
2009-08-16 17:23 ` Paolo Bonzini
2009-08-19 0:02 ` Ralf Wildenhues
2009-08-19 4:34 ` Ian Lance Taylor
2009-08-19 7:07 ` Paolo Bonzini
2009-08-19 7:24 ` Nick Clifton [this message]
2009-08-19 19:52 ` Ralf Wildenhues
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=4A8BA4A0.8040407@redhat.com \
--to=nickc@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gdb@sourceware.org \
/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