Re: git: ebbef4b5f84b - main - devel/boost*: update Boost to 1.81.0 release (+)
Date: Tue, 17 Jan 2023 11:28:59 UTC
On 17/01/23 12:23, Daniel Engberg wrote: > On 2023-01-17 12:17, Dima Panov wrote: >> Moin-moin! >> >> On 17.01.2023 14:01, Guido Falsi wrote: >>> On 17/01/23 09:23, Yasuhiro Kimura wrote: >>>> From: Dima Panov <fluffy@FreeBSD.org> >>>> Subject: git: ebbef4b5f84b - main - devel/boost*: update Boost to >>>> 1.81.0 release (+) >>>> Date: Mon, 16 Jan 2023 19:32:51 GMT >>>> >>>>> The branch main has been updated by fluffy: >>>>> >>>>> URL: >>>>> https://cgit.FreeBSD.org/ports/commit/?id=ebbef4b5f84b7cff911d4714000c2ebbc0f786f7 >>>>> >>>>> commit ebbef4b5f84b7cff911d4714000c2ebbc0f786f7 >>>>> Author: Dima Panov <fluffy@FreeBSD.org> >>>>> AuthorDate: 2023-01-16 19:23:41 +0000 >>>>> Commit: Dima Panov <fluffy@FreeBSD.org> >>>>> CommitDate: 2023-01-16 19:32:06 +0000 >>>>> >>>>> devel/boost*: update Boost to 1.81.0 release (+) >>>>> Changelog: >>>>> https://www.boost.org/users/history/version_1_81_0.html >>>> >>>> With recent 14-CURRENT amd64, build of devel/boost-libs fails as >>>> following. >>>> >>>> https://people.freebsd.org/~yasu/poudriere/data/logs/bulk/curamd64-default/2023-01-17_17h09m39s/logs/boost-libs-1.81.0.log >>>> >>> >>> Hi, >>> >>> I'd like to confirm this on my build machine with very recent head. >>> Same error. >>> >>>> yasu@rolling-vm-freebsd1[1040]% uname -a >>>> FreeBSD rolling-vm-freebsd1.home.utahime.org 14.0-CURRENT FreeBSD >>>> 14.0-CURRENT #0 main-n260055-8bce8d28abe: Sat Jan 14 01:06:42 JST >>>> 2023 >>>> rootz@rolling-vm-freebsd1.home.utahime.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >>>> yasu@rolling-vm-freebsd1[1041]% >>>> >>> >>> I'm at commit 9b7eddfeed465d4062dbad178261b806e97d6b62, from >>> yesterday (2023-01-17) >>> >> >> Build was verified many times :( >> >> No error before commit >> >> https://build.dimapanov.com/data/140amd64-dimaports/2023-01-16_22h55m22s/logs/boost-libs-1.81.0.log >> >> >> FreeBSD 14.0-CURRENT #0 main-n260013-4856aeaaed17: Wed Jan 11 23:07:49 >> MSK 2023 > > Maybe this is related to -CURRENT using 14 while you've 15 set as default? I did not notice this. I think it should be avoided to test things with non default options. The failure is fully reproducible with default options. BTW I'm seeing similar failure in libdispatch (required by telegram desktop) which also happens on the cluster: https://lists.freebsd.org/archives/freebsd-pkg-fallout/2023-January/305864.html Since you're using a non default clang I suspect that's also being caused by default base using clang 14. > > I think Guido is going it a go with either 13 or 15 as we speak > Yes, I'm going to have a go using clang 15, I'll also test forcing it for libdispatch. -- Guido Falsi <madpilot@FreeBSD.org>