From: Julien L. <ju...@fa...> - 2007-05-03 09:55:36
|
Keith MARSHALL wrote, quoting me: >> I just also thought of the fact that I have >> "MAKEFLAGS=--no-print-directory" by default on my systems; thus >> maybe that's why it was less clear to me. > > I don't understand; why would that impact on the diagnostics resulting > from a failed attempt to run MSVC's lib command? With less verbose from make, out of the common messages tend to stand out; so I took the warning message as an error one. If the message had been drowned in "entering/leaving directory..." lines, I probably wouldn't have noticed it, or it wouldn't have been the last output from the make command and I wouldn't have thought much of it. > I don't understand what you mean by a `MinGW shell'. Do you mean > MSYS shell, used for native applications development with MinGW, as > opposed to the special shell environment required to compile MSYS > itself; i.e. the msysDVLPR environment? By 'MinGW shell', I mean an typical MSYS shell with MSYSTEM=MINGW32. I guess it's a misnomer. >> at least that's how it works with 'automake' ;> > > It's how it works if I make config.h a prerequisite for all of the > project's object files. I don't need to use automake, to establish > that dependency, and as you may remember, I utterly loathe and detest > that particular autotool; throw away comments like this aren't going > to change my opinion of it. I do remember, thus the smiley in my comment. Julien |