Sent from Proton Mail mobile -------- Messaggio originale -------- Il 19 Ott 2023, 09:08, Matthias Apitz < g...@unixarea.de> ha scritto: El día miércoles, octubre 18, 2023 a las 08:45:16p. m. +0200, Matthias Apitz escribió: > > Hello salvad...@freebsd.org, > > I'm writing to you as MAINTAINER of the port lang/gcc10. > > When compiling the port lang/gcc10 with poudriere on a recent > 14.0-CURRENT system and very recent ports from git, I encounter > in /var/log/messages lines like these: > > Oct 18 17:44:45 jet kernel: pid 21011 (cc1plus), jid 169, uid 65534: exited on signal 11 (core dumped) > Oct 18 17:45:17 jet kernel: pid 30102 (cc1plus), jid 169, uid 65534: exited on signal 11 (core dumped) > ... I'm recompiling lang/gcc10 again with poudriere and while this is writing the log file .../latest-per-pkg/gcc10-10.4.0_1.log I attached another shell cmd which reads this log with tail -f and writes each line again to another file with a timestamp in front; looks like this: 08:21:31: ===> Installing existing package /packages/All/mpc-1.3.1_1.pkg 08:21:31: [140-CURRENT-ports20231014-job-01] Installing mpc-1.3.1_1... 08:21:31: [140-CURRENT-ports20231014-job-01] Extracting mpc-1.3.1_1: ...... done 08:21:31: ===> gcc10-10.4.0_1 depends on shared library: libmpc.so - found (/usr/local/lib/libmpc.so) 08:21:31: ===> Returning to build of gcc10-10.4.0_1 08:21:31: =========================================================================== 08:21:31: =================================================== 08:21:31: ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 08:21:31: ===> Configuring for gcc10-10.4.0_1 ... (still running). So at the end we can match the signal 11 lines from /var/log/messages exactly with what the make engine was doing at that time. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Hello, I have reproduced your issue both on 13.2 and 14.0: https://cirrus-ci.com/build/5307810582364160 Please let me know what are the results of your tests. Then we will see if the issue needs more research or not. It might be that some test is being made and is expected to fail. In case we need to work on this, I suggest to file a bug report in bugzilla. Cheers, Lorenzo Salvadore
