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 06:24:27 GMT
Justin Erenkrantz wrote:
> On 7/14/06, Paul Querna <chip@force-elite.com> wrote:
>> Is this the correct way to do it, or is something wrong in my setup?
> That patch should be fine.  This is due to Python being a 'true' Win32
> build - so it has path delimiters of '\' which the msys make doesn't
> accept (I referred to this in my earlier post, FWIW - perhaps too
> cryptically though).  In a perfect world, we would conditionalize this
> mapping to only be done on Win32 too; but it's essentially a no-op on
> Unix platforms.  So, +1.

Committed in r422146.

> BTW, I saw on #apr that you were having an issue with:
> /mingw/lib/libmingw32.a(main.o)(.text+0x106):main.c: undefined
> reference to `WinMain@16'
> This is caused by apr_app.c being pulled in incorrectly (also
> mentioned before too).  It defines main() and should not be linked
> with the APR DLL.  We need to teach gen-build to ignore that one file.
> (Ideally, we should delete it from the tree, but the test programs
> use it and doing so would cause us to have to tweak MSVC++'s build
> system and I really don't want to do that...)

Thanks, killed it, and it works.

I also got apr-util to compile -- I tried using the bundled expat, but 
it broke due to autoconf sillyness -- So I built it using an external 
Expart 2.0.0 and everything built great.


View raw message