public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Subject: Re: changes in 'intl'
Date: Mon, 26 Jun 2006 13:11:00 -0000	[thread overview]
Message-ID: <20060626131049.GA28405@nevyn.them.org> (raw)
In-Reply-To: <20060623060312.GF4388@bubble.grove.modra.org>

On Fri, Jun 23, 2006 at 03:33:12PM +0930, Alan Modra wrote:
> On Wed, May 31, 2006 at 11:33:02AM -0400, Daniel Jacobowitz wrote:
> > Index: binutils/ChangeLog
> > 2006-05-31  Daniel Jacobowitz  <dan@codesourcery.com>
> > 
> > 	* Makefile.am: Replace INTLLIBS with LIBINTL everywhere.  Add
> > 	DEPENDENCIES variables for every program.
> 
> This results in libbfd, libopcodes, and libiberty dependencies being
> omitted.  If you specify *_DEPENDENCIES variables, they need to list
> *all* dependencies.  A similar problem occurs if you try to add empty
> rules for the exe files like
> addr2line$(EXEEXT): $(LIBINTL_DEP)
> ar$(EXEEXT): $(LIBINTL_DEP)
> ..
> Automake then decides not to add its own rules.  :-(
> 
> This patch isn't very nice, but I'm not inclined to delve into automake
> to find a more elegant solution.

Oh, that's where this patch went - sorry, it got dropped into my rda@
folder.

Aside from the @LEXLIB@ problem which I fixed the next day, this is
about the best we can do.  There's no user hook to perform the LDADD ->
DEPENDENCIES conversion, unfortunately.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-06-26 13:10 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
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 [this message]
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=20060626131049.GA28405@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).