This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: re-re-re-re-configuring
- From: DJ Delorie <dj at redhat dot com>
- To: neroden at twcny dot rr dot com
- Cc: binutils at sources dot redhat dot com, gdb-patches at sources dot redhat dot com, gcc-patches at sources dot redhat dot com
- Date: Sun, 8 Dec 2002 17:53:56 -0500
- Subject: Re: re-re-re-re-configuring
- References: <20021206102555.GA15028@redhat.com> <200212061850.gB6Io3m26371@greed.delorie.com> <3DF3C9D7.90204@twcny.rr.com>
> 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.