apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <c...@force-elite.com>
Subject Re: [patch 00/17] successful msys/mingw build
Date Sat, 15 Jul 2006 02:38:43 GMT
Justin Erenkrantz wrote:
> For the record, here's a quick dump of what I downloaded/installed
> from mingw.sf.net:
> - MinGW 5.0.3
> - MSYS-1.0.11-2004.04-30-1
> - msysDTK-1.0.1
> - msys-autoconf-2.5.9.tar.bz2 (extract to /usr)
> - msys-libtool-1.5.tar.bz2 (extract to /usr)

I also needed:
Python-2.5b2 (to run buildconf)

So that I could run buildconf.

1) checkout source
2) open msys
3) run buildconf
4) run ./configure with:
    --enable-experimental-libtool CFLAGS="-O0"
5) go get a beer (configure is really slow...)
6) run make

Then I ran into problems:
make[1]: Entering directory `/c/work/asf/apr'
/c/work/asf/apr/libtool --silent --mode=compile gcc   -O0 
-I/c/work/asf/apr/include/arch/win32 -I./include/arch/unix 
-I/c/work/asf/apr/include  -o passwd\apr_getpass.lo -c 
passwd\apr_getpass.c && touch passwd\apr_getpass.lo
gcc.exe: passwdapr_getpass.c: No such file or directory
gcc.exe: no input files
make[1]: *** [passwd\apr_getpass.lo] Error 1
make[1]: Leaving directory `/c/work/asf/apr'
make: *** [all-recursive] Error 1

If I manually changed the libtool line, to use / as path deliminators, 
it works.

So, attached is a patch to modify buildconf to generate a 'correct' 
build-rules.mk on win32.

Is this the correct way to do it, or is something wrong in my setup?


View raw message