On 5/9/22 12:43, Stuart Henderson wrote:
You might get some more usable trace if you build PHP yourself including debug symbols ("make FETCH_PACKAGES= prepare && make DEBUG=-g package") and run that.

Even if we know whether the SIGBUS is due to misaligned access or one of the other conditions that can result in this, without a backtrace it will be hard to find which source code is involved.


I tried to build the php8 port with debug informations but I got the message:

===>  Building package for apache-httpd-2.4.53p1
Create /usr/packages/arm/all/apache-httpd-2.4.53p1.tgz
Error: Libraries in packing-lists in the ports tree
       and libraries from installed packages don't match

I used the snapshot ports.tar.gz on my armv7 snapshot system.

On Monday the new snapshot packages for the arm/armv7 platform were pushed to the mirrors. And now my php-fpm problem, I've tested php-8.0.17p2 and php-8.1.4p1, is solved. In my opinion the cause for my issue was, that I use a snapshot operating system but the last snapshot packages for armv7 were build on 2021-11-16.

If I'm wrong please correct me. But maybe I should not use snapshot on the armv7 platform. The snapshots for the operating system are quite often updated. But the snapshots for the packages are rebuild not so frequently (in contrast to the amd64 platform). And this could lead to some errors. I also could stay on the snapshot based operating system and build my required ports. But how can I prevent that the required build dependencies, like apr, brotli for php8 are pulled as packages (which maybe don't match)? In my opinion for the armv7 platform it also makes sense that the required build dependencies are build from the ports and are not used from (the outdated) packages.

Thanks,
Sven

Reply via email to