Gleb Smirnoff wrote on
Date: Sat, 24 Feb 2024 04:32:52 UTC :
> More seriously speaking, I
> actually hope that in some future snapshots.FreeBSD.org will start using these
> points for snapshot generation.
How about also the likes of:
https://pkg.freebsd.org/FreeBSD:15:aarch64/stabweek/
for
Hi FreeBSD/main users,
the February 2024 stabilization week started with 03cc3489a02d that was tagged
as main-stabweek-2024-Feb. At the moment of the tag creation we already knew
about several regression caused by libc/libsys split.
In the stabilization branch stabweek-2024-Feb we accumulated
Hi FreeBSD CURRENT users,
back in November I came up with a proposal of providing some stabilization
cadence to development of the main branch, also known as FreeBSD CURRENT. Here
is a video with the initial proposal and following discussion at VendorBSD
Conference (18 minutes):
On Fri, Feb 23, 2024 at 10:21:12AM -0800, Michael Dexter wrote:
> On 2/23/24 9:13 AM, Brooks Davis wrote:
> > Things are in a somewhat messy state. CASPER and CAPSICUM were moved to
> > a new __REQUIRED_OPTIONS list, but the various bits still exist and
> > there's even one use of MK_CASPER=no in
On 2/23/24 9:13 AM, Brooks Davis wrote:
Things are in a somewhat messy state. CASPER and CAPSICUM were moved to
a new __REQUIRED_OPTIONS list, but the various bits still exist and
there's even one use of MK_CASPER=no in Makefile.inc1. The commit
message (c24c117b9644) suggests that the intent
On 05-02-24 17:02, Brooks Davis wrote:
Could you do a quick test with an exe linked to libsys but not libc running
under Valgrind memcheck, please?
Could you suggest a more concrete example?
This little example seems to be OK
void _start(void)
{
_exit(0);
}
However I do see quite a
On Thu, Feb 22, 2024 at 07:49:08PM -0800, Michael Dexter wrote:
> All,
>
> The WITHOUT_CASPER build option was deprecated in main and 14-stable branches
> but is still showing up and will trip up the build option survey:
>
> sh src/tools/tools/build_option_survey/listallopts.sh | grep CASPER
>
