New build system (BETA)

It's not a custombuild bug. Try:
Code: 
yum -y install curl-devel

Or if you're using Debian:
Code: 
apt-get -y install curl-devel

Marcin said:
A weird error appears now after d/l of custombuild.tar.gz, unpacking, setting options.conf and doing:

./build update
./build all d

checking for cURL in default path... not found
configure: error: Please reinstall the libcurl distribution -
easy.h should be in <curl-dir>/include/curl/

*** There was an error while trying to configure php. Check the configure/ap2/configure.php5 file

I can see curl-7.16.2.tar.gz, but there's no folder for it after ./build all d - curl was not unpacked and built before ./build tries to compile php, hence an above error.

Several times I have deleted the entire custombuild folder, redownloaded custombuild.tar.gz and tried to recompile, but the above error happens every time.
Click to expand...
 
smtalk said:
It's not a custombuild bug. Try:
Or if you're using Debian:
Code: 
apt-get -y install curl-devel
Click to expand...

All right.. but why did "./build update; ./build all d" so far downloaded and compiled curl on its own?!

Note: this happened when I tried using "custombuild" script for default DA install (touch /root/.custombuild etc).
 
Marcin, curl is being built as in customapache, nothing has been changed.
 
Last edited:
smtalk said:
Marcin, curl is being built as it customapache, nothing has been changed.
Click to expand...

Oh. That's a bit confusing, though, because in the meantime I reinstalled using old "customapache" script (no /root/.custombuild file before DA install), downloaded custombuild.tar.gz, unpacked it, rebuilt the installation, and in custombuild folder I can see curl-7.16.2 folder with config.status file and everything configured and built during custombuild process, not customapache process!

If customapache installs curl, why does custombuild bother just downloading it again if it's not using it? And if custombuild script is used in default install process, why doesn't it compile and install curl and other tools (gd, libpng, etc) in the first place?

Let's even say that default custombuild process doesn't install them by default for the rest of the system. OK. But why then custombuild process when ran again doesn't configure and compile all those tools for its own use in directadmin/custombuild directory, just downloads them (./build update DOES download them)?
 
Marcin said:
Oh. That's a bit confusing, though, because in the meantime I reinstalled using old "customapache" script (no /root/.custombuild file before DA install), downloaded custombuild.tar.gz, unpacked it, rebuilt the installation, and in custombuild folder I can see curl-7.16.2 folder with config.status file and everything configured and built during custombuild process, not customapache process!

If customapache installs curl, why does custombuild bother just downloading it again if it's not using it? And if custombuild script is used in default install process, why doesn't it compile and install curl and other tools (gd, libpng, etc) in the first place?

Let's even say that default custombuild process doesn't install them by default for the rest of the system. OK. But why then custombuild process when ran again doesn't configure and compile all those tools for its own use in directadmin/custombuild directory, just downloads them (./build update DOES download them)?
Click to expand...

Thank you for the report, I'm changing checks now. :) Checks will be fixed into 1.0.6 version of custombuild.
 
Chrysalis said:
Is the httpd.conf supposed to include all the comments from the basic apache template?

Example on the normal DA httpd.conf its small and easy to edit everything in one file.

For apache 2.2 on this build script everything is in seperate files (I understand this bit because apache 2.2.x changed to this system) so have to find the right file to edit. But also the config is like this.



And so on, so lots of commented documented stuff to scroll by so bloating the config file.
Click to expand...

It's fixed in 1.0.6. It's very light now :)
 
Marshall said:
Not sure how much testing has been done with this on CentOS 5 so far, but an issue I have run into while using this has been with the zZipLib. The build script defaulted to 0.10.82 for CentOS 5 which kept erroring on the make process, I had to manually go download and install 0.13.47 and install it to get it working. Not sure why it was doing that but just a heads up for any CentOS 5 testers that are getting errors when they use script.


edit - I notice theres a check in the script that looks for fedora release and if found will use 13.47 but for some reason wasnt being triggered by CentOS 5, not sure why.
Click to expand...

Fixed in 1.0.6. Please update to it :)
 
Marcin said:
A weird error appears now after d/l of custombuild.tar.gz, unpacking, setting options.conf and doing:

./build update
./build all d

checking for cURL in default path... not found
configure: error: Please reinstall the libcurl distribution -
easy.h should be in <curl-dir>/include/curl/

*** There was an error while trying to configure php. Check the configure/ap2/configure.php5 file

I can see curl-7.16.2.tar.gz, but there's no folder for it after ./build all d - curl was not unpacked and built before ./build tries to compile php, hence an above error.

Several times I have deleted the entire custombuild folder, redownloaded custombuild.tar.gz and tried to recompile, but the above error happens every time.
Click to expand...

There should be no problems with 1.0.6. :)
 
I'm going to celebrate my birthday now (May 2nd). Happy testing!
 
Now I have tryed the latest version of custombuild and now cert and key files were not created and also after compile I get next:

Invalid command 'php_admin_flag', perhaps misspelled or defined by a module not included in the server configuration

:rolleyes:
 
LionRock said:
Now I have tryed the latest version of custombuild and now cert and key files were not created and also after compile I get next:

Invalid command 'php_admin_flag', perhaps misspelled or defined by a module not included in the server configuration

:rolleyes:
Click to expand...

If you're using an old version of DirectAdmin update it to 1.295 and run:
Code: 
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

Let me know how everything is going now :) There should be no issues with certificate.
 
I dont know how to update DA :D In DA update does not work so .... I cant update it :/

Happy Birthday Martynas!!! ;)


Regards
 
You must log in or register to reply here.
Back
Top