Custom Apache Build System

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Some people don't have openssl-devel installed which will prevent the customapache script from compiling. To check if you have it, run:

rpm -q openssl-devel

to install it, run:

up2date -u openssl-devel

then run the ./build all program again.

Also, if you have an older version of customapache, you may have outdated versions of the configure.* files (unless you've customized them). It's recommended that you delete both configure.* files then run ./build update before building again.

John
 

Quincy

Verified User
Joined
Jun 19, 2003
Messages
8
Location
Houston, TX
What's Wrong?

make[2]: *** [wbmp.lo] Error 1
make[2]: Leaving directory `/usr/local/directadmin/customapache/gd-2.0.15'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/directadmin/customapache/gd-2.0.15'
make: *** [all] Error 2


Wut's Up? :mad:
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Hello,

The error is probably shown farther up in the compile text -- what you pasted isn't able to help me determine your problem.

Solving it via the forum is generally quite difficult, so send us your ip and root password, and we'll be able to help you out. :)

John
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Hello,

The customapache script now support apache 1.3.28 and mod_ssl 2.8.15.

You must change your configure.apache_ssl file to have 1.3.28 instead of 1.3.27, or you can just delete the file. Deletion is easiest.

To update:

Code:
cd /usr/local/directadmin/customapache
rm configure.*  (manually edit configure.apache_ssl if you have it customized)
./build clean
./build update
./build all

This was probably mentioned before, but some people run into some problems with the script. Normally, they don't have openssl-devel or patch. To install them, run:

Code:
up2date -u patch
up2date -u openssl-devel
John
 

Clearhosting

Verified User
Joined
Jul 31, 2003
Messages
6
Hello all, i had a question because i am a total noob.
Im buying 2 new servers and i always paid someone to update and configure my servers for me now i want to save money by switching from ensim to DA and i had some questions:

Whats the step through plan like this:
1. Install linux (wich version) we now have redhat 7.3
2. Install custom apache from this post
3. install DA

Am i done installing then ? or what ? Well as i said total noob questions :):eek:
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Hello,

Zend is built into the package, but is not included with the
Code:
./build all
command. You can just run
Code:
./build zend
to install it. Follow the directions at the begging of this thread for answers to the questions it asks.

John
 

ProWebUK

Verified User
Joined
Jun 9, 2003
Messages
2,326
Location
UK
just thought i'd mention php is now at 4.3.3 stable :)

updated all our current plesk / ensim servers to 4.3.3 and everything running fine, may want to update the script to include 4.3.3 over 4.3.2 :D

Chris
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Thanks for the info.

Anyone who wants the new php can simply type:
Code:
cd /usr/local/directadmin/customapache
./build update
./build php
and press 'n' for recompiling the other libraries.

John
 

Dixiesys

Verified User
Joined
Aug 2, 2003
Messages
137
Location
The South
Am I correct in assuming these php updates are part of the latest version?

Everything I check seems to indicate the versions match so I'm just checking :)
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Hello,

Yes, that's the beauty of the customapache script. All I do is upload the new php tar.gz file, change the version # in the build script, and let people know there is an update and to run ./build update; ./build all (or ./build php for php). This allows all systems, on any OS, to be kept updated quite easily.

John
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
No, we just added the new php. You can add freetype by downloading the source into the customapache directory, untarring it, ./configure; make; make install; it .. then add the required configure lines when building gd or php (im not sure what actually uses it)

John
 

Icheb

Verified User
Joined
Sep 15, 2003
Messages
556
Location
The Netherlands
It worked great, had a total downtime of about 2 minutes.
The only problem is, i wanted to try to get the asp apache module to work, but it really doesn't want to compile...

But ok, you can't have everything, the installer is quite good, allthough isn't it better for most users to send all ./configure and make output (including the errors) to a log file for later review instead of the terminal screen you are useing ?
 

snickn

Verified User
Joined
Oct 7, 2003
Messages
23
Location
los angeles, cali
/usr/bin/ld: cannot find -lltdl
collect2: ld returned 1 exit status
make: *** [libphp4.la] Error 1

This is while trying to build Zend with the custom buildapache. Just wanted to let everyone know.. I'll also post how I fixed it (if I fix it)
 

jasonyates

Verified User
Joined
Sep 24, 2003
Messages
79
I dont have a problem as such but after i ran the Custom Apache build thing i get this error message when restarting httpd.

Stopping httpd: [ OK ]
Starting httpd: [Sun Oct 12 12:34:16 2003] [warn] module perl_module is already
loaded, skipping
[Sun Oct 12 12:34:17 2003] [warn] NameVirtualHost 65.77.219.27:80 has no Virtual
Hosts
[Sun Oct 12 12:34:17 2003] [warn] NameVirtualHost 65.77.219.27:443 has no Virtua
lHosts
[ OK ]

It restarts ok and has been working ok for a few days but i thought i better check.
 

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
8,923
Hello,

The virtualhosts is normal, it means apache was told to listen on those ips, but nobody has been added to them yet. It's just a warning, that doesn't matter.

The perl message also isn't too important. You can comment out one of the LoadModule directives for perl in the /etc/httpd/conf/httpd.conf if you want. What happened was we have perl included in the httpd.conf file, and when mod_perl is compiled, it decides to add it again. One entry will be ignored, but it's anything but fatal :)

John
 
Top