public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Cc: Steve Ellcey <sje@cup.hp.com>
Subject: Re: changes in 'intl'
Date: Fri, 26 May 2006 02:30:00 -0000	[thread overview]
Message-ID: <20060525174240.GA5632@nevyn.them.org> (raw)
In-Reply-To: <20060525144537.GA1017@nevyn.them.org>

On Thu, May 25, 2006 at 10:45:37AM -0400, Daniel Jacobowitz wrote:
> On Thu, May 25, 2006 at 06:57:01AM -0700, Brian Dessent wrote:
> > I'm having difficulty building current CVS binutils for native cygwin
> > (i686-pc-cygwin).  If I configure without options, nothing is built in
> > intl/ and I get the following error trying to link in binutils/
> 
> The very same code fragment, from config/gettext.m4, is used to
> determine whether to build intl/ and whether to link to it.  This is
> very strange.  I'm going to try to reproduce it myself.

BFD uses src/gettext.m4.  intl uses src/config/gettext.m4.  They define
different macros, and detect different conditions.

config/gettext.m4 is the new one and presumably better.  We will have
to migrate.  With a little luck, this will fix some known problems
building GDB with NLS...

I will work on it.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-05-25 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 17:22 Brian Dessent
2006-05-25 21:05 ` Daniel Jacobowitz
2006-05-26  2:30   ` Daniel Jacobowitz [this message]
2006-05-26  3:49     ` Daniel Jacobowitz
2006-05-31 22:17       ` Daniel Jacobowitz
2006-06-23  8:56         ` Alan Modra
2006-06-26 13:11           ` Daniel Jacobowitz
2006-07-17 16:21         ` Jakub Jelinek
2006-07-17 16:31           ` Daniel Jacobowitz
2006-07-17 20:07           ` DJ Delorie

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=20060525174240.GA5632@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@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).