compiling modperl with mingw on win32

2002-11-12 Thread pascal barbedor



Hi

on win32,

I have compiled perl 5.8 with mingw gcc 3.2 and 
dmake.
it gives a very fast perl.

is it possible to build mod_perl 1.99_07 with this 
perl and an apache 2043 build with msvc6 ?

(is it possible to compile apache with gcc3.2 
?)

because I am trying it , and it don't seems to work 
.


i have

-probabely harmless no library found for 
c:\apache\lib\libapr... at the perl makefile.pl step
(though i can see the files are there)

and later a lot of undefined references to 
apr_ in modperl_handler.c and others.

is it because there is an incompatibility format 
between msvc6 *.lib files and what gcc 3.2 is expecting to find ?


thanks 

pascal


Re: compiling modperl with mingw on win32

2002-11-12 Thread Randy Kobes
On Tue, 12 Nov 2002, pascal barbedor wrote:

 Hi
 
 on win32,
 
 I have compiled perl 5.8 with mingw gcc 3.2 and dmake.
 it gives a very fast perl.
 
 is it possible to build mod_perl 1.99_07 with this perl and an
 apache 2043 build with msvc6 ? (is it possible to compile
 apache with gcc3.2 ?)

In looking through some of the list archives of various groups,
it looks possible in principle to compile Apache with mingw, but
I've no experience doing so. The Apache sources however don't
seem to recognize 'mingw' in the configuration set-up.
 
 because I am trying it , and it don't seems to work . 
 i have
 
 - probabely harmless no library found for
 c:\apache\lib\libapr... at the perl makefile.pl step (though i
 can see the files are there)
 
 and later a lot of undefined references to apr_ in
 modperl_handler.c and others.
 
 is it because there is an incompatibility format between msvc6
 *.lib files and what gcc 3.2 is expecting to find ?

From what I understand, mingw is designed to be compatible at
this level, although there's no guarantees ... If you write some
simple test program that just calls one of the functions 
in a library created with msvc6, does it compile and link 
successfully?

The fact that the libraries weren't even found though suggests
the build didn't even get to the stage of trying to find the
symbols. For one thing, the message above indicates it's looking
in an '/Apache/lib' directory - is this where Apache2 lives? If
so, might it be a problem with the names of the libraries? The
libraries distributed with the Apache Win32 binary don't always
have the 'lib' prefix, which may be assumed in the '-l...' link
option that mingw uses ...

-- 
best regards,
randy kobes