From: Ian Lance Taylor <ian@airs.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: binutils@sourceware.org, gdb@sourceware.org, gcc@gcc.gnu.org
Subject: Re: intl directory: gcc vs. src
Date: Fri, 12 May 2006 20:04:00 -0000 [thread overview]
Message-ID: <m3wtcr6be8.fsf@gossamer.airs.com> (raw)
In-Reply-To: <200605112057.NAA14726@hpsje.cup.hp.com>
Steve Ellcey <sje@cup.hp.com> writes:
> By removing the AM_PROG_INSTALL definition from aclocal.m4 I was able to
> run autoconf 2.59 on the src tree intl subdir with no problems but I was
> wondering if we should take the time to synchronize the GCC intl
> directory with the src tree intl directory. The GCC version is already
> configured with autoconf 2.59.
>
> I did some testing by copying my GCC intl directory (plus config.rpath)
> into my src tree and I was able to build binutils and gas with no
> problem and with no other changes needed. This was on a system where
> libintl was not installed and the intl subdir was built.
>
> What do people who build in a combined tree do with intl? Do they use
> the GCC version or the src tree version? Is there any consensus about
> whether or not there should be a single version of intl, and if so,
> which one should be used?
Yes, there should be a single version of intl. I don't think anybody
cares which version is used, as long as it works. If you have taken
the time to test a unified intl, and are prepared to fix any problems,
I think your patch would be great.
Ian
next prev parent reply other threads:[~2006-05-12 5:49 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 [this message]
2006-05-16 23:23 ` Steve Ellcey
2006-05-17 0:35 ` Daniel Jacobowitz
2006-05-17 11:05 ` Steve Ellcey
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=m3wtcr6be8.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=sje@cup.hp.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).