Re: Problem with the package builds

On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > Am 10.07.23 um 23:26 schrieb Kevin Oberman: >> On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling > > wrote: >>Am 10.07.23 um 08:15 schrieb Rainer Hurling: >> > Am 10.07.23 um 08:08 schrieb Mark Millard: >> >> On

Re: Problem with the package builds

Am 10.07.23 um 23:26 schrieb Kevin Oberman: On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling > wrote: Am 10.07.23 um 08:15 schrieb Rainer Hurling: > Am 10.07.23 um 08:08 schrieb Mark Millard: >> On Jul 9, 2023, at 22:52, Rainer Hurling mailto:rhur...@gwdg.de>

Re: Problem with the package builds

Jan Beich wrote on 2023/07/11 12:51: > Even with pkg-1.20.2 many running jobs are stuck with *-depends in Status. > > https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=pd6fe15e0ee7a_s1ec7cb1b5d At the time I started writing this email, several qt5-* and kf5-*s

Unmaintained FreeBSD ports which are out of date

Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this po

Re: Problem with the package builds

Kevin Oberman writes: > On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling wrote: > >> Am 10.07.23 um 08:15 schrieb Rainer Hurling: >> > Am 10.07.23 um 08:08 schrieb Mark Millard: >> >> On Jul 9, 2023, at 22:52, Rainer Hurling wrote: >> >> >> >>> Am 10.07.23 um 06:53 schrieb Mark Millard: >>

Re: build of www/chromium stops in node18

bob prohaska writes: > While compiling www/chromium on an 8GB Pi4 poudriere seems to have > trouble compiling www/node. [...] > In file included from > ../deps/v8/src/compiler/backend/instruction-scheduler.cc:5: > In file included from > ../deps/v8/src/compiler/backend/instruction-scheduler.h:1

Re: build of www/chromium stops in node18

On Jul 10, 2023, at 19:04, bob prohaska wrote: > While compiling www/chromium on an 8GB Pi4 poudriere seems to have > trouble compiling www/node. > > The error message is: > >^ > c++ -o > /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_c

build of www/chromium stops in node18

While compiling www/chromium on an 8GB Pi4 poudriere seems to have trouble compiling www/node. The error message is: ^ c++ -o /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/instruction-schedu ler.o .

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

elated notices >>> in a kyua report: >>> >>> # kyua report --verbose >>> --results-file=usr_obj_DESTDIRs_main-CA7-chroot_usr_tests.20230710-064632-752785 >>> 2>&1 | grep "Undefined symbol" | sort -u >>> +ImportError: >>>

Re: Problem with the package builds

Hello. Guido Falsi wrote on 2023/07/10 18:01: > This resonates with something I have observed from time to time on my build > machine. > Especially when using a big ccache (32 GiB or more, is what I can testify > about), but also when building ports with a big number of files like the > teTeX,

Re: Problem with the package builds

On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling wrote: > Am 10.07.23 um 08:15 schrieb Rainer Hurling: > > Am 10.07.23 um 08:08 schrieb Mark Millard: > >> On Jul 9, 2023, at 22:52, Rainer Hurling wrote: > >> > >>> Am 10.07.23 um 06:53 schrieb Mark Millard: > Konstantin Belousov wrote on > >

Re: Problem with the package builds

Am 10.07.23 um 08:15 schrieb Rainer Hurling: Am 10.07.23 um 08:08 schrieb Mark Millard: On Jul 9, 2023, at 22:52, Rainer Hurling wrote: Am 10.07.23 um 06:53 schrieb Mark Millard: Konstantin Belousov wrote on Date: Mon, 10 Jul 2023 01:18:05 UTC : On Sun, Jul 09, 2023 at 05:52:50PM -0700, Ke

Re: Problem with the package builds

On 7/10/23 02:28, Gleb Popov wrote: On Mon, Jul 10, 2023 at 3:53 AM Kevin Oberman wrote: Something looks really messed up on the beefy16 package builder for 13.1amd64. The main culprit is pkg 1.20: https://github.com/freebsd/pkg/issues/2155 https://github.com/freebsd/pkg/issues/2156 Dang,

Re: Problem with the package builds

Tatsuki Makino wrote: No, actually I suspect there is something wrong with the base as well. :) There must be something wrong with the area around the disk IO. It often goes to access as if the cache is not working and the HDD random access is unusually slow. I'm hesitant to move to version 13 s