Re: git for armv7

On May 3, 2023, at 10:29, Mark Millard <marklmi@yahoo.com> wrote:

> bob prohaska <fbsd_at_www.zefox.net> wrote on
> Date: Wed, 03 May 2023 15:46:02 UTC :
> 
>> I have an armv7 Pi2 running -current and have somehow deleted my
>> executable of git. The existing port fails with the libunwind breakage,
>> 
>> I expected that re-enabling the master pkg site would allow me to re-fetch
>> a runnable copy of git, but nothing is found for armv7. What the best way out
>> of this pickle? 
> 
> main [so: 14] can run ports that are built for 13.* .

See note below about that this may have been wrong
for the context.

> So pkg can be pointed at a 13.1-RELEASE quarterly
> instead of latest and forced to get materials from
> the quarterly, such as installing git from the
> quarterly.
> 
> There is some chance that you might have to use
> pkg for some of the quarterly activity via the
> likes of:
> 
> env ABI=FreeBSD:13:aarch64 pkg . . .
> 
> 
> It is still going to be a while before a armv7 git
> shows up based on the fixed libunwind vintage. The
> active build of main's latest, when I looked, still
> predated the libunwind update for when it started.
> The fix availability for main waits on the next
> build of main's latest.

There is some possibility that git will depend on an
other things that would need to also come from
quarterly as well. If so, the process is messier to
get the full set in place.

I've run main [so: 14] with all the ports being from
13.1-RELELASE main in the past. But I've never had
the mix of ports from main and from 13.1-RELEASE's
latest. My claims above may have been inappropriate
to this context.

===
Mark Millard
marklmi at yahoo.com