Gleb Popov wrote on
Date: Sun, 13 Aug 2023 20:30:48 UTC :
> Some of the ports I'm using are failing to build after OpenSSL 3
> import due to the following problem. OpenSSL headers that are shipped
> in base contain declarations of various deprecated functions for which
> libcrypto.so doesn't
On Mon, 14 Aug 2023 11:55:04 +1000
"Greg 'groggy' Lehey" wrote:
> I've spent the last couple of days chasing random hangs on my -CURRENT
> box. It seems to be related to the Ethernet driver (em). I've been
> trying without much success to chase it down, and I'd be grateful.
> The box is
On Sun, Aug 13, 2023 at 6:55 PM Greg 'groggy' Lehey wrote:
>
> I've spent the last couple of days chasing random hangs on my -CURRENT
> box. It seems to be related to the Ethernet driver (em). I've been
> trying without much success to chase it down, and I'd be grateful.
> The box is headless,
On Sun, 13 Aug 2023 23:16:47 +
Alastair Hogge wrote:
> On 2023-08-13 23:22, Matthias Apitz wrote:
> > fwd to freebsd-current@ because I don't know if kde@ is read by someone;
> >
> > matthias
> >
> > - Forwarded message from bugzilla-nore...@freebsd.org -
> >
> > Date: Sun, 13
I've spent the last couple of days chasing random hangs on my -CURRENT
box. It seems to be related to the Ethernet driver (em). I've been
trying without much success to chase it down, and I'd be grateful.
The box is headless, and all communication is via the net, which
doesn't make it any
On Aug 3, 2023, at 00:19, Mark Millard wrote:
> This is after the patch (leading whitespace might
> not have been preserved in what you see):
>
> # git -C /usr/main-src/ diff sys/dev/md/
> diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
> index a719dccb1955..365296ec4276 100644
> ---
On 2023-08-13 23:22, Matthias Apitz wrote:
> fwd to freebsd-current@ because I don't know if kde@ is read by someone;
>
> matthias
>
> - Forwarded message from bugzilla-nore...@freebsd.org -
>
> Date: Sun, 13 Aug 2023 15:08:04 +
> From: bugzilla-nore...@freebsd.org
> To:
On Aug 13, 2023, at 15:33, bob prohaska wrote:
> On Sun, Aug 13, 2023 at 12:45:12PM -0700, Mark Millard wrote:
>>
>> Wow. I'm going to suggest doing a clone (to a temporary
>> place) on one or more different types of system, such
>> as aarch64 or amd64. If, say, aarch64 works but armv7
>> does
On Sun, Aug 13, 2023 at 12:45:12PM -0700, Mark Millard wrote:
>
> Wow. I'm going to suggest doing a clone (to a temporary
> place) on one or more different types of system, such
> as aarch64 or amd64. If, say, aarch64 works but armv7
> does not, then the corruption may well be in some armv7
>
On Aug 13, 2023, at 14:37, Juraj Lutter wrote:
> On 13 Aug 2023, at 23:13, Mark Millard wrote:
>>
>> On Aug 13, 2023, at 14:01, Mark Millard wrote:
>>
>>> On Aug 13, 2023, at 13:19, Juraj Lutter wrote:
>>>
> On 13 Aug 2023, at 21:13, Mark Millard wrote:
>
> But the offical CI
> On 13 Aug 2023, at 23:13, Mark Millard wrote:
>
> On Aug 13, 2023, at 14:01, Mark Millard wrote:
>
>> On Aug 13, 2023, at 13:19, Juraj Lutter wrote:
>>
On 13 Aug 2023, at 21:13, Mark Millard wrote:
But the offical CI builds on amd64 do not have the problem.
On Aug 13, 2023, at 14:01, Mark Millard wrote:
> On Aug 13, 2023, at 13:19, Juraj Lutter wrote:
>
>>> On 13 Aug 2023, at 21:13, Mark Millard wrote:
>>>
>>> But the offical CI builds on amd64 do not have the problem.
>>>
>>> We still have not found what is different about your context from
On Aug 13, 2023, at 13:19, Juraj Lutter wrote:
>> On 13 Aug 2023, at 21:13, Mark Millard wrote:
>>
>> But the offical CI builds on amd64 do not have the problem.
>>
>> We still have not found what is different about your context from the
>> standard context used for CI builds and snapshot
On 13 Aug 2023, at 15:19, Juraj Lutter wrote:
>> On 13 Aug 2023, at 21:13, Mark Millard wrote:
>>
>> But the offical CI builds on amd64 do not have the problem.
>>
>> We still have not found what is different about your context from the
>> standard context used for CI builds and snapshot builds,
Some of the ports I'm using are failing to build after OpenSSL 3
import due to the following problem. OpenSSL headers that are shipped
in base contain declarations of various deprecated functions for which
libcrypto.so doesn't contain definitions. Some of them are
RSA_generate_key and ERR_*
> On 13 Aug 2023, at 21:13, Mark Millard wrote:
>
> But the offical CI builds on amd64 do not have the problem.
>
> We still have not found what is different about your context from the
> standard context used for CI builds and snapshot builds, all of which
> have worked find building on
On Aug 13, 2023, at 12:26, bob prohaska wrote:
> On Sat, Aug 12, 2023 at 08:45:54PM -0700, Mark Millard wrote:
>>
>> You might need to use the ssh alternative if your
>> context allows it:
>>
>> ssh://anon...@git.freebsd.org/src.git
>>
>> There was a time when git fetch proved unreliable
>>
On Aug 13, 2023, at 12:07, Jessica Clarke wrote:
> On Sun, Aug 13, 2023 at 02:23:54AM -0700, Mark Millard wrote:
>> On Aug 13, 2023, at 01:06, Mina Galić wrote:
>>
>>> from IRC, i have learned this is working as designed:
>>> etcupdate without -B does a build.
>>
>> My interpretation of what
On Sat, Aug 12, 2023 at 08:45:54PM -0700, Mark Millard wrote:
>
> You might need to use the ssh alternative if your
> context allows it:
>
> ssh://anon...@git.freebsd.org/src.git
>
> There was a time when git fetch proved unreliable
> in my context and I got around it via ssh use. It
> also
Juraj Lutter wrote on
Date: Sun, 13 Aug 2023 17:49:16 UTC :
> > On 13 Aug 2023, at 17:22, Juraj Lutter wrote:
> >
> >
> >
> >> On 13 Aug 2023, at 17:17, Mike Karels wrote:
> >>
> >>
> >> On 13 Aug 2023, at 10:00, Juraj Lutter wrote:
> >>
> On 13 Aug 2023, at 16:55, Mike Karels
On Sun, Aug 13, 2023 at 02:23:54AM -0700, Mark Millard wrote:
> On Aug 13, 2023, at 01:06, Mina Galić wrote:
>
> > from IRC, i have learned this is working as designed:
> > etcupdate without -B does a build.
>
> My interpretation of what "build" referred to for
> etcupate was way off. I've
Ship it!
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
> On Aug 13, 2023, at 2:39 PM, George Mitchell wrote:
>
> On 8/11/23 23:15, Glen Barber wrote:
>> [...]
>> It was discovered that due to human error (my own) the arm64 are, as
>> Colin put it very politely, are "lacking
> On 13 Aug 2023, at 19:50, Mark Millard wrote:
>
> So it still looks to me like a build infrastructure problem:
> it did not do what it said it would do. I've no clue about
> why at this point.
>
> I'll note that clang and lld do not get per-target builds like
> gcc does. "bootstrap" means
On Aug 13, 2023, at 10:10, Juraj Lutter wrote:
> Mark,
>
>> On 13 Aug 2023, at 19:04, Mark Millard wrote:
>>
>> No arm64.aarch64/tmp/ SYSTEM_COMPILER or SYSTEM_LINKER bootstrap
>> compiler/linker were built.
>>
>> From what I can tell, this leads to:
>>
>> cc -march=armv7 -m32 -target
> On 13 Aug 2023, at 17:22, Juraj Lutter wrote:
>
>
>
>> On 13 Aug 2023, at 17:17, Mike Karels wrote:
>>
>>
>> On 13 Aug 2023, at 10:00, Juraj Lutter wrote:
>>
On 13 Aug 2023, at 16:55, Mike Karels wrote:
lib32 is not built until stage 4.3.1, after build and cross
Mark,
> On 13 Aug 2023, at 19:04, Mark Millard wrote:
>
> No arm64.aarch64/tmp/ SYSTEM_COMPILER or SYSTEM_LINKER bootstrap
> compiler/linker were built.
>
> From what I can tell, this leads to:
>
> cc -march=armv7 -m32 -target armv7-unknown-freebsd14.0-gnueabihf
> -DCOMPAT_LIBCOMPAT=\"32\"
Juraj Lutter wrote on
Date: Sun, 13 Aug 2023 12:42:45 UTC :
> > On 13 Aug 2023, at 00:17, Mike Karels wrote:
> >
> > On 12 Aug 2023, at 15:32, Juraj Lutter wrote:
> >
> > Did the buildworld start out by building a cross-compiler?
> >
> > Have you tried without meta mode? With a clean objdir,
On Sun, 13 Aug 2023 17:22:19 +0200
Matthias Apitz wrote:
> fwd to freebsd-current@ because I don't know if kde@ is read by someone;
>
> matthias
>
> - Forwarded message from bugzilla-nore...@freebsd.org -
>
> Date: Sun, 13 Aug 2023 15:08:04 +
> From:
> On 13 Aug 2023, at 17:17, Mike Karels wrote:
>
>
> On 13 Aug 2023, at 10:00, Juraj Lutter wrote:
>
>>> On 13 Aug 2023, at 16:55, Mike Karels wrote:
>>>
>>>
>>> lib32 is not built until stage 4.3.1, after build and cross tools. I tested
>>> a build just now on amd64 with empty
fwd to freebsd-current@ because I don't know if kde@ is read by someone;
matthias
- Forwarded message from bugzilla-nore...@freebsd.org -
Date: Sun, 13 Aug 2023 15:08:04 +
From: bugzilla-nore...@freebsd.org
To: k...@freebsd.org
Subject: [Bug 270041] www/qt5-webengine:
On 13 Aug 2023, at 10:00, Juraj Lutter wrote:
>> On 13 Aug 2023, at 16:55, Mike Karels wrote:
>>
>>
>> lib32 is not built until stage 4.3.1, after build and cross tools. I tested
>> a build just now on amd64 with empty /usr/obj, and it worked (make -j$NCU
>> buildworld TARGET=arm64
> On 13 Aug 2023, at 16:55, Mike Karels wrote:
>
>
> lib32 is not built until stage 4.3.1, after build and cross tools. I tested
> a build just now on amd64 with empty /usr/obj, and it worked (make -j$NCU
> buildworld TARGET=arm64 TARGET_ARCH=aarch64). However, the host was
> approximately
On Sun, Aug 13, 2023, 8:55 AM Mike Karels wrote:
> On 13 Aug 2023, at 9:25, Juraj Lutter wrote:
>
> >> On 13 Aug 2023, at 14:42, Juraj Lutter wrote:
> >>
> >> Hi,
> >>
> >>> On 13 Aug 2023, at 00:17, Mike Karels wrote:
> >>>
> >>> On 12 Aug 2023, at 15:32, Juraj Lutter wrote:
> >>>
> >>> Did
On 13 Aug 2023, at 9:25, Juraj Lutter wrote:
>> On 13 Aug 2023, at 14:42, Juraj Lutter wrote:
>>
>> Hi,
>>
>>> On 13 Aug 2023, at 00:17, Mike Karels wrote:
>>>
>>> On 12 Aug 2023, at 15:32, Juraj Lutter wrote:
>>>
>>> Did the buildworld start out by building a cross-compiler?
>>>
>>> Have you
> On 13 Aug 2023, at 14:42, Juraj Lutter wrote:
>
> Hi,
>
>> On 13 Aug 2023, at 00:17, Mike Karels wrote:
>>
>> On 12 Aug 2023, at 15:32, Juraj Lutter wrote:
>>
>> Did the buildworld start out by building a cross-compiler?
>>
>> Have you tried without meta mode? With a clean objdir, I
Hi,
> On 13 Aug 2023, at 00:17, Mike Karels wrote:
>
> On 12 Aug 2023, at 15:32, Juraj Lutter wrote:
>
> Did the buildworld start out by building a cross-compiler?
>
> Have you tried without meta mode? With a clean objdir, I don't see how
> it would matter, but I'm not sure I've tried it.
>
On Aug 13, 2023, at 01:06, Mina Galić wrote:
> from IRC, i have learned this is working as designed:
> etcupdate without -B does a build.
My interpretation of what "build" referred to for
etcupate was way off. I've added the -B's that I
was not using before.
Thanks for the note!
> Also,
from IRC, i have learned this is working as designed:
etcupdate without -B does a build.
Also, jrtc27 recently made it so bootstrapping, because otherwise
BUILD_WITH_STRICT_TMPPATH doesn't work:
https://github.com/freebsd/freebsd-src/commit/d81da4c98328d4ee3fe4c0a85f6874a3c69a1afd
Kind
I'd noticed that the etcupdate part of my build procedure has been taking
much time. So I looked with a ps -axldww while it was going on. An
example was:
`-- /bin/sh /usr/sbin/etcupdate -D/usr/obj/DESTDIRs/main-CA7-chroot -s
/usr/main-src -M TARGET_ARCH=armv7
`-- make TARGET_ARCH=armv7
39 matches
Mail list logo
