From: Nathanael Nerode <neroden@twcny.rr.com>
To: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: (toplevel patch) Configure in Makefile, version 3.
Date: Thu, 05 Dec 2002 16:54:00 -0000 [thread overview]
Message-ID: <20021206004458.GA11878@doctormoo> (raw)
> Ok, now that I've recovered from my `pleasant suprise' :-) I'm finding
>that, given a build that barfs in GDB, it tries to re-configure BFD
>when
>re-made.
>
> It's being run with `gmake -k -j 2'. Anyone else noticed this?
Not me.
Have you got it working when the build doesn't crash in gdb?...
I've done oodles of builds with the current versions of the files, but
I'm sure there are builds I haven't tried. :-/
The only reasons it should try to reconfigure BFD are:
* bfd/Makefile was changed (or 'touch'ed) by something
* libiberty/Makefile was changed (or 'touch'ed) by something
* config.status at the top level was changed (or 'touch'ed) by something
I can't imagine why either of those things would happen.
Is it really a problem, anyway? BFD is reconfigured with the same
arguments it was configured with the previous time...
It *will* try to rebuild BFD. That is correct. BFD's Makefile should
be clever enough to do nothing in this case, though it might not be.
Hmm. When GNU make runs BFD's Makefile, maybe BFD's Makefile decides
that it's out of date? I haven't poked BFD's Makefile enough.
Can you figure out which level of Make is trying to rebuild BFD's
Makefile?
--Nathanael
next reply other threads:[~2002-12-06 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 16:54 Nathanael Nerode [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-04 18:27 Nathanael Nerode
2002-12-05 12:10 ` Andrew Cagney
2002-12-05 12:15 ` DJ Delorie
2002-12-05 12:20 ` Andrew Cagney
2002-12-05 12:22 ` DJ Delorie
2002-12-05 12:30 ` Andrew Cagney
2002-12-05 12:36 ` Daniel Jacobowitz
2002-12-05 12:48 ` Andrew Cagney
2002-12-05 12:51 ` DJ Delorie
2002-12-05 15:15 ` Andrew Cagney
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=20021206004458.GA11878@doctormoo \
--to=neroden@twcny.rr.com \
--cc=ac131313@redhat.com \
--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