<br><br><div class="gmail_quote">On Mon, May 14, 2012 at 12:25 PM, Anand Babu Periasamy <span dir="ltr"><<a href="mailto:abperiasamy@gmail.com" target="_blank">abperiasamy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, May 14, 2012 at 11:46 AM, Emmanuel Dreyfus <<a href="mailto:manu@netbsd.org">manu@netbsd.org</a>> wrote:<br>
> Kaleb S. KEITHLEY <<a href="mailto:kkeithle@redhat.com">kkeithle@redhat.com</a>> wrote:<br>
><br>
>> > Well, my problem is that python 2.5, python 2.6 and python 2.7 are not<br>
>> > detected by configure. One need to patch configure in order to build<br>
>> > with python 2.x (x> 4) installed.<br>
>><br>
>> Seems like it would be easier to get autoconf and automake from the<br>
>> NetBSD packages and just run `./autogen.sh && ./configure`<br>
><br>
> I prefer patching the configure script. Running autogen introduce build<br>
> dependencies on perl just to substitute a string on a single line:<br>
> that's overkill.<br>
><br>
<br>
</div>Who ever builds from source is required to run autogen.sh to produce<br>
env specific configure and build files. </blockquote><div><br>Not quite. That's the whole point of having a configure script in the first place - to detect the environment at build time. One who builds from source should not require to run autogen.sh, just configure should be sufficient. Since configure itself is a generated script, and can possibly have mistakes and requirements change (like the one being discussed), that's when autogen.sh must be used to re-generate configure script.<br>
<br>In this case however, the simplest approach would actually be to run autogen.sh till either:<br><br>a) we upgrade the release build machine to use newer aclocal macros<br><br>b) qualify geo-replication to work on python 3 and remove the check.<br>
<br>Emmanuel, since the problem is not going to be a long lasting one (either of the two should fix your problem), I suggest you find a solution local to you in the interim.<br><br>Even better, if someone can actually test and qualify geo-replication to work on python 3 it would ease solution "b" sooner.<br>
<br>Avati<br><br></div></div>