Re: Getting /usr/src to match specific git hash?

On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote: > From: Steve Kargl > Subject: Getting /usr/src to match specific git hash? > Date: Sat, 23 Jan 2021 19:58:52 -0800 > > > Suppose one has an empty /usr/src. > > > > Suppose further that one had to re-install a 32-bit > >

Re: Getting /usr/src to match specific git hash?

On 24 Jan, Yasuhiro Kimura wrote: > From: Steve Kargl > Subject: Getting /usr/src to match specific git hash? > Date: Sat, 23 Jan 2021 19:58:52 -0800 > >> Suppose one has an empty /usr/src. >> >> Suppose further that one had to re-install a 32-bit >> i386-*-freebsd with the 24 Dec 2020 image

Re: Getting /usr/src to match specific git hash?

From: Steve Kargl Subject: Getting /usr/src to match specific git hash? Date: Sat, 23 Jan 2021 19:58:52 -0800 > Suppose one has an empty /usr/src. > > Suppose further that one had to re-install a 32-bit > i386-*-freebsd with the 24 Dec 2020 image available > from freebsd.org. > > uname -a for

Getting /usr/src to match specific git hash?

Suppose one has an empty /usr/src. Suppose further that one had to re-install a 32-bit i386-*-freebsd with the 24 Dec 2020 image available from freebsd.org. uname -a for the booted kernel shows % uname -a FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \ 3cc0c0d66a0-c255241(main)-dirty: Thu

13-alpha2 libncurses removal breaks ports build

Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING about how one should handle the removal of libncurses.so.9 from base. Source UPDATING only says:ncurses installation has been modified to only keep the widechar     enabled version.  Incremental build is broken for

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote: > So has anyone tracking stable/12 and ports successfully completed the > git checkout stable/13; make buildworld; make installworld; mergemaster > drill? I see I can checkout stable/13. > > Do make.conf | src.conf | GENERIC have

Re: Beta Git repo for ports

On Sat, Jan 23, 2021, 7:09 PM Philip Paeps wrote: > On 2021-01-22 14:24:47 (+0800), Graham Perrin wrote: > > Via > > < > https://www.freebsd.org/news/status/report-2020-10-2020-12.html#Git-Migration-Working-Group> > > > : > > > > > > > > Please: where to

Re: Beta Git repo for ports

On 2021-01-22 14:24:47 (+0800), Graham Perrin wrote: Via : Please: where to file enhancement requests (or bugs) for development of this cgit service for ports?

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 07:52:57PM -0600, Donald Willinger wrote: > Look for 14-current. There is no more 13. as I understand it. > head is 14. stable/13 and stable/12 also exist: FreeBSD freebeast.catwhisker.org 12.2-STABLE FreeBSD 12.2-STABLE #1144 stable/12-c243280-g4493b69d4aa: Sat

Re: Which branch in git is 13.0-current?

Look for 14-current. There is no more 13. as I understand it. On Sat, Jan 23, 2021 at 7:51 PM David Wolfskill wrote: > On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote: > > ... > > > That is correct, 13-stable has been branched from 13-current which has > now > > > been

Re: Which branch in git is 13.0-current?

On Sat, Jan 23, 2021 at 06:34:58PM -0700, Russell L. Carter wrote: > ... > > That is correct, 13-stable has been branched from 13-current which has now > > been bumped to 14-current. > > Because it's a major version change going from 13 to 14, pkg is a bit > > agitated regarding the ABI. > > So

Re: Which branch in git is 13.0-current?

On 1/23/21 10:22 AM, driesm.michi...@gmail.com wrote: -Original Message- From: owner-freebsd-curr...@freebsd.org On Behalf Of Malcolm Matalka Sent: Saturday, 23 January 2021 17:43 To: FreeBSD Current Subject: Which branch in git is 13.0-current? I upgraded my src checkout to git,

Re: RTC on ROCKPRO64

On 2021-01-22 23:16:29 (+0800), Henri Hennebert wrote: I have tested https://reviews.freebsd.org/D22692 on my ROCKPRO64 with a battery and it works. (After correcting the typo at line 516 of rk805.c) Is it possible to merge it for 13.0-RELEASE ? It looks like that revision needs some

Re: FreeBSD 13.0 Build Option Sweep (13.0-ALPHA2 Update)

Hello all, I have re-run every option that failed under 13.0-ALPHA1 build under 12.2, on 13.0-ALPHA2 under 13.0-ALPHA2. HUGE thanks to everyone who has helped resolve failing build options! I have linked a list of annotated remaining failures plus an archive of the full build here:

Re: 13-alpha2 libncurses removal breaks ports build

On Sat, Jan 23, 2021 at 10:40:57PM +, Kostya Berger wrote: > Hi everyone,I don't seem to find any mentioning in the /usr/ports/UPDATING > about how one should handle the removal of libncurses.so.9 from base. > Source UPDATING only says:ncurses installation has been modified to only keep >

RE: Which branch in git is 13.0-current?

> > Does that mean CURRENT is now 14.0? I must have missed the > > announcement. > That is correct, 13-stable has been branched from 13-current which has now > been bumped to 14-current. > Because it's a major version change going from 13 to 14, pkg is a bit > agitated regarding the ABI. > > >

RE: Which branch in git is 13.0-current?

> >> -Original Message- > >> From: owner-freebsd-curr...@freebsd.org >> curr...@freebsd.org> On Behalf Of Malcolm Matalka > >> Sent: Saturday, 23 January 2021 17:43 > >> To: FreeBSD Current > >> Subject: Which branch in git is 13.0-current? > >> > >> I upgraded my src checkout to git,

Re: Which branch in git is 13.0-current?

From: Malcolm Matalka Subject: Re: Which branch in git is 13.0-current? Date: Sat, 23 Jan 2021 18:16:21 +0100 >> Build pkg from ports or wait a bit till the clusters have caught up building >> the packages with the base version change. > > Does that mean CURRENT is now 14.0? I must have missed

Re: Which branch in git is 13.0-current?

driesm.michi...@gmail.com writes: >> -Original Message- >> From: owner-freebsd-curr...@freebsd.org > curr...@freebsd.org> On Behalf Of Malcolm Matalka >> Sent: Saturday, 23 January 2021 17:43 >> To: FreeBSD Current >> Subject: Which branch in git is 13.0-current? >> >> I upgraded my

RE: Which branch in git is 13.0-current?

> -Original Message- > From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of Malcolm Matalka > Sent: Saturday, 23 January 2021 17:43 > To: FreeBSD Current > Subject: Which branch in git is 13.0-current? > > I upgraded my src checkout to git, and looks like I'm on

Re: Which branch in git is 13.0-current?

Stable/13 On Sat, Jan 23, 2021, 13:43 Malcolm Matalka wrote: > I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? > > > FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 > main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 >

Which branch in git is 13.0-current?

I upgraded my src checkout to git, and looks like I'm on 14.0-CURRENT? FreeBSD bsdell 14.0-CURRENT FreeBSD 14.0-CURRENT #33 main-c256217-g6c789c55c4ba: Sat Jan 23 16:08:16 CET 2021 root@bsdell:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I am in the main branch, which I got by following the

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

Ronald Klop wrote: >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote: > >> Hi freebsd-current@, >> >> I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while >> back. >> >> With 13.0-RELEASE around the corner, I'm thinking about upgrading my >> home server, well if I can

Re: Can In-Kernel TLS (kTLS) work with any OpenSSL Application?

On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote: Hi freebsd-current@, I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while back. With 13.0-RELEASE around the corner, I'm thinking about upgrading my home server, well if I can accelerate any SSL application. I'm

Re: elfctl is broken

On Fri, Jan 22, 2021 at 05:13:16PM -0800, Steve Kargl wrote: > ===> usr.bin/elfctl (all) > cc -target i386-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/i386.i386/tmp > -B/usr/obj/usr/src/i386.i386/tmp/usr/bin -O2 -pipe -fno-common > -I/usr/src/contrib/elftoolchain/li belftc >