David, On 2013-02-26 22:44, David DeHaven wrote: > > config.status does other things too, it's quite handy.
Yes. The only problem with it - I typically forget to copy it out before doing rm -rf build -Dmitry > > -DrD- > >> Awsome! >> >> Thanks, >> /Staffan >> >> On 26 feb 2013, at 16:31, David DeHaven <david.deha...@oracle.com> wrote: >> >>> >>> build/<target dir>/config.status --recheck >>> >>> -DrD- >>> >>>> Thanks Dmitry, >>>> >>>> I was looking for a standard way of doing this. While a custom script >>>> helps, it would be nice to have the support in the source. >>>> >>>> /Staffan >>>> >>>> On 26 feb 2013, at 14:53, Dmitry Samersoff <dmitry.samers...@oracle.com> >>>> wrote: >>>> >>>>> Staffan, >>>>> >>>>> 1. Keep config.log somewhere >>>>> 2. Attached script or something similar will do the trick >>>>> >>>>> -Dmitry >>>>> >>>>> On 2013-02-26 13:05, Staffan Larsen wrote: >>>>>> Is there a shorthand for re-running configure on one of my >>>>>> configurations without having to re-type the configure arguments I >>>>>> used when creating the configuration? >>>>>> >>>>>> I have a number of configurations and when I have to re-run >>>>>> configure, I have to both specify the correct --with-conf-name and >>>>>> then the correct configure options I used last time. I know I can >>>>>> find those in the configure-arguments file. >>>>>> >>>>>> What I would like is something simliar to "make CONF=..." but for >>>>>> configure: "sh configure CONF=...". >>>>>> >>>>>> Thanks, /Staffan >>>>>> >>>>> >>>>> >>>>> -- >>>>> Dmitry Samersoff >>>>> Oracle Java development team, Saint Petersburg, Russia >>>>> * Give Rabbit time, and he'll always get the answer >>>>> <rr.txt> >>>> >>> >> > -- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia * Give Rabbit time, and he'll always get the answer
