Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
some change in the kernel has made ntpd stop working on my arm64 test
box. (My amd64 test box is a couple of days behind so I'm not sure if
it's arm-specific).
What I've identified so far:
* The problem is in the kernel, not userl
Peter Jeremy write on
Date: Sun, 23 Apr 2023 11:47:01 UTC :
> Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
I see the problem at main-n262371-72ef722b2a34-dirty (aarch64),
in the middle of your range. So in the smaller range is:
Thu, 20 Apr 2023
. . .
• git: 607bc91d90
On 23 Apr 2023, at 6:47, Peter Jeremy wrote:
> Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
> some change in the kernel has made ntpd stop working on my arm64 test
> box. (My amd64 test box is a couple of days behind so I'm not sure if
> it's arm-specific).
>
> What I've ide
On Apr 23, 2023, at 05:29, Mark Millard wrote:
> Peter Jeremy write on
> Date: Sun, 23 Apr 2023 11:47:01 UTC :
>
>> Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
>
> I see the problem at main-n262371-72ef722b2a34-dirty (aarch64),
> in the middle of your range. So in the sm
On 4/23/23 07:47, Peter Jeremy wrote:
Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
some change in the kernel has made ntpd stop working on my arm64 test
box. (My amd64 test box is a couple of days behind so I'm not sure if
it's arm-specific).
[ .. snip .. ]
While I can'
On Sun, Apr 23, 2023 at 07:34:45AM -0500, Mike Karels wrote:
> On 23 Apr 2023, at 6:47, Peter Jeremy wrote:
>
> > Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
> > some change in the kernel has made ntpd stop working on my arm64 test
> > box. (My amd64 test box is a couple of
On Sun, Apr 23, 2023 at 09:47:01PM +1000, Peter Jeremy wrote:
> Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
> some change in the kernel has made ntpd stop working on my arm64 test
> box. (My amd64 test box is a couple of days behind so I'm not sure if
> it's arm-specific).
>
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"
Does this mean that a /lib/libc.so.8 is pend
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 sym
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: /usr/lo
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 "__libc
[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 1400081
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 tar
13 matches
Mail list logo
