build all stuck in loop

tnuz

Verified User
Joined
Jan 12, 2006
Messages
23
Location
Canada
After a new install of DA on Rocky 8.4, i set "php1_release=8.0" in options.conf, and not use 7.4 at all.
After that I ran "./build all y"

At some point the build ends up in a loop saying:
Code:
Trying to make imagick-3.5.1 PHP extension...
make: getcwd: No such file or directory
make: *** No targets specified and no makefile found.  Stop.

When I set "php2_release=7.4" and a "./build all y", it all compiles good; even in PHP 8.0

Is PHP 7.4 still needed for new DirectAdmin installs?
Is there a way of getting rid of it completely, as I don't plan to have any sites using it?
 
Last edited:
At some point the build ends up in a loop saying:
Code:
Trying to make imagick-3.5.1 PHP extension...
make: getcwd: No such file or directory
make: *** No targets specified and no makefile found.  Stop.
This could help you?



PHP 8.0.12, 7.4.25 (CVE)


22 Oct 2021 PHP 7.4.25 Released! The PHP development team announces the immediate availability of PHP 7.4.25. This is a security release. All PHP 7.4 users are encouraged to upgrade to this version. For source downloads of PHP 7.4.25 please visit our downloads page, Windows source and binaries...




Also do forumseacrh before post on error message ;)


and
 
Thanks for the response.
Maybe I missed it, but it's not really helpful.

I am aware that we need to migrate from 7.4 to 8.x; that's what I'm doing (read my post)

I did search for a solution in the forum and beyond, but found no answer to this specific case.
The two links to forum articles are indeed related to imagick, but not to what is happening during "./build all y" when only PHP 8.0 is selected.

I started off with a clean, standard install. Then replaces 7.4 to 8.0 for "php1_release" in options.conf. Also enabled "imagick" and couple of other changes, before running "./build all y". This is my way of installing multiple servers with the same configuration. I'm sure that there is a better way, but this worked for me for the last odd years. Starting with a proven-to-be-reliable setup, then make the needed/wanted changes. For the current project I need to install ten servers the exact same way, to replace 10 older machines. Doing a basic install

Just this time the build script got into a loop that I could only ctrl-c out of.
When I do everything the same on a clean install, but without imagick, there is no problem. Installing imagick afterwards doen't case any trouble either. Sio there is a workaround, but in my opinion there is unwanted behaviour by the build script.
 
Was ony pointing out combi php 8 DA and imagick have problems, and that @smtalk did updated some , if did don't work maybe that update didn't have your case in it for now.

And so still BUG, you can however also post a link there to your topic here.
 
I recall having the same issue earlier this year with ./build all. When imagick is enables the build all command fails, setting imagick to no in php_extensions.conf it finishes without any issue. Then afterwards, ./build imagick also works without issues.

Maybe this is something @smtalk can look into?
 
I'm not sure how the build process works in detail, but it makes me think that it freaks out by replacing PHP 7.4 with 8.0. I think build all tries to build imagick for PHP 7.4, while it's being replaced. That might explain "No such file or directory".
When replace PHP 7.4 with 8.0, then do a build all, then enable imagick and build it, it all goes well.
 
Back
Top