On 2022-07-23, Mik J wrote:
> Hello Stuart, thank you for your answer.I didn't understand exactly what you
> meant by "The main problem occurs if the build directory is on NFS" when I
> first read it.I was surprised that this problem only occurs when building
> php. When building other package
So you have the case that really doesn't work, "The main problem occurs if
the build directory is on NFS"
But for PHP there really is no reason to build yourself, all the available
packages are built anyway, flavours don't affect this.
--
Sent from a phone, apologies for poor formatting.
On
We do bulk builds with ports tree, package and log directories, etc
on NFS _all_ _the_ _time_ and there is not normally a problem.
The main problem occurs if the build directory is on NFS.
(A second problem with cmake when packages are built by more than
one machine and the clocks are different bet
On Fri, May 07, 2021 at 11:08:00PM +, Mik J wrote:
> Hello,
> Does anyone knows why compiling php from ports systematically fails ? It's
> been since openbsd 6.8 that it acts this way
Why do you ask this on misc@ instead of ports@ ?
Second, it actually works for all of us... so it must be so
Hello,
Does anyone knows why compiling php from ports systematically fails ? It's been
since openbsd 6.8 that it acts this way
/usr/ports/pobj/php-7.4.19/bin/install -c -m 644
/usr/ports/pobj/php-7.4.19/php-7.4.19/modules/opcache.so
/usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/lib/php-7.4/mo
5 matches
Mail list logo
