Greg Stein wrote: > > On Sat, Feb 17, 2001 at 04:10:55PM -0000, [EMAIL PROTECTED] wrote: > >... > > --- Makefile.in 2001/02/01 21:54:22 1.32 > > +++ Makefile.in 2001/02/17 16:10:54 1.33 > > @@ -55,3 +55,6 @@ > > > > exports.c: $(EXPORT_FILES) > > (cat $(EXPORT_FILES) | ../build/buildexports.sh ..) > $@ > > + > > +# wtf does this have to be explicit???? > > +exports.lo: exports.c > > What OS and make are you using?
3.2-STABLE FreeBSD, using the make that comes with it. > Did you use the debug flags to 'make' to see > wtf it was thinking? No. The amount of output that produces from these makefiles is ridiculous. I could be persuaded to look but it isn't high on my list! > I can't imagine it would need to be explicit. Too many other things would > break. Possibly, it is related to the very dynamic nature of exports.c. > Possibly, it grabbed all the timestamps at the start of the make, and didn't > notice the updated timestamp after exports.c was rebuilt. ??? That seems rather unlikely! Make wouldn't work at all in this case. > Did a second 'make' run fix it? Or did it just persist in being broken? (if > the former, it might support my hypothesis of grabbing timestamps) It persisted in being broken. Cheers, Ben. -- http://www.apache-ssl.org/ben.html "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff
