[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Johnson wrote: > On Tuesday 30 Sep 2003 13:27, Mike Tidball wrote: >>What is the procedure after a failed ./configure. >>I have found that I need to add an option but what has the last >>./configure already written.Am I best to delete the directory and unzip >>the .tgz again or does configure write files elseware? > You can do a 'make clean' which should clear out anything that was written. I'm not a configure/autoconf guru, but I think "make clean" will fail if configure didn't create the makefile's. Creating makefiles is usually the last thing that configure does, or at least near to last. Removing the directory, and reextracting the files from the tar file should always work, and is well recommended if you are getting confused! Configure doesn't usually write files elsewhere. You should normally build and test as an unprivileged user, as it is conceivable that the configure scripts are malicious (the tendency is to believe they aren't if they actually build a working version of the desired program, if you checked the MD5 checksum of the tar ball at least they fooled the package maintainer as well as you!). 9 times out of 10, you can just rerun configure with the new options. If you are ambitious you can scrub manually the "config.guess" and other "config.*, auto4* etc" files created when configure is run, but probably best to leave that for people who are practiced in such things. Usually reproducibiliy is a key goal, and if it happens to build because of some weird step you can't later reproduce, YOU may be toast when the server dies and the boss says build me a new one just like the old one. Simon -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/ealgGFXfHI9FVgYRAtj/AKCKJKz9mk27iubRIeyyJgbtsLMf7wCffpUC H1KEs1la1qT6Exf86oplwjg= =pa1A -----END PGP SIGNATURE----- -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.