From: Christopher Faylor <me@cgf.cx>
To: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: gcc/intl vs. src/intl
Date: Wed, 17 Nov 2004 14:25:00 -0000 [thread overview]
Message-ID: <20041117032856.GD28679@trixie.casa.cgf.cx> (raw)
In-Reply-To: <m3vfc5p7ge.fsf@gossamer.airs.com>
On Tue, Nov 16, 2004 at 08:53:05PM -0500, Ian Lance Taylor wrote:
>So, I notice that gcc/intl and src/intl are pretty different. And I
>wonder how this can possibly work in the context of uberbaum. I
>suppose it will work fine on a host on which all the intl code can be
>found in libc with no other dependencies--such as GNU/Linux. On such
>a host the intl directory will not be built, and code will simply link
>with -lc. But on a host in which gcc/intl requires -liconv--such as
>NetBSD, or Cygwin--the differing expectations of gcc/intl and src/intl
>will cause conflict.
>
>Has anybody looked into resolving this? Presumably the correct
>short-term fix is to bring gcc/intl over to src/intl, and update the
>Makefiles accordingly. Presumably the long-term fix would to keep
>intl in sync as we keep libiberty in sync. Does anybody have a better
>idea?
The other, more radical way of doing this is to get rid of uberbaum and
finally put gcc, gdb, and binutils under one repository. cygwin, sid
and other non-GNU projects could keep using the src repository while
the other GNU projects could use the same infrastructure.
cgf
prev parent reply other threads:[~2004-11-17 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 2:11 Ian Lance Taylor
2004-11-17 3:28 ` DJ Delorie
2004-11-17 14:25 ` Christopher Faylor [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=20041117032856.GD28679@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=binutils@sourceware.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