From: Nathanael Nerode <neroden@twcny.rr.com>
To: DJ Delorie <dj@redhat.com>,
rth@redhat.com, ac131313@redhat.com, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com, gcc-patches@sources.redhat.com
Subject: Re: re-re-re-re-configuring
Date: Sun, 08 Dec 2002 14:40:00 -0000 [thread overview]
Message-ID: <3DF3C9D7.90204@twcny.rr.com> (raw)
In-Reply-To: <200212061850.gB6Io3m26371@greed.delorie.com>
DJ Delorie wrote:
>>So who broke the make dependencies such that we
>>re-run configure *every* time you type "make"?
>
>
> I debugged this, and the dependencies look right, almost (sigh).
> Basically, it boils down to this:
>
> .PHONY: configure-libiberty maybe-configure-libiberty
> maybe-configure-libiberty:
> configure-libiberty: libiberty/Makefile
>
> Considering target file `all-libiberty'.
> File `all-libiberty' does not exist.
> Considering target file `configure-libiberty'.
> File `configure-libiberty' does not exist.
> Considering target file `libiberty/Makefile'.
> Pruning file `config.status'.
> Pruning file `intl/Makefile'.
> Finished prerequisites of target file `libiberty/Makefile'.
> Prerequisite `config.status' is older than target `libiberty/Makefile'.
> Prerequisite `intl/Makefile' is older than target `libiberty/Makefile'.
> No need to remake target `libiberty/Makefile'.
> Finished prerequisites of target file `configure-libiberty'.
> Must remake target `configure-libiberty'.
> Successfully remade target file `configure-libiberty'.
> Finished prerequisites of target file `all-libiberty'.
> Must remake target `all-libiberty'.
>
> So, even though configure-libiberty is .PHONY and its prereqs are OK,
> it gets "rebuilt" anyway. Consequently...
>
> Considering target file `bfd/Makefile'.
> Pruning file `config.status'.
> Pruning file `configure-libiberty'.
> Pruning file `opcodes/Makefile'.
> Finished prerequisites of target file `bfd/Makefile'.
> Prerequisite `config.status' is older than target `bfd/Makefile'.
> Prerequisite `configure-libiberty' of target `bfd/Makefile' does not exist.
> Prerequisite `opcodes/Makefile' is older than target `bfd/Makefile'.
> Must remake target `bfd/Makefile'.
>
> Even though configure-libiberty is .PHONY, it was "rebuilt" and so
> bfd/Makefile must also be rebuilt.
Arrrr. Right. Phony target problem. :-/
>
> I did a test changing this line:
>
> bfd/Makefile: configure-libiberty
>
> to this:
>
> configure-bfd: configure-libiberty
>
> and it seems to work. I'll work up a patch.
>
And the reason I didn't do this was due to a different bug.
If libiberty is changed, then since
configure-bfd: configure-libiberty
configure-bfd: bfd/Makefile
bfd/Makefile won't be regenerated.
The correct solution is to change it to
bfd/Makefile: libiberty/Makefile
which I will work up a simple patch for if nobody beats me to it.
(I'll replace all maybe-configure-X: configure-X dependencies with
maybe-configure-X: X/Makefile dependencies.)
next parent reply other threads:[~2002-12-08 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021206102555.GA15028@redhat.com>
[not found] ` <200212061850.gB6Io3m26371@greed.delorie.com>
2002-12-08 14:40 ` Nathanael Nerode [this message]
2002-12-08 16:12 ` re-re-re-re-configuring DJ Delorie
2002-12-08 19:28 ` re-re-re-re-configuring Daniel Jacobowitz
2002-12-08 20:38 ` re-re-re-re-configuring 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=3DF3C9D7.90204@twcny.rr.com \
--to=neroden@twcny.rr.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@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