[Monetdb-developers] buildtools configure.ac
I'm trying to bootstrap buildtools but foud out that buildtools is shipped with an configure.ac which isn't an ac file, but just plain configure itself (as the local bootstrap script just copies it to configure). This is hard to detect for my generic scripts who like to generate a configure from the .ac file. Is there a reason why this ac file exists? If not, I'd be happier if it could just be renamed to configure instead, as I don't think this is the right solution.
There's simply one reason: "enforce" that /bootstrap is run before configure; and as usually, bootstrap creates configure from configure.* . Why * = "ac" and not "ag" or "in" -- well, bascially because there are {Mx,mel,burg}/configure.ac, not {Mx,mel,burg}/configure.ag or {Mx,mel,burg}/configure.in . Both, the top-level "bootstrap" & "configure[.ac]" are just wrappers that call the respective conifugre of Mx, mel, burg . Looking into configure.ac, you might have noticed that it is not "real" configure.ac at all. If the .ac is a problem for some script, feel free to remane it too something else (configure.bs (for "bootstrap", i.e., the "tool" that eventually creates configure)?), but I'd prefer (in fact recommend) to not call it confiure (without extension) as that could suggest that no bootstrap is required, which is not the case. Stefan On Tue, Dec 26, 2006 at 02:29:06PM +0100, Fabian Groffen wrote:
I'm trying to bootstrap buildtools but foud out that buildtools is shipped with an configure.ac which isn't an ac file, but just plain configure itself (as the local bootstrap script just copies it to configure). This is hard to detect for my generic scripts who like to generate a configure from the .ac file. Is there a reason why this ac file exists? If not, I'd be happier if it could just be renamed to configure instead, as I don't think this is the right solution.
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
On 26-12-2006 15:36:41 +0100, Stefan Manegold wrote:
There's simply one reason: "enforce" that /bootstrap is run before configure; and as usually, bootstrap creates configure from configure.* .
Why * = "ac" and not "ag" or "in" -- well, bascially because there are {Mx,mel,burg}/configure.ac, not {Mx,mel,burg}/configure.ag or {Mx,mel,burg}/configure.in .
Both, the top-level "bootstrap" & "configure[.ac]" are just wrappers that call the respective conifugre of Mx, mel, burg .
Looking into configure.ac, you might have noticed that it is not "real" configure.ac at all.
I think it's too challenging to write a script to check whether an .ac file really is an .ac file. Autoconf itself doesn't even do that.
If the .ac is a problem for some script, feel free to remane it too something else (configure.bs (for "bootstrap", i.e., the "tool" that eventually creates configure)?), but I'd prefer (in fact recommend) to not call it confiure (without extension) as that could suggest that no bootstrap is required, which is not the case.
I worked around it by just bootstrapping the separate directories and copying configure.ac to configure. That works for me, but still I find it confusing to find an .ac file which in fact isn't an ac file at all. (The same would hold if it would be called configure.in.)
Fabian, shall I rename buildtools/configure.ac to buildtools/configure.bs (it has to be "processed" by bootstrap, only, not by autogen (.ag) or autoconf (.ac)), or would that cause more problems for you then it would solve? Stefan On Tue, Dec 26, 2006 at 03:46:14PM +0100, Fabian Groffen wrote:
On 26-12-2006 15:36:41 +0100, Stefan Manegold wrote:
There's simply one reason: "enforce" that /bootstrap is run before configure; and as usually, bootstrap creates configure from configure.* .
Why * = "ac" and not "ag" or "in" -- well, bascially because there are {Mx,mel,burg}/configure.ac, not {Mx,mel,burg}/configure.ag or {Mx,mel,burg}/configure.in .
Both, the top-level "bootstrap" & "configure[.ac]" are just wrappers that call the respective conifugre of Mx, mel, burg .
Looking into configure.ac, you might have noticed that it is not "real" configure.ac at all.
I think it's too challenging to write a script to check whether an .ac file really is an .ac file. Autoconf itself doesn't even do that.
If the .ac is a problem for some script, feel free to remane it too something else (configure.bs (for "bootstrap", i.e., the "tool" that eventually creates configure)?), but I'd prefer (in fact recommend) to not call it confiure (without extension) as that could suggest that no bootstrap is required, which is not the case.
I worked around it by just bootstrapping the separate directories and copying configure.ac to configure. That works for me, but still I find it confusing to find an .ac file which in fact isn't an ac file at all. (The same would hold if it would be called configure.in.)
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
On 28-12-2006 13:31:12 +0100, Stefan Manegold wrote:
Fabian,
shall I rename buildtools/configure.ac to buildtools/configure.bs (it has to be "processed" by bootstrap, only, not by autogen (.ag) or autoconf (.ac)), or would that cause more problems for you then it would solve?
That's fine with me, and allows to more nicely solve the problem I got now ;) Thanks!
On Thu, Dec 28, 2006 at 01:33:35PM +0100, Fabian Groffen wrote:
On 28-12-2006 13:31:12 +0100, Stefan Manegold wrote:
Fabian,
shall I rename buildtools/configure.ac to buildtools/configure.bs (it has to be "processed" by bootstrap, only, not by autogen (.ag) or autoconf (.ac)), or would that cause more problems for you then it would solve?
That's fine with me, and allows to more nicely solve the problem I got now ;)
Thanks!
Done. Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
participants (2)
-
Fabian Groffen -
Stefan Manegold