RE: Win32 build problems libapreq2-2.04_03-dev
On Wed, 8 Sep 2004, Craig Dayton wrote: After updating both Apache2 and mod_perl on the W2K Server, there are still some problems in building libarpeq2-2.04_03-dev on Win32. Current software levels are: Apache/2.0.50 (Win32) mod_perl/1.99_16 Perl/v5.8.4 Server When invoking 'nmake perl_glue', 'nmake perl_test', or nmake perl_install each will return the same error message. Nmake correctly detects that Apache2 is installed at 'E:\Apache2'. . . . nmake perl_glue writing...xs//Makefile.PL writing...xs/Apache/Makefile.PL [ info] generating script t/TEST Can't find the mod_perl include dir (reason: path D:\Apache2\include doesn't exi st) at E:/Perl/site/lib/Apache2/Apache/Build.pm line 1715. NMAKE : fatal error U1077: 'E:\Perl\bin\perl.exe' : return code '0x2' Is it only the perl_* targets that have this problem, or does nmake test also get confused with the wrong drive letter? Could you send me (off-list) your $APACHE2\build\config_vars.mk file, as well as the top-level Makefile? Thanks. -- best regards, randy -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
RE: Win32 build problems libapreq2-2.04_03-dev
After updating both Apache2 and mod_perl on the W2K Server, there are still
some problems in building libarpeq2-2.04_03-dev on Win32.
Current software levels are:
Apache/2.0.50 (Win32) mod_perl/1.99_16 Perl/v5.8.4 Server
When invoking 'nmake perl_glue', 'nmake perl_test', or nmake perl_install
each will return the same error message. Nmake correctly detects that
Apache2 is installed at 'E:\Apache2'.
.
.
.
nmake perl_glue
writing...xs//Makefile.PL
writing...xs/Apache/Makefile.PL
[ info] generating script t/TEST
Can't find the mod_perl include dir (reason: path D:\Apache2\include doesn't
exi
st) at E:/Perl/site/lib/Apache2/Apache/Build.pm line 1715.
NMAKE : fatal error U1077: 'E:\Perl\bin\perl.exe' : return code '0x2'
If this error message is indeed attempting to find files in the directory,
'D:\Apache2\include', it won't because the directory doesn't exist. Its not
clear to me where the build process is picking up the reference to
'D:\Apache2\include'.
Scanning both the directories 'E:\Perl' and 'E:\Apache2' for 'D:\Apache2',
the file
'E:\Perl\site\lib\Apache2\auto\libaprext\extralibs.ld' was found to contain
references to 'D:\Apache2\lib'. After correcting the invalid references, the
problem still exists.
Windows XP Pro is having the exact same problem too.
Thanks, Craig
-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 01, 2004 21:15
To: Craig Dayton
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Win32 build problems libapreq2-2.04_03-dev
On Wed, 1 Sep 2004, Craig Dayton wrote:
Hi Randy,
For the Windows 2000 Server system its running mod_perl/1.99_14, so
this explains the missing file problem. The current
mod_perl will get
built on this system.
Great - that should resolve that problem ...
I'm not sure what the problem is here - all of the Apache
references
above use E:\ as the drive, which appears correct. When you did the
'perl Makefile.PL', did a confirmation come up asking you which
Apache to use? If so, was it the correct one, including the drive
letter?
Yes Yes.
I tried 'perl Makefile.PL' and it found the correct Apache2 location
and I responded 'yes' to the prompt. Also, I tried 'perl Makefile.PL
--with-Apache2=E:/Apache2'. In both cases its trying to find Apache
on a another drive. In the first instance, it was expecting Apache2
on drive Z: which was a valid network drive. After disconnecting the
network drive Z:, the second attempt was expecting Apache to be on
drive D: (CD-ROM).
I take it this is at the
nmake test
stage? I can't see why it would be looking in different
drives at this point; it's already found Apache ...
[ debug] can't figure out Apache revision, from string:
'', using
a non-existin g revision 0
Its interesting that an empty string is referenced in the output
above.
Do you have an Apache/TestConfigData.pm somewhere on your system,
either in the main Perl tree or under a .apache-test
directory under,
eg, C:\ or E:\? If so, does it help if you move it out of
the way and
run the tests again?
No. TestConfigData.pm is only located at 'E:\Perl\site\lib\Apache\'.
Looking at this module, I see the following:
$Apache::TestConfigData::vars = {'httpd' =
'\Apache2\bin\Apache.EXE',}; I tried changing this to
'E:\Apache2\bin\Apache.EXE'. This didn't help.
What if you tried moving this file completely away?
I tried adding 'E:\Apache2\bin' to the Path environmental variable
just see if that might help. It didn't. The 'nmake test' is still
failing for the same apparent reason of not being able to resolve
Apache2's location. Also, I find it interesting that
apxs.bat failed
its 3 query attempts too.
Thanks, Craig
The problem with apxs.bat on Win32 is related to something
that changed recently in Apache-Test; I haven't been able to
trace why these warnings are arising ...
To try to eliminate one possibility, what happens if you
move $APACHE2\bin\apxs.bat somewhere outside of the PATH,
and then do
nmake perl_glue
nmake perl_test
That should work - it's only the
nmake test
target that requires apxs.
Also, there's a file $APACHE2\build\config_vars.mak with
various settings used by apxs - for those that reference a
drive, is the letter correct?
--
best regards,
randy
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Win32 build problems libapreq2-2.04_03-dev
On Tue, 31 Aug 2004, Craig Dayton wrote: Does anyone have an idea how to resolve either of the following errors when building libapreq2-2.04_03-dev on either a Windows 2000 Server or on Windows XP Pro (SP2)? Thanks, Craig Windows 2000 Server Apache/2.0.49 mod_perl/1.99_15 perl/v5.8.4 The build process on W2K Server made it all the way to the 'nmake perl_glue' step on returned the following message. E:/Projects\libapreq2-2.04-dev\glue\perl\xsbuilder\Apache\Upload\Apache__Upl oad. h(20) : fatal error C1083: Cannot open include file: 'modperl_common_util.h': No such file or directory I've cc'd the apreq list on this ... The modperl_common_util.h header file should have been copied over to your $APACHE2\include directory when you installed mod_perl (assuming you compiled mod_perl yourself, and are using a version = 1.99_15). Is there a file $APACHE2\include\modperl_common_util.h on your system (where $APACHE2 is the root of your Apache2 installation)? Windows XP Professional SP2 Apache/2.0.49 mod_perl/1.99_16 perl/v5.8.4 After the 'nmake test' step the following error messages below were was returned. For some reason the 'nmake test' process thinks the root directory for Apache2 is on drive D: which in this case is a CD-ROM even though root directory has been explictly specified. perl makefile.pl --with-apache2=E:\Apache2 . . . Microsoft (R) Program Maintenance Utility Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. . . nmake test 22 tests run: 22 passed, 0 failed, 0 not implemented. cd E:\Projects\LIBAPR~1.04- nmake /nologo /f E:\Projects\LIBAPR~1.04-\win32\test_cgi.mak CFG=test_c gi - Win32 Release APACHE=E:\Apache2 APREQ_HOME=E:\Projects\LIBAPR~1.04- AP R_LIB=E:\Apache2\lib\libapr.lib APU_LIB=E:\Apache2\lib\libaprutil.lib cl.exe /nologo /MD /W3 /O2 /D WIN32 /D NDEBUG /D _CONSOLE /D _MBC S /IE:\Apache2\include /IE:\Projects\LIBAPR~1.04-\src /FpE:\Projects\LIBAP R~1.04-\win32\libs\test_cgi.pch /YX /FoE:\Projects\LIBAPR~1.04-\win32\libs\\ /FdE:\Projects\LIBAPR~1.04-\win32\libs\\ /FD /c E:\Projects\LIBAPR~1.04-\env\t est_cgi.c test_cgi.c link.exe @E:\DOCUME~1\cadayton\LOCALS~1\Temp\nm42.tmp if not exist E:\Projects\LIBAPR~1.04-\env\t\cgi-bin mkdir E:\Projects \LIBAPR~1.04-\env\t\cgi-bin copy E:\Projects\LIBAPR~1.04-\win32\libs\test_cgi.exe E:\Projects\LIBAPR ~1.04-\env\t\cgi-bin\test_cgi.exe 1 file(s) copied. cd E:\Projects\LIBAPR~1.04- cd E:\Projects\LIBAPR~1.04-\env E:\Perl\bin\perl.exe t\TEST.PL -apxs E:\Apache2\bin\apxs.bat [ debug] loading custom config data from: 'E:\Perl\site\lib\Apache\TestConfigData.pm' [ debug] overlaying custom config data APXS (E:\Apache2\bin\apxs.bat) query for SBINDIR failed APXS (E:\Apache2\bin\apxs.bat) query for TARGET failed APXS (E:\Apache2\bin\apxs.bat) query for SYSCONFDIR failed *** at this point a dialog appear request to mount drive D *** [ debug] configuring httpd [ debug] can't figure out Apache revision, from string: '', using a non-existin g revision 0 [ debug] generating ..\c-modules\apache_httpd_test.h [ error] configure() has failed: Can't figure out what Apache server generation we are running at E:/Perl/site/lib/Apache/TestServer.pm line 98. [warning] forcing Apache::TestConfig object save [ debug] generating conf\apache_test_config.pm [ debug] saving config data to apache_test_config.pm [warning] run 't/TEST -clean' to clean up before continuing NMAKE : fatal error U1077: 'E:\Perl\bin\perl.exe' : return code '0x1' Stop. I'm not sure what the problem is here - all of the Apache references above use E:\ as the drive, which appears correct. When you did the 'perl Makefile.PL', did a confirmation come up asking you which Apache to use? If so, was it the correct one, including the drive letter? Do you have an Apache/TestConfigData.pm somewhere on your system, either in the main Perl tree or under a .apache-test directory under, eg, C:\ or E:\? If so, does it help if you move it out of the way and run the tests again? -- best regards, randy kobes -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
RE: Win32 build problems libapreq2-2.04_03-dev
On Wed, 1 Sep 2004, Craig Dayton wrote:
Hi Randy,
For the Windows 2000 Server system its running mod_perl/1.99_14, so this
explains the missing file problem. The current mod_perl will get built on
this system.
Great - that should resolve that problem ...
I'm not sure what the problem is here - all of the Apache
references above use E:\ as the drive, which appears correct.
When you did the 'perl Makefile.PL', did a confirmation come
up asking you which Apache to use? If so, was it the correct
one, including the drive letter?
Yes Yes.
I tried 'perl Makefile.PL' and it found the correct Apache2 location and I
responded 'yes' to the prompt. Also, I tried 'perl Makefile.PL
--with-Apache2=E:/Apache2'. In both cases its trying to find Apache on a
another drive. In the first instance, it was expecting Apache2 on drive Z:
which was a valid network drive. After disconnecting the network drive Z:,
the second attempt was expecting Apache to be on drive D: (CD-ROM).
I take it this is at the
nmake test
stage? I can't see why it would be looking in different
drives at this point; it's already found Apache ...
[ debug] can't figure out Apache revision, from string: '', using a
non-existin g revision 0
Its interesting that an empty string is referenced in the output above.
Do you have an Apache/TestConfigData.pm somewhere on your
system, either in the main Perl tree or under a .apache-test
directory under, eg, C:\ or E:\? If so, does it help if you
move it out of the way and run the tests again?
No. TestConfigData.pm is only located at 'E:\Perl\site\lib\Apache\'.
Looking at this module, I see the following:
$Apache::TestConfigData::vars = {'httpd' = '\Apache2\bin\Apache.EXE',};
I tried changing this to 'E:\Apache2\bin\Apache.EXE'. This didn't help.
What if you tried moving this file completely away?
I tried adding 'E:\Apache2\bin' to the Path environmental variable just see
if that might help.
It didn't. The 'nmake test' is still failing for the same apparent reason
of not being able to resolve Apache2's location. Also, I find it
interesting that apxs.bat failed its 3 query attempts too.
Thanks, Craig
The problem with apxs.bat on Win32 is related to something
that changed recently in Apache-Test; I haven't been able to
trace why these warnings are arising ...
To try to eliminate one possibility, what happens if you
move $APACHE2\bin\apxs.bat somewhere outside of the PATH,
and then do
nmake perl_glue
nmake perl_test
That should work - it's only the
nmake test
target that requires apxs.
Also, there's a file $APACHE2\build\config_vars.mak with
various settings used by apxs - for those that reference a
drive, is the letter correct?
--
best regards,
randy
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
