From: James Lemke <jwlemke@wasabisystems.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org
Subject: Re: intl directory: gcc vs. src
Date: Mon, 15 May 2006 23:09:00 -0000 [thread overview]
Message-ID: <1147700272.6054.37.camel@winch.thelemkes.ca> (raw)
In-Reply-To: <200605112057.NAA14726@hpsje.cup.hp.com>
> 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?
FWIW, I have always given preference to the gcc version.
--
Jim Lemke jwlemke@wasabisystems.com Orillia, Ontario
prev parent reply other threads:[~2006-05-15 13:37 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
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 [this message]
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=1147700272.6054.37.camel@winch.thelemkes.ca \
--to=jwlemke@wasabisystems.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).