Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] sim/common/Make-common.in: Correct dependency for LIBDEPS
Date: Tue, 24 May 2005 15:29:00 -0000	[thread overview]
Message-ID: <20050524141153.GA3561@nevyn.them.org> (raw)
In-Reply-To: <20050524140827.GA13850@calimero.vinschen.de>

On Tue, May 24, 2005 at 04:08:27PM +0200, Corinna Vinschen wrote:
> Hi,
> 
> LIBDEPS in sim/common/Make-common.in defines the dependencies used
> to figure out what has to be build, while EXTRA_LIBS defines what
> libraries are used for building.
> 
> The same difference is made for INTLDEPS vs. INTLLIBS.  Nevertheless,
> LIBDEPS depends on $(INTLLIBS) instead of $(INTLDEPS), which would
> be the correct dependency.
> 
> The below patch fixes that.  Ok to apply?
> 
> 
> Corinna
> 
> 	* Make-common.in (LIBDEPS): Correctly use INTLDEPS for dependency
> 	check.

Yes, this is OK.  Nice catch.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-24 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 14:22 Corinna Vinschen
2005-05-24 15:29 ` Daniel Jacobowitz [this message]
2005-05-24 15:43   ` Corinna Vinschen

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=20050524141153.GA3561@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.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