On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
Dimitry Andric writes:
Probably best to create a bugzilla ticket, but as I said before, I
cannot reproduce this.
I can. My builder is running 15 and sees segfaults while building
packages for 14 and 15 but not for 13.
Interesting. Luckily every
On Nov 25, 2024, at 12:41, Guido Falsi wrote:
> On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
>> Dimitry Andric writes:
>>> Probably best to create a bugzilla ticket, but as I said before, I
>>> cannot reproduce this.
>> I can. My builder is running 15 and sees segfaults while building
>> packa
Mark Millard writes:
> Guido Falsi writes:
>> On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
>>> Dimitry Andric writes:
Probably best to create a bugzilla ticket, but as I said before, I
cannot reproduce this.
>>> I can. My builder is running 15 and sees segfaults while building
>>> pa
Hello.
(I don't subscribe to the current mailing list, so I don't send it there.)
If changing the CPUTYPE changes the occurrence of the problem, is there
-Wl,--as-needed involved?
Not so long ago, Firefox used libraries loaded by other binaries, but that
stopped working.
As an example, recently
On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
Mark Millard writes:
Guido Falsi writes:
On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
Dimitry Andric writes:
Probably best to create a bugzilla ticket, but as I said before, I
cannot reproduce this.
I can. My builder is running 15 and sees s
On Nov 25, 2024, at 13:27, Guido Falsi wrote:
> On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
>> Mark Millard writes:
>>> Guido Falsi writes:
On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
> Dimitry Andric writes:
>> Probably best to create a bugzilla ticket, but as I said before,
On 25 Nov 2024, at 23:12, Mark Millard wrote:
>
> On Nov 25, 2024, at 13:27, Guido Falsi wrote:
>
>> On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
>>> Mark Millard writes:
Guido Falsi writes:
> On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
>> Dimitry Andric writes:
>>> Proba
Dimitry Andric writes:
> Probably best to create a bugzilla ticket, but as I said before, I
> cannot reproduce this.
I can. My builder is running 15 and sees segfaults while building
packages for 14 and 15 but not for 13.
% uname -a
FreeBSD pkg.des.dev 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-
On 26/11/24 03:05, Mark Millard wrote:
Top posting going in a different direction that
established a way to control the behavior in my
context . . .
I changed USE_TMPFS=all to USE_TMPFS=no :
USE_TMPFS=all gets the failure
vs.
USE_TMPFS=no works just fine
So it is a FreeBSD system error associa
On Nov 25, 2024, at 18:05, Mark Millard wrote:
> Top posting going in a different direction that
> established a way to control the behavior in my
> context . . .
For folks new to the discoveries: the context here
is poudriere bulk builds, for USE_TMPFS=all vs.
USE_TMPFS=no . My test context is
On Nov 25, 2024, at 14:23, Guido Falsi wrote:
> On 25/11/24 23:15, Dimitry Andric wrote:
>> On 25 Nov 2024, at 23:12, Mark Millard wrote:
>>>
>>> On Nov 25, 2024, at 13:27, Guido Falsi wrote:
>>>
On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
> Mark Millard writes:
>> Guido Falsi
From: Dimitry Andric
Subject: Re: port binary dumping core on recent head in poudriere
Date: Mon, 25 Nov 2024 23:15:20 +0100
> On 25 Nov 2024, at 23:12, Mark Millard wrote:
>>
>> On Nov 25, 2024, at 13:27, Guido Falsi wrote:
>>
>>> On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
Mark Milla
On Nov 25, 2024, at 15:21, Mark Millard wrote:
> On Nov 25, 2024, at 14:23, Guido Falsi wrote:
>
>> On 25/11/24 23:15, Dimitry Andric wrote:
>>> On 25 Nov 2024, at 23:12, Mark Millard wrote:
On Nov 25, 2024, at 13:27, Guido Falsi wrote:
> On 25/11/24 22:18, Dag-Erling Smø
On 25/11/24 23:15, Dimitry Andric wrote:
On 25 Nov 2024, at 23:12, Mark Millard wrote:
On Nov 25, 2024, at 13:27, Guido Falsi wrote:
On 25/11/24 22:18, Dag-Erling Smørgrav wrote:
Mark Millard writes:
Guido Falsi writes:
On 25/11/24 09:17, Dag-Erling Smørgrav wrote:
Dimitry Andric wri
Top posting going in a different direction that
established a way to control the behavior in my
context . . .
I changed USE_TMPFS=all to USE_TMPFS=no :
USE_TMPFS=all gets the failure
vs.
USE_TMPFS=no works just fine
So it is a FreeBSD system error associated with
use of tmpfs .
Now back to wha
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
16 matches
Mail list logo
