2009/10/21 Michael Biebl <[email protected]>: > 2009/10/21 <[email protected]>: >> On Wed, 21 Oct 2009, Michael Biebl wrote: >> >>> 2009/10/21 <[email protected]>: >>>> >>>> On Wed, 21 Oct 2009, Michael Biebl wrote: >>>> >>>>> 2009/10/21 <[email protected]>: >>>>>> >>>>>> On Wed, 21 Oct 2009, Michael Biebl wrote: >>>>>> >>>>>>> 2009/10/21 <[email protected]>: >>>>>>>> >>>>>>>> when doing 'make clean' it should not need to run configure first. >>>>>>> >>>>>>> Ist that from a release tarball or a git snapshot? >>>>>> >>>>>> git snapshot, especially after doing the autoconf -fvi. the system >>>>>> spends >>>>> >>>>> That's the wrong command. >>>>> >>>>> You should use autoreconf -vfi in a fresh git checkout. >>>> >>>> sorry, I typed the wrong thing in the e-mail >>>> >>>>> After that ./configure && make clean works as expected for me. >>>> >>>> I do >>>> autoreconf -fvi >>>> make clean >>> >>> How do you expect "make" to work without running ./configure before? >>> If you have a Makefile's from a previous ./configure run, it's >>> absolutely correct behaviour that after a autoreconf -vfi, a configure >>> run is first done before you can run make. >>> >>> To sum up, everything works as it should. >> >> I would not expect to be able to do a normal make, but since a make clean >> just deletes files (and the same files, not matter what the config options >> are) I would expect it to work. > > Well, that's how automake/autoconf works. > If the timestamps of build input files change, the build system is > automatically re-generated.
Btw, since you run autoreconf anyway there is a much nicer (and quicker way to get rid of the old build files): git clean -x -d -f autoreconf -vfi Will give you a clean working state ready to run ./configure && make -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
