Dear Rüdiger On Mon, Feb 7, 2011 at 3:42 PM, "Plüm, Rüdiger, VF-Group" <[email protected]> wrote:
> buildconf is a shell script. so you need to start it with bash, not with > python. Sorry, sometimes Windows confuses me, I am so used to Linux. I get this far C:\Users\zdavatz\software\apr>sh buildconf buildconf: checking installation... buildconf: python version 2.5 (ok) buildconf: autoconf version 2.67 (ok) buildconf: libtool version 2.4 (ok) buildconf: copying libtool helper files using /c/MinGW/bin/libtoolize buildconf: creating include/arch/unix/apr_private.h.in ... autom4te-2.67: m4sugar/m4sugar.m4: no such file or directory autoheader-2.67: failed to run '/c/MinGW/bin/autom4te-2.67': Bad file number buildconf: creating configure ... autom4te-2.67: m4sugar/m4sugar.m4: no such file or directory buildconf: generating 'make' outputs ... buildconf: rebuilding rpm spec file and no "configure" file is created. My MinGW setup is correct as far as I can tell. Best Zeno
