public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: gdb@sources.redhat.com
Cc: ian@wasabisystems.com
Subject: Can we have the intl directory back?
Date: Sat, 20 Nov 2004 12:29:00 -0000	[thread overview]
Message-ID: <200411201001.iAKA1KDA054275@elgar.sibelius.xs4all.nl> (raw)

I just discovered that we released a GDB 6.3 that will probably not
build out of the box on systems that don't have an installed libintl
in the default search path.  You can work around this by specifying
--disable-nls, but that sucks.  I didn't realize that our autoconfig
scripts don't default to --disable-nls if no usable libintl is found.
I didn't notice it because I never removed the intl directory from my
checked out CVS tree.

Now that I know this, Andrew's argument for not including the intl
subdirectory doesn't really make sense.  Instead of having to specify
--disable-nls on systems where the included intl doesn't build, you
now have to specify --disable-nls on almost all non-GNU systems.

So can we please add back the intl directory?  The alternative of
checking whether an installed intl is available would be acceptable
too, but that requires coordination with binutils, since we'd have to
duplicate that logic for the bfd subdirectory too.

There was a recent discussion about bringing over the intl stuff from
GCC.  I'm willing to spend some time on that if it means I get my intl
back ;-).

Mark

             reply	other threads:[~2004-11-20 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20 12:29 Mark Kettenis [this message]
2004-11-20 23:30 ` Eli Zaretskii
     [not found] <20041121003023.GA26335@nevyn.them.org>
2004-11-22 12:41 ` Paul Schlie

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=200411201001.iAKA1KDA054275@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=ian@wasabisystems.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).