From: DJ Delorie <dj@redhat.com>
To: neroden@twcny.rr.com
Cc: 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 16:12:00 -0000 [thread overview]
Message-ID: <200212082253.gB8MruD28484@greed.delorie.com> (raw)
In-Reply-To: <3DF3C9D7.90204@twcny.rr.com> (message from Nathanael Nerode on Sun, 08 Dec 2002 17:38:15 -0500)
> 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.
But I tested that specific case, and it worked fine.
I'll try it again. Full build twice, second time nothing happens.
Remove libiberty/Makefile and "make" again...
$ grep 'Configuring in' /tmp/foo
Configuring in libiberty
Configuring in opcodes
Configuring in bfd
Configuring in binutils
Configuring in gas
Configuring in ld
Configuring in gprof
Configuring in etc
Configuring in utils
Same thing if I just do "touch libiberty/Makefile".
I wonder if it's something gnu-make specific.
No, wait... bfd/Makefile depends on opcodes/Makefile, which then
depends on libiberty/Makefile.
Ok, feel free to change all the configure:configure dependencies to
Makefile:Makefile dependencies.
next prev parent reply other threads:[~2002-12-08 22:53 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 ` re-re-re-re-configuring Nathanael Nerode
2002-12-08 16:12 ` DJ Delorie [this message]
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=200212082253.gB8MruD28484@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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