Re: Build error

2023-06-24 Thread Christos Zoulas
In article , Paul Goyette wrote: >On Tue, 20 Jun 2023, Paul Goyette wrote: > >> On Tue, 20 Jun 2023, Paul Goyette wrote: >> >>> With sources updated on 2023-06-20 at 17:26:58 UTC and building into >>> a completely empty $DESTDIR I am getting >>> >>> >>> == 2 missing files in DESTDIR

Re: Build error

2023-06-20 Thread Paul Goyette
On Tue, 20 Jun 2023, Paul Goyette wrote: On Tue, 20 Jun 2023, Paul Goyette wrote: With sources updated on 2023-06-20 at 17:26:58 UTC and building into a completely empty $DESTDIR I am getting == 2 missing files in DESTDIR Files in flist but missing from DESTDIR. File wasn't

Re: Build error

2023-06-20 Thread Paul Goyette
On Tue, 20 Jun 2023, Paul Goyette wrote: With sources updated on 2023-06-20 at 17:26:58 UTC and building into a completely empty $DESTDIR I am getting == 2 missing files in DESTDIR Files in flist but missing from DESTDIR. File wasn't installed ?

Re: Build error for HEAD on amd64

2020-07-02 Thread Paul Goyette
Looks like this has already been fixed. On Thu, 2 Jul 2020, Paul Goyette wrote: With sources updated on 2020-07-02 at 14:06:53 UTC, and using build.sh -T /build/netbsd-compat/tools/x86_64/amd64 \ -D /build/netbsd-compat/dest/amd64 \ -O

Re: Build error on amd64 -current

2020-06-27 Thread Jaromír Doleček
Fixed in rev.1.137 of sys/arch/xen/x86/cpu.c Le sam. 27 juin 2020 à 11:42, Jaromír Doleček a écrit : > > I'll fix it. > > Le sam. 27 juin 2020 à 11:39, Andreas Gustafsson a écrit : > > > > Paul Goyette wrote: > > > With up-to-date sources I'm getting > > > > > >

Re: Build error on amd64 -current

2020-06-27 Thread Jaromír Doleček
I'll fix it. Le sam. 27 juin 2020 à 11:39, Andreas Gustafsson a écrit : > > Paul Goyette wrote: > > With up-to-date sources I'm getting > > > > /build/netbsd-compat/src_ro/sys/arch/xen/x86/cpu.c: In function > > 'mp_cpu_start': > > /build/netbsd-compat/src_ro/sys/arch/xen/x86/cpu.c:999:1:

Re: Build error on amd64 -current

2020-06-27 Thread Andreas Gustafsson
Paul Goyette wrote: > With up-to-date sources I'm getting > > /build/netbsd-compat/src_ro/sys/arch/xen/x86/cpu.c: In function > 'mp_cpu_start': > /build/netbsd-compat/src_ro/sys/arch/xen/x86/cpu.c:999:1: error: stack usage > is5408 bytes [-Werror=stack-usage=] > mp_cpu_start(struct cpu_info

Re: Build error on amd64 -current

2020-06-26 Thread Hisashi T Fujinaka
I've been complaining about this since yesterday. I'm trying a clean build now. On Fri, 26 Jun 2020, Paul Goyette wrote: With up-to-date sources I'm getting /build/netbsd-compat/src_ro/sys/arch/xen/x86/cpu.c: In function 'mp_cpu_start':

Re: Build error with MKDEBUG=yes

2020-06-07 Thread Rin Okuyama
On 2020/06/08 9:21, Paul Goyette wrote: With MKDEBUG=yes I get ==  1 missing files in DESTDIR  Files in flist but missing from DESTDIR. File wasn't installed ? -- ./usr/libdata/debug/usr/tests/lib/libprop/t_basic.debug   end of 1

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Martin Husemann
On Sun, May 10, 2020 at 07:52:42PM -, Michael van Elst wrote: > And I'd like to talk to Martin, since 100% of the task is done if > we just add the missing dependency without the option. Lets start with just the dependency and see if everything fits in the next build run. We can add the

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Michael van Elst wrote: p...@whooppee.com (Paul Goyette) writes: Well, 90%+ of the effort has already been expended, so why not? 90%+ is probably the time needed to test optional builds in the future. FWIW, I have just successfully completed my build of my custom

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Michael van Elst
p...@whooppee.com (Paul Goyette) writes: >> Well, 90%+ of the effort has already been expended, so why not? 90%+ is probably the time needed to test optional builds in the future. >FWIW, I have just successfully completed my build of my custom kernel >(and an entire ``build.sh release'') and it

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Paul Goyette wrote: On Sun, 10 May 2020, Michael van Elst wrote: p...@whooppee.com (Paul Goyette) writes: FWIW, here's an additional patch to update the options(4) man page: But is it worth the effort to make 16kB optional ? Well, 90%+ of the effort has already been

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Michael van Elst wrote: p...@whooppee.com (Paul Goyette) writes: FWIW, here's an additional patch to update the options(4) man page: But is it worth the effort to make 16kB optional ? Well, 90%+ of the effort has already been expended, so why not?

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Michael van Elst
p...@whooppee.com (Paul Goyette) writes: >FWIW, here's an additional patch to update the options(4) man page: But is it worth the effort to make 16kB optional ? -- -- Michael van Elst Internet: mlel...@serpens.de "A potential

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Michael van Elst wrote: On Sun, May 10, 2020 at 08:46:30AM -0700, Paul Goyette wrote: Here is a patch that makes encrypted swap (but not rijndael) optional: http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/uvm_swap.diff That looks good to me, too. I guess you should also

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Paul Goyette wrote: Here is a patch that makes encrypted swap (but not rijndael) optional: http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/uvm_swap.diff That looks good to me, too. I guess you should also add VM_SWAPCRYPT option to various kernels (GENERIC*, XEN3*, ...)?

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
Here is a patch that makes encrypted swap (but not rijndael) optional: http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/uvm_swap.diff That looks good to me, too. I guess you should also add VM_SWAPCRYPT option to various kernels (GENERIC*, XEN3*, ...)? Please commit.

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Michael van Elst wrote: On Sun, May 10, 2020 at 07:54:06AM -0700, Paul Goyette wrote: Prior to the encrypted-swap commit, a kernel configured without the ``pseudo-device crypto'' was able to link and run successfully. (Any attempt to use rijndael results in an auto-load

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Michael van Elst
On Sun, May 10, 2020 at 07:54:06AM -0700, Paul Goyette wrote: > Prior to the encrypted-swap commit, a kernel configured without the > ``pseudo-device crypto'' was able to link and run successfully. (Any > attempt to use rijndael results in an auto-load of the crypto module.) Even without

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Taylor R Campbell
> Date: Sun, 10 May 2020 13:44:49 - > From: mlel...@serpens.de (Michael van Elst) > > Here is a patch that makes encrypted swap (but not rijndael) optional: > > http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/uvm_swap.diff > > which might be useful to create small kernels (it's just about

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Paul Goyette
On Sun, 10 May 2020, Michael van Elst wrote: p...@whooppee.com (Paul Goyette) writes: the kernel. Without this, the kernel fails to link, with undefined references to several symbols: rijndael_cipherInit rijndael_blockEncrypt rijndael_blockDecrypt

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Michael van Elst
p...@whooppee.com (Paul Goyette) writes: >the kernel. Without this, the kernel fails to link, with undefined >references to several symbols: > rijndael_cipherInit > rijndael_blockEncrypt > rijndael_blockDecrypt > rijndael_makeKey >Since the two crypto devices are

Re: Build error for port-sparc

2020-03-04 Thread Paul Goyette
OK, this turns out to be a problem only for building with MKPAM=0 If I enable PAM, it builds correctly. On Tue, 3 Mar 2020, Paul Goyette wrote: And with even more recent sources (updated on 2020-03-04 at 02:52:55 UTC), I'm getting an error even earlier in the build: dependall ===>

Re: Build error for port-sparc

2020-03-03 Thread Paul Goyette
And with even more recent sources (updated on 2020-03-04 at 02:52:55 UTC), I'm getting an error even earlier in the build: dependall ===> external/bsd/pam-u2f/bin/pamu2fcfg #create pamu2fcfg/explicit_bzero.d CC=/build/netbsd-compat/tools/x86_64/sparc/bin/sparc--netbsdelf-gcc

Re: Build error

2019-08-25 Thread Paul Goyette
OK, I did another ``cvs up'' and the problem appears to have been fixed! Sorry for the noise. On Sun, 25 Aug 2019, Paul Goyette wrote: With sources updated to just a few minutes ago, I'm getting the following when building on a 9.99.4 amd64 host: dependall ===> tests/crypto/libcrypto/srp

Re: build error with MKX11MOTIF=yes in mk.conf

2019-02-16 Thread Benny Siegert
> MKX11MOTIF=yes This is the first time that I hear of this make variable :) I'd file a PR. -- Benny

Re: Build error - ELF

2015-05-19 Thread Paul Goyette
BTW, this error occurred while building usr.sbin/crash ... On Wed, 20 May 2015, Paul Goyette wrote: On amd64 with up-to-date source tree... /build/netbsd-local/src/usr.sbin/crash/../../sys/ddb/db_elf.c:51:0: error: ELFSIZE redefined [-Werror] #define ELFSIZE DB_ELFSIZE ^ In file included

Re: Build error spdmem.

2015-04-20 Thread Paul Goyette
Thanks - I wonder how it managed to compile here... On Mon, 20 Apr 2015, Ryota Ozaki wrote: Applied. Thanks! ozaki-r On Mon, Apr 20, 2015 at 2:52 PM, henning petersen henning.peter...@t-online.de wrote: In spdmemvar.h is there a space after backslace and one semicolon is missing.

Re: Build error spdmem.

2015-04-20 Thread Ryota Ozaki
Applied. Thanks! ozaki-r On Mon, Apr 20, 2015 at 2:52 PM, henning petersen henning.peter...@t-online.de wrote: In spdmemvar.h is there a space after backslace and one semicolon is missing.

Re: build error for -macppc

2015-02-09 Thread Christian Groessler
On 02/09/15 21:40, Christos Zoulas wrote: In article 54d8ba16.6090...@groessler.org, Christian Groessler ch...@groessler.org wrote: Hi, when cross-building on Linux/x86_64 for macppc I get the following error: Should be fixed now. The build went through. Thanks, chris