On Sun, Apr 23, 2023 at 10:22 PM Mark Millard wrote:
> [Warner answered my specific question separately. This is about
> something else.]
>
> On Apr 23, 2023, at 20:57, Warner Losh wrote:
>
> > On Sun, Apr 23, 2023 at 9:40 PM Simon J. Gerraty
> wrote:
> >> Mark Millard wrote:
> >> > I will
Warner Losh wrote:
> > ld-elf.so.1: /usr/local/bin/git: Undefined symbol "__libc_start1@FBSD_1.7"
>
> This is a symptom of trying to run a prog built for target on a host
> which is not the same.
> Your path is messed up then. We always run (a copy of) the host's binaries
I wasn't using the
[Warner answered my specific question separately. This is about
something else.]
On Apr 23, 2023, at 20:57, Warner Losh wrote:
> On Sun, Apr 23, 2023 at 9:40 PM Simon J. Gerraty wrote:
>> Mark Millard wrote:
>> > I will not get into why, but I executed a git built for 1400082
>> > in a
On Sun, Apr 23, 2023 at 9:09 PM Mark Millard wrote:
> I will not get into why, but I executed a git built for 1400082
> in a 1400081 world context and got what was to me a surprise,
> given that /lib/libc.so.7 is part of 13.2-RELEASE :
>
> ld-elf.so.1: /usr/local/bin/git: Undefined symbol
On Sun, Apr 23, 2023 at 9:40 PM Simon J. Gerraty wrote:
> Mark Millard wrote:
> > I will not get into why, but I executed a git built for 1400082
> > in a 1400081 world context and got what was to me a surprise,
> > given that /lib/libc.so.7 is part of 13.2-RELEASE :
> >
> > ld-elf.so.1:
Mark Millard wrote:
> I will not get into why, but I executed a git built for 1400082
> in a 1400081 world context and got what was to me a surprise,
> given that /lib/libc.so.7 is part of 13.2-RELEASE :
>
> ld-elf.so.1: /usr/local/bin/git: Undefined symbol "__libc_start1@FBSD_1.7"
This is a
