This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: (toplevel patch) Configure in Makefile, version 3.
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: ac131313 at redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Thu, 5 Dec 2002 19:44:58 -0500
- Subject: Re: (toplevel patch) Configure in Makefile, version 3.
> 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