Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Feb 2025 07:23:08 +0300
From:      Gleb Popov <arrowd@freebsd.org>
To:        Yusuf Yaman <nxjoseph@protonmail.com>
Cc:        FreeBSD Ports ML <freebsd-ports@freebsd.org>
Subject:   Re: About my ports that fail build on pkg builder 134i386
Message-ID:  <CALH631kbVVs4siuCgWmN-_bJc3gR81pEYLNu8WNtEO6u0VCWCA@mail.gmail.com>
In-Reply-To: <0209d1aa-6f1c-4da7-bf73-49bbeb246b53@protonmail.com>
References:  <0209d1aa-6f1c-4da7-bf73-49bbeb246b53@protonmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 17, 2025 at 12:24=E2=80=AFAM Yusuf Yaman <nxjoseph@protonmail.c=
om> wrote:
>
> Hi,
>
> I have currently 3 ports that fail while building on pkg builder 134i386
> however in my Poudriere jail (134-p3-i386) they all build fine and I
> think I can only guess the fix because on my side they are fine. How can
> I be sure if I fixed my ports or not? I am new in fixing failed build
> ports on pkg builders. Thanks in advance.
>
> These are logs of the ports that fail to build on pkg builder 134i386.
>
> https://pkg-status.freebsd.org/beefy15/data/134i386-default/978f321fff54/=
logs/cairo-dock-3.5.1_1.log
> https://pkg-status.freebsd.org/beefy15/data/134i386-default/7ae51b97b46d/=
logs/libinfinity-0.7.2.log
> https://pkg-status.freebsd.org/beefy15/data/134i386-default/9e15f4b0eb47/=
logs/dissent-0.0.32.log

There is something really strange going on there, because in all 3
cases it is the compiler that crashes. It is not your ports fault.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631kbVVs4siuCgWmN-_bJc3gR81pEYLNu8WNtEO6u0VCWCA>