Re: Build failure for ``no options PTRACE''

2020-10-18 Thread Christos Zoulas
In article <293ee35a-90b6-fe89-42ca-9adfbc9db...@netbsd.org>, Kamil Rytarowski wrote: >-=-=-=-=-=- >-=-=-=-=-=- > >On 18.10.2020 15:00, Paul Goyette wrote: >> >> I'm getting lost inside all this elf stuff  :) > >ptrace is not really pluggable and the maintenance burden to have part >of it

Re: Build failure for ``no options PTRACE''

2020-10-18 Thread Paul Goyette
I've opened PR kern/55731 for this issue. On Sun, 18 Oct 2020, Kamil Rytarowski wrote: On 18.10.2020 15:00, Paul Goyette wrote: I'm getting lost inside all this elf stuff?? :) ptrace is not really pluggable and the maintenance burden to have part of it as loadable modules questions the

Re: Build failure for ``no options PTRACE''

2020-10-18 Thread Kamil Rytarowski
On 18.10.2020 15:00, Paul Goyette wrote: > > I'm getting lost inside all this elf stuff  :) ptrace is not really pluggable and the maintenance burden to have part of it as loadable modules questions the usefulness of this. My request to demodularize it stands. signature.asc Description:

Re: Build failure for ``no options PTRACE''

2020-10-18 Thread Paul Goyette
On Sat, 17 Oct 2020, Paul Goyette wrote: OK, I updated kern/kern_core.c to #include exec_elf.h and made is past the modules. I'll install in the morning and make sure that all combinations of modules from {coredump, exec_elf32, exec_elf64} work. At the very least, they all have to

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
OK, I updated kern/kern_core.c to #include exec_elf.h and made is past the modules. I'll install in the morning and make sure that all combinations of modules from {coredump, exec_elf32, exec_elf64} work. At the very least, they all have to successfully load in any sequence without requiring

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
On Sat, 17 Oct 2020, Christos Zoulas wrote: Just add their declarations in exec_elf.h they have the same signatures as the "unreal" ones :-) Tried that, but now kern_core.c won't compile as part of the coredump module: ... # compile coredump/kern_core.o ... (gcc command line elided) In

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
OK, I got a build failure for modules: # compile coredump/kern_core.o /build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-gcc -O2 -g -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
Oh, ignore this for now. I might have to also rebuild my modules again. On Sat, 17 Oct 2020, Paul Goyette wrote: On Sat, 17 Oct 2020, Paul Goyette wrote: Thanks - I'll give it a try. OK, it builds. But it doesn't work, and least not completely! FWIW, in addition to no options

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
On Sat, 17 Oct 2020, Paul Goyette wrote: Thanks - I'll give it a try. OK, it builds. But it doesn't work, and least not completely! FWIW, in addition to no options COREDUMP no options PTRACE my custom kernel also has no options EXEC_ELF32 no options

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Kamil Rytarowski
On 17.10.2020 18:53, Paul Goyette wrote: > Kamil wrote: > >> This, I propose to do the following: >> >> 1. Remove the modularization of ptrace. This does not affect the compat >> layers that still can and should be in my opinion modular. >> >> 2. Either abandon 'no PTRACE' or make it complete

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
Kamil wrote: This, I propose to do the following: 1. Remove the modularization of ptrace. This does not affect the compat layers that still can and should be in my opinion modular. 2. Either abandon 'no PTRACE' or make it complete ifdefing all the ptrace-related code from the kernel core.

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Kamil Rytarowski
On 17.10.2020 15:32, Christos Zoulas wrote: > In article , > Paul Goyette wrote: >> For a custom kernel build with ``no options PTRACE'' and ``no options >> COREDUMP'' defined, and sources updated on 2020-10-16 at 13:18:24 UTC, >> I get the following linker error: >> >> # link

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Paul Goyette
Thanks - I'll give it a try. On Sat, 17 Oct 2020, Christos Zoulas wrote: In article , Paul Goyette wrote: For a custom kernel build with ``no options PTRACE'' and ``no options COREDUMP'' defined, and sources updated on 2020-10-16 at 13:18:24 UTC, I get the following linker error: #

Re: Build failure for ``no options PTRACE''

2020-10-17 Thread Christos Zoulas
In article , Paul Goyette wrote: >For a custom kernel build with ``no options PTRACE'' and ``no options >COREDUMP'' defined, and sources updated on 2020-10-16 at 13:18:24 UTC, >I get the following linker error: > ># link SPEEDY/netbsd

Build failure for ``no options PTRACE''

2020-10-16 Thread Paul Goyette
For a custom kernel build with ``no options PTRACE'' and ``no options COREDUMP'' defined, and sources updated on 2020-10-16 at 13:18:24 UTC, I get the following linker error: # link SPEEDY/netbsd /build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-ld -Map netbsd.map --cref -T