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 22 July 2022 18:48:46 Mik J <mikyde...@yahoo.fr> wrote:
Hello Stuart and thank you for your answer.

I'm not hiding anything, I have a machine and mounted /usr/ports/pobj
10.x.x.x:/home/data/pobj on /usr/ports/pobj type nfs (wxallowed, v3, udp, timeo=100, retrans=101)

Now you're telling me you always mount NFS shares, it makes me think that my problem might happen because both are VMs and not pure hardware machines.
But the clocks were synchronised on the same NTP server.
So maybe it happens only on VMs.


For some packages I use Flavors when I build them.


Regards

Le vendredi 22 juillet 2022 à 15:21:53 UTC+2, Stuart Henderson <stu.li...@spacehopper.org> a écrit :


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 between those machines,

but that is less common).


Is there something you're not telling us which makes this build

different to a standard build? That might give some clues.


(And, if not, why not just use the normal packages?)



On 2022-07-22, Mik J <mikyde...@yahoo.fr> wrote:

 Hello again, everyone, Marc,

Do you have an idea why I had this error

Link to /usr/ports/packages/amd64/ftp/debug-php-7.4.19.tgz

`/usr/ports/pobj/php-7.4.19/fake-amd64/.fake_done' is up to date.

Extracting debug info from /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/php-7.4

Warning: no debug-info in /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/php-7.4

dwz: /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/.debug/php-7.4.dbg: .debug_info section not present

objcopy: /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/.debug/php-7.4.dbg: Invalid operation

*** Error 1 in /usr/ports/pobj/php-7.4.19/fake-amd64 (debug-pkg/Makefile:26 '/usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/.debug/php-7.4.dbg')

*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3050 '_copy-debug-info': @cd /usr/ports/pobj/php-7.4.19/fake-amd64 && exec /usr/...)

*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2137 '/usr/ports/packages/amd64/all/php-apache-7.4.19.tgz': @cd /usr/ports/lang/p...)

*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2623 '_internal-package': @case X${_DEPENDS_CACHE} in X) _DEPENDS_CACHE=$( mktem...)

*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2602 'package': @:; cd /usr/ports/lang/php/7.4 && PKGPATH=lang/php/7.4 make _inte...)

*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2155 '/var/db/pkg/php-7.4.19/+CONTENTS': @cd /usr/ports/lang/php/7.4 && PKGPATH=l...)

*** Error 2 in /usr/ports/lang/php/7.4 (/usr/ports/infrastructure/mk/bsd.port.mk:2602 'install': @lock=php-7.4.19; export _LOCKS_HELD=" php...)

Marc told me if I had mounted a NFS share and there would be a clock problem- Yes I mounted a NFS share where /usr/ports is on the remote server- But No, both servers are NTP synchronised on the same NTP server and have the same time# ntpctl -sa

1/1 peers valid, clock synced, stratum 4



So it's strange.

Anyway the work around is not to have a NFS share mounted.

Regards



Le mercredi 27 avril 2022 à 19:45:00 UTC+2, Mik J <mikyde...@yahoo.fr> a écrit :



 Hello Marc,

You were right, I did mount a NFS share.Both servers (client and NFS server) are correctly NTP synchronised but when I do not use a NFS share it works properly.So I don't know what side effect makes this error.

Thank you again for your answer last year.



   Le samedi 8 mai 2021, 10:28:02 UTC+2, Marc Espie <es...@nerim.net> a écrit :



 On Fri, May 07, 2021 at 11:08:00PM +0000, 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 something

you're doing.



Renaming /usr/ports/pobj/php-7.4.19/fake-amd64/debug-pkg/Makefile.new to Makefile

> Extracting debug info from /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/php-7.4

[...]

Installing /usr/ports/lang/php/7.4/pkg/php74_fpm.rc as /usr/ports/pobj/php-7.4.19/fake-amd64/etc/rc.d/php74_fpm

===>  Building package for php-7.4.19

Create /usr/ports/packages/amd64/all/php-7.4.19.tgz

Creating package php-7.4.19

Creating package debug-php-7.4.19

Link to /usr/ports/packages/amd64/ftp/php-7.4.19.tgz

Link to /usr/ports/packages/amd64/ftp/debug-php-7.4.19.tgz

`/usr/ports/pobj/php-7.4.19/fake-amd64/.fake_done' is up to date.

> Extracting debug info from /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/php-7.4

Warning: no debug-info in /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/php-7.4

dwz: /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/.debug/php-7.4.dbg: .debug_info section not present

objcopy: /usr/ports/pobj/php-7.4.19/fake-amd64/usr/local/bin/.debug/php-7.4.dbg: Invalid operation





oh look, it's doing the same thing TWICE. But wait: there's a Makefile

involved.



Now why would it do that ?



It could only happen if somehow, the dates are completely wacked.



Would you by any chance use NFS for your pobj tree, or anything that

would get your clock to act strangely ?...









--

Please keep replies on the mailing list.

Reply via email to