Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH] sim: generate build dependencies on the fly
Date: Wed, 13 Jul 2011 02:04:00 -0000	[thread overview]
Message-ID: <CAJaTeTpoc=UUiePTTBNiRA=dREKdYABMfXQ+HdCsDWaa4wuG0w@mail.gmail.com> (raw)
In-Reply-To: <m3d3hffbq1.fsf@fleche.redhat.com>

On Tue, Jul 12, 2011 at 17:08, Tom Tromey wrote:
> GDB arranges for generated files to be built early, via order-only
> dependencies.  Order-only dependencies ensure that merely touching one
> of the generated files doesn't cause a global recompile.
>
> # Ensure that generated files are created early.  Use order-only
> # dependencies if available.  They require GNU make 3.80 or newer,
> # and the .VARIABLES variable was introduced at the same time.
> @GMAKE_TRUE@ifdef .VARIABLES
> @GMAKE_TRUE@$(all_object_files): | $(generated_files)
> @GMAKE_TRUE@else
> $(all_object_files) : $(generated_files)
> @GMAKE_TRUE@endif

oh, ok.  i saw that, but didnt quite grok what was going on.  this
will make things much easier to work with, so i'll take this approach
and send an updated patch.

> Tom> Finally I thought there was some problem with multiple entries in VPATH,
> Tom> but I cannot find that in the docs.  Perhaps it is one of those ancient
> Tom> incorrect memories.  It would bear testing with a non-GNU make.
>
> Mike> sounds like all good reasons to use automake :).  otherwise all the
> Mike> files in common/ need manual deps (like gdb does with files in
> Mike> subdirs), and that semi-defeats the purpose of this in the first
> Mike> place.
>
> Yeah.  I am not actually sure how well Automake would currently handle
> sources in "../common/".  Neither here nor there I guess.

pretty sure it wouldnt care.  it can handle relative paths in subdirs
last i looked (foo/blah.c), so i dont see why relative paths in a
sibling tree (../foo/blah.c) would be different.  knock on wood :x.

> Fedora includes the BSD make (yum install bmake); I assume other distros
> do too.  So you could try a build with that.

yes, Gentoo includes many alternative makes including bmake and pmake.
Gentoo works natively on BSD systems too you know :).

but would saying "yes, this works on current BSD makes" be
satisfactory when the complaint in the manual alludes to "ancient makes" ?
-mike


  reply	other threads:[~2011-07-12 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1310436152-8693-1-git-send-email-vapier__46811.2245122485$1310436164$gmane$org@gentoo.org>
2011-07-12 19:49 ` Tom Tromey
2011-07-12 20:59   ` Mike Frysinger
     [not found]   ` <CAJaTeTqM-Kr3Nrr4JKyfpys7=+aWk_YJCA+=AensJyBTUvg4dQ__24418.5384632603$1310503395$gmane$org@mail.gmail.com>
2011-07-12 21:15     ` Tom Tromey
2011-07-13  2:04       ` Mike Frysinger [this message]
     [not found]       ` <CAJaTeTpoc=UUiePTTBNiRA=dREKdYABMfXQ+HdCsDWaa4wuG0w__27433.0390304842$1310506984$gmane$org@mail.gmail.com>
2011-07-13 13:59         ` Tom Tromey
2011-07-13 20:17           ` Mike Frysinger
2011-07-12  5:18 Mike Frysinger
2011-12-03 18:24 ` Mike Frysinger

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='CAJaTeTpoc=UUiePTTBNiRA=dREKdYABMfXQ+HdCsDWaa4wuG0w@mail.gmail.com' \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=toolchain-devel@blackfin.uclinux.org \
    --cc=tromey@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