Updating src tree:
P src/UPDATING
P src/bin/csh/time.c
P src/crypto/external/bsd/netpgp/dist/src/netpgpverify/libverify.c
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/public-domain/tz/dist/Makefile
P src/external/public-domain/tz/dist/NEWS
U
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
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
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
On Friday 16 Oct 2020, at 11:05, Anthony Mallet wrote:
> For some databases (especially those in the firefox profile, but not
> only), inserting a row in some tables (not all) from a NFS client does
> not update the file on the server.
I made some progress on this, and could apparently fix
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
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
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
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.
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
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:
#
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
12 matches
Mail list logo
