> I haven't used the configure tool much before while building from source > and am wondering if I want to configure in new options or change old > ones do I need to include all the origional configuration options I used > or will it 'remember' these and just add or change the new options I use?
This probably won't help you much with whatever you're compiling right now, but has long-term benefits: I've gotten into the habit of creating a file called "configure.script", and putting the configure line in there. Remember to set the executable bit (chmod u+x configure.script) and invoke that script. This is something I've learned from running into your exact problem too many times. It's also great for refining the configure arguments when something goes pop partway through the compile. And yes, I even wrote a script to back up all my configure.script files. Saves much time when (re)building machines, as well as when compiling an upgraded version. Cheers, James -- ...so there I am at ten thousand feet with a power drill in one hand, a takeaway menu in the other, no parachute and a _very_ suprised expression...
pgp00000.pgp
Description: PGP signature
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
