From: Steve Ellcey <sje@cup.hp.com>
To: drow@false.org
Cc: ian@airs.com, binutils@sourceware.org, gdb@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: intl directory: gcc vs. src
Date: Wed, 17 May 2006 11:05:00 -0000 [thread overview]
Message-ID: <200605162306.QAA29605@hpsje.cup.hp.com> (raw)
In-Reply-To: <20060516223900.GA16291@nevyn.them.org>
> > Who maintains this automatic merge process?
>
> The man to ask about this is DJ Delorie. I'm not sure how much work it
> is on his part, though.
>
> Either way it would probably be best to do the initial sync by hand.
> And is it really plausible that nothing in src would need updating for
> the new intl?
>
> --
> Daniel Jacobowitz
> CodeSourcery
If something in src is going to need updating I don't know what it is.
I built binutils, gas, and gdb on HP-UX platforms using the gcc intl
directory and had no problems. When I built on Linux the intl directory
was basically ignored because it used the system gettext stuff.
I'm sure something might need updating after this change and I am
willing to try and fix anything I break, but I am not sure what other
testing I can do with the platforms I have available. Do you have any
suggestions as to what products or platforms might cause problems?
I did get one reply from a combined-tree user who said they used the gcc
version of intl when building things in a combined-tree.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2006-05-16 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 0:23 Steve Ellcey
2006-05-12 20:04 ` Ian Lance Taylor
2006-05-16 23:23 ` Steve Ellcey
2006-05-17 0:35 ` Daniel Jacobowitz
2006-05-17 11:05 ` Steve Ellcey [this message]
2006-05-17 13:21 ` Daniel Jacobowitz
2006-05-17 0:41 ` DJ Delorie
2006-05-17 1:27 ` Bobby McNulty
2006-05-17 5:09 ` DJ Delorie
2006-05-15 23:09 ` James Lemke
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=200605162306.QAA29605@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).