Hi !

ok it compiles from vc+ !

(i had to drop a void apachecore.lib file in the vc6 file list, that pointed
to a strange

c:\unzipped\ap\apache-1.3\src\release\apachecore.lib . suppose some one
forgot it here.


and when adding directive in httpd.conf and running i have the reassuring
line :

Apache/ 1.3.19 (win32) mod_perl/1.25 PHP/4.0.4pl1 running...

about the test i type nmake test in c:\mod_perl-1.25 dir from comman window
and got this line

makefile(533) fatal error U1035: syntax error : expected ':' or '='
separator stop.

i don't know where is the test file is and if i should test at this point



thanks a lot for your help anyway.


note that it
continues to fail from perl

here is the output of perl makefile.pl after the changes suggested :

(maybe some perl bad installation)
****************************************************************************
*****
Commande ou nom de fichier incorrect
Commande ou nom de fichier incorrect
Unable to find a perl 5 (by these names: C:\Perl\bin\Perl.exe miniperl perl
perl5 perl5.6.0, in these dirs: C:\Program Files\TextPad 4\
C:\ELJ-WIN32\SMALLEIFFEL\BIN C:\ELJ-WIN32\LCC\BIN C:\WINDOWS
C:\WINDOWS\COMMAND C:\PERL\BIN\ C:\PROGRA~1\PANDAS~1\PANDAA~1.0 C:\Perl\bin)
Writing Makefile for Apache
Writing Makefile for Apache::Connection
Writing Makefile for Apache::Constants
Writing Makefile for Apache::File
Commande ou nom de fichier incorrect
Running '..\0 -IC:\Perl\lib C:\Perl\lib\ExtUtils\xsubpp -v 2>&1' exits with
status 16777215 at (eval 121) line 17.
Commande ou nom de fichier incorrect
Running '..\0 C:\Perl\lib\ExtUtils\xsubpp temp000 2>&1' exits with status
16777215 at (eval 121) line 43.
Writing Makefile for Apache::Leak
Writing Makefile for Apache::Log
Writing Makefile for Apache::ModuleConfig
Writing Makefile for Apache::PerlRunXS
Writing Makefile for Apache::Server
Writing Makefile for Apache::Symbol
Writing Makefile for Apache::Table
Writing Makefile for Apache::URI
Writing Makefile for Apache::Util
Writing Makefile for mod_perl

Beginning with version 1.3.15, Apache uses a different convention for
Win32 module names. Correspondingly, the name of the mod_perl module
built here has been changed from ApacheModulePerl.dll to mod_perl.so.
Please see INSTALL.win32 for further details.
************************************************************************





----- Original Message -----
From: "Randy Kobes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 6:00 PM
Subject: Re: problem compiling under win98


> On Thu, 26 Apr 2001 [EMAIL PROTECTED] wrote:
>
> > i have succesfully compiled apache 1_3.19 under win 98 with vc6
> > and dsw project
> >
> > I'm trying to compile mod_perl 1_25 under windows 98 the same way
> > i downloaded the source 1_25 and found the modperl.dsp
> > for vc++ compiling
> > i followed the install.win32 notes but when compiling there are
> > missing files :
> [ ... ]
> > c:\apache_1.3.19\src\include\ap_config.h(114) : fatal error C1083:
> > Cannot open include file: 'os.h': No such file or directory
> [ ... ]
>
> Apache_1.3.19 changed the way that the header os.h was included.
> To fix this, if you're building mod_perl.so from Visual Studio,
> include
> C:\apache_1.3.19\src\os\win32
> as well as
> C:\apache_1.3.19\src\include
> in the list of include directories. If you're building this
> from command line arguments, find the line in the mod_perl
> top-level Makefile.PL
>
> s!(/D "WIN32")!/I "$apache_inc" /I "$perl_inc" $1!;
>
> and change this to (all on one line)
>
> s!(/D "WIN32")!/I "$apache_inc" /I "$apache_inc/../os/win32"
> /I "$perl_inc" $1!;
>
> Whichever way you choose, does this then build OK? If so,
> the tests might fail for a different reason, due to another
> change in apache_1.3.19 in setting the relative server root
> to the path of the apache binary. As a temporary fix,
> in t\docs\startup.pl and t\docs\rl.pl, find occurrences of
> $Apache::Server::CWD
> and change this to the path to the mod_perl build directory
> (eg, "C:\mod_perl-1.25").
>
> best regards,
> randy kobes
>

Reply via email to