DeveloperSide.NET Forums
February 22, 2020, 07:14:25 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Apache 2.0.48 build broken  (Read 16967 times)
0 Members and 1 Guest are viewing this topic.
admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« on: November 01, 2003, 02:01:11 AM »

It looks like the newly implemented changes that took place from 2.0.47 to 2.0.48 that had something to do with ssl.conf broke the build process.

Quote

copy docs\conf\ssl-std.conf "\Apache2\conf\ssl.default.conf" <.y
The system cannot find the file specified.
NMAKE : fatal error U1077: 'copy' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"E:\Program Files\Microsoft Visual Studio .NET\VC7\BIN\nmake.exe"' : return code '0x2'
Stop.


From the first look at it, it seems that "ssl-std.conf" is never formed from "ssl-std.conf.in".

If I'm not mistaken, if you build 2.0.47 and move all the old config files from httpd-2.0.47\docs\conf over before the build, the build process should complete.

Or, since this fails on the "final file copying over to the new directory process after everything is built", just put a new ssl.conf into the newly created Apache2\conf directory and everything should be complete.

Here is probably the culprit, from the changlog
Quote

Ensure that ssl-std.conf is generated at configure time, and switch to using the expanded config variables to work the same as httpd-std.conf PR: 19611 [Thom May]
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
Jorge
Customer, Basic Support
Guru
*****
Posts: 544

jorge_schrauwen@msn.com
View Profile WWW
« Reply #1 on: November 01, 2003, 12:40:45 PM »

It builds ok here, my apache is installed in c:\server\apache, but i build it to c:\server\apache-new and then if apache-new runs replace it with the old one, and had no problems whatsoever btw i used vs.net 7.1
Logged

Anonymous
Guest
« Reply #2 on: November 01, 2003, 04:40:44 PM »

Others on Usenet have reported the same problem as I have.  Others are saying it works.

It might be VS.NET 7.0 specific....

Or,

I used the short "nmake /f Makefile.win installr", I'll try specifing more variables...

Also, this was just a default built, no zlib or ssl.
Logged
Jorge
Customer, Basic Support
Guru
*****
Posts: 544

jorge_schrauwen@msn.com
View Profile WWW
« Reply #3 on: November 01, 2003, 04:49:17 PM »

well i used nmake from vs.net 2003(7.1)
so maybe it's becouse i installed to a diferent dir? than my previuse version?
Logged

admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« Reply #4 on: November 01, 2003, 04:58:45 PM »

Tried...
nmake /f Makefile.win SERVERNAME="localhost" PORT=80 INSTDIR="E:\www2\Apache2" installr

Still the same problem.

Did you do it with deflate and mod_ssl?
Do you have conf\ssl.conf present?

In 7.1, nmake might be set, by default, to just keep on going.  While under 7.0, it breaks out on the first fault.  So it could be that the same thing is happening on your side, but its just not noticed.  If that is so, ssl.conf should be missing.
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« Reply #5 on: November 01, 2003, 07:23:17 PM »

Tried it with zlib and openssl, via the IDE...

same thing again...
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« Reply #6 on: November 01, 2003, 10:10:44 PM »

I installed the .msi version and even though install.log claims
Quote

Installing Apache HTTP 2.0 server with
 DomainName =  localhost
 ServerName =  localhost
 ServerAdmin = webmaster@localhost
 ServerPort =  80
 ServerRoot =  E:/Program Files/Apache Group/Apache2
Rewrote E:/Program Files/Apache Group/Apache2/conf/httpd-win.conf
 to E:/Program Files/Apache Group/Apache2/conf/httpd.default.conf
Successfully removed E:\Program Files\Apache Group\Apache2\conf\httpd-win.conf
Duplicated E:/Program Files/Apache Group/Apache2/conf/httpd.default.conf
 to E:/Program Files/Apache Group/Apache2/conf/httpd.conf
Duplicated E:/Program Files/Apache Group/Apache2/conf/ssl.default.conf
 to E:/Program Files/Apache Group/Apache2/conf/ssl.conf
Duplicated E:/Program Files/Apache Group/Apache2/conf/magic.default
 to E:/Program Files/Apache Group/Apache2/conf/magic
Duplicated E:/Program Files/Apache Group/Apache2/conf/mime.types.default
 to E:/Program Files/Apache Group/Apache2/conf/mime.types
Successfully removed E:\Program Files\Apache Group\Apache2\conf\InstallConf.awk


...ssl.conf is also missing from Apache2/conf
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« Reply #7 on: November 02, 2003, 01:11:45 AM »

I got to the bottom of this...

Basically, httpd-2.0.48\docs\conf\ssl-std.conf is missing from the distribution.

This causes 3 files to never be created...

ssl.default.conf
ssl.conf
dbmmanage.pl

This happens because httpd-2.0.48\docs\conf\ssl-std.conf.in is never processed. (...forming ssl-std.conf)
OR, this file was never ment to be processed under win32 and ssl-std.conf is just plain missing...As I can not find any mention of the extra @values@ used in ssl-std.conf.in anywhere in the distro.

The good news is, this is the last step of the build/install process.  The resulting Apache2 directory contains everything it should, except these 3 files.

You can see this all at the very end of Makefile.win

And this would explain why some people are claiming that their build finished!

------------------

Looking at the source of 2.0.47, ssl-std.conf is present, while ssl-std.conf.in is not.

The difference between 2.0.47 ssl-std.conf and 2.0.48 ssl-std.conf.in is that the later contains more layers of @values@ that need to be processed/resolved.

We might actually get away with taking .47 ssl-std.conf and placing it into .48
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
Jorge
Customer, Basic Support
Guru
*****
Posts: 544

jorge_schrauwen@msn.com
View Profile WWW
« Reply #8 on: November 02, 2003, 08:01:56 AM »

I checked my and ssl.conf was indeed missing, not that i need it, i reused my old configfiles.
Logged

admin
Administrator
Master of All Subjects
*****
Posts: 3272


View Profile WWW Email
« Reply #9 on: November 03, 2003, 05:37:11 PM »

I made a post to...

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24329

...the apache bug db.

I still have major unresolved bugs that I reported from months ago that no one has touched, (see the bug section of the Apache build instructions -- http://www.devside.net/web/server/win32/apache-ssl-zlib ), so there is no telling if this one is going to get resolved untill 2.1.

I think there is only one guy doing 400 bugs, and the back log is something like 6 months!!!
Logged

DeveloperSide.NET
Advanced PHP and MySQL Solutions for your Web Design and Development needs with Web.Developer Server Suite.
poscribes
Member
*
Posts: 1


View Profile
« Reply #10 on: November 06, 2003, 03:50:24 PM »

OK Guys, first time post but a good result for all I hope.

I am using WinXP-Pro with VS.net and have successfully compiled and am now running 2.0.48 with SSL after simply taking the ssl-std.conf file from the 2.0.47 source code (found in httpd-2.0.47\docs\conf\ssl-std.conf) and putting in the same corresponding directory for 2.0.48 before doing any of the compile commands.

Needless to say it worked just fine!  No other changes were made anywhere.  It really does look as though Apache just forgot to include the file for windows.

I hope everyone is as successful. :D
Logged
PoDuck
Guest
« Reply #11 on: February 22, 2004, 07:06:44 AM »

It appears that 2.0.48 does include ssl-std.conf, but it is instead named ssl-std.conf.in.

You can rename the file to ssl-std.conf, or you can open Makefile.win and change the two instances of ssl-std.conf to ssl-std.conf.in.

No reason to get into 2.0.47 sources.
Logged
Anonymous
Guest
« Reply #12 on: February 22, 2004, 08:25:39 AM »

Have you read the posts in this thread?

ssl-std.conf.in has @ variables that will NOT be processed.  That was the main point!  The mechanism to process those variables has been left out.  The only thing that will be processed if you do as you have suggested, are the @@ variables.

Look into your newly formed ssl.conf file.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.9 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!