On 5/24/25 21:47, Mark Millard wrote:
> Dennis Clarke <dclarke_at_blastwave.org> wrote on
> Date: Sat, 24 May 2025 22:46:18 UTC :
>
>> wow ... archive ? Well why not and yes I will give that a whirl.
>>
>> Still doesn't clear up why I can not build from source but that is a
>> whole other matter.
>
> MFC's do not go back through the whole history
I have no idea what "MFC" is supposed to mean.
I guess it is a code change that happened somewhere.
> making source files compatible with updated
> toolchains. Even something like llvm18 can have
> where syntax is allowed corrected before llvm19,
Got it. The compiler is picky and ever increasingly more picky with
each passing year. So stuff from the past that slipped quietly under
the radar is now being stomped on as bad stuff.
>
> In general things are set up to go forward in
> small enough jumps, not to go backwards.
>
So it seems to me that all those branches of stuff named releng/X are
going to be just chewing up bandwidth for some values of X. I guess a
person could go hunt down that thing called "archive" and install a
version of FreeBSD such as 12.2-RELEASE. Then that stuff would be able
to build from source. Maybe. Most likely not worth the effort.
> The MFC of the source correction to 13.* was made
> to 13.3, not to 13.2. See:
>
>
https://cgit.freebsd.org/src/commit/contrib/tzcode/zic.c?h=releng/13.3&id=7ef70d24eee731375fe17a8ef1a30573338d9468
>
Nice to know that the change can be found. Way more detail than I would
ever need. The first thought that I had after the failure to build a
jail was that something much be wrong in 15.0-CURRENT. Turns out that it
was something slightly wrong in the code for 13.2-RELEASE.
I was able to create the 13.2 jail neatly named 132amd64 and then I took
a look at the branch names in ports. Since the 13.2-RELEASE seems to be
supported somewhere in mid 2023 it made sense to use package names from
a branch such as 2023Q3. That works neatly and I get 481 packages built
with zero failures.
pluto# uname -a
FreeBSD pluto 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 GENERIC amd64
pluto# pkg query %n\ %v\ %o\ %R\ %a | grep '0$'
bind-tools 9.18.19 dns/bind-tools titan 0
bind918 9.18.19 dns/bind918 titan 0
dmidecode 3.5 sysutils/dmidecode titan 0
groff 1.22.4_4 textproc/groff titan 0
iperf3 3.13 benchmarks/iperf3 titan 0
pkg 1.19.2 ports-mgmt/pkg titan 0
smartmontools 7.3_1 sysutils/smartmontools titan 0
tmux 3.3a_1 sysutils/tmux titan 0
pluto#
Pretty nifty.
The real trick is to upgrade the whole machine but I keep waving my
hands at that. I figure 14.3-RELEASE is just days away:
https://www.freebsd.org/releases/14.3R/schedule/
So the full upgrade can happen somewhere in June if I can figure out how
to deal with the massive zpool this thing is dragging around. There is
at least sixteen years of backups of old Sun Solaris stuff as well as a
ton of other projects. I am not yet ready to toss that into /dev/null.
Thank you again for the great help. I could not get some things done at
all if it were not for this mail list.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
