Re: ./build.sh -O ../obj tools producing error

[Michael Cheponis <michael.cheponis%gmail.com@localhost>]

The <stuff> looked pretty generic, mostly just turning .c into .o files

Yes, I apparently have an old libc (thanks for catching this):

lrwxr-xr-x  1 root  wheel         14 Jul 22  2020 /lib/libc.so@ -> libc.so.12.217
lrwxr-xr-x  1 root  wheel         14 Jul 22  2020 /lib/libc.so.12@ -> libc.so.12.217
-r--r--r--  1 root  wheel  2,256,536 Jul 22  2020 /lib/libc.so.12.217

But I think I'm in a catch-22:  How do I build a new up-to-date libc, if the 'tools' won't build (because they need the new libc)?

On Thu, Jul 27, 2023 at 2:01 PM Valery Ushakov <uwe%stderr.spb.ru@localhost> wrote:

On Thu, Jul 27, 2023 at 10:22:20 -0700, Michael Cheponis wrote:

> $ nm -D /lib/libc.so | grep sigaction
>
>
>  ~/July.2023
> 0000000000099c18 T __libc_sigaction14
> 0000000000099c18 W __sigaction14
> 0000000000099dd4 T __sigaction_sigtramp
> 0000000000084dbc T sigaction
[...]
> It is *missing* __sigaction_siginfo          (!)
>
> I have no idea what gives (how that happened), nor how to fix it.

An old libc?  You seems to have new includes that rename sigaction,
but an old libc that doesn't have the target symbol.

lib/libc/sys/Makefile.inc:

date: 2021-11-01 08:53:45 +0300;  author: thorpej;  state: Exp;  lines: +3 -3;  commitid: yBY9X0v5b6DYo3fD;
Version the sigaction(2) libc wrapper.  The new version uses the "siginfo"
trampoline exclusively, thus relegating "sigcontext"-style handlers (which
have not been documented for many years now) to the dustbin of the compat
library.


-uwe