Re: Build error
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
>>> Files in flist but missing from DESTDIR.
>>> File wasn't installed ?
>>> --
>>> ./usr/lib/i386/libvers_g.a
>>> ./usr/lib/libvers_g.a
>>> end of 2 missing files ==
>>>
>>> Any clues?
>>
>> FWIW, this build was with all 3 of DEBUG{,LIB,KERNEL} set.
>
>Looks like this debug library goes away with the new heimdal.
>
>I'll commit the changes as soon as I get a clean build.
It was a bug to install it before because LIBISPRIVATE was missing
christos
Re: Build error
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 installed ?
--
./usr/lib/i386/libvers_g.a
./usr/lib/libvers_g.a
end of 2 missing files ==
Any clues?
FWIW, this build was with all 3 of DEBUG{,LIB,KERNEL} set.
Looks like this debug library goes away with the new heimdal.
I'll commit the changes as soon as I get a clean build.
++--+--+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:|
| (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com|
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org |
| & Network Engineer | | pgoyett...@gmail.com |
++--+--+
Re: Build error
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 ?
--
./usr/lib/i386/libvers_g.a
./usr/lib/libvers_g.a
end of 2 missing files ==
Any clues?
FWIW, this build was with all 3 of DEBUG{,LIB,KERNEL} set.
++--+--+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:|
| (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com|
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org |
| & Network Engineer | | pgoyett...@gmail.com |
++--+--+
Re: Build error for HEAD on amd64
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 /build/netbsd-compat/obj/amd64 \ -R /build/netbsd-compat/release \ -V RELEASEMACHINEDIR=amd64 \ -V MKDEBUG=yes \ -V MKKDEBUG=yes \ -U -N2 -m amd64 -j1 release I get: /build/netbsd-compat/src_ro/external/bsd/dhcpcd/dist/src/logerr.c: In function 'vlogprintf_r': /build/netbsd-compat/src_ro/external/bsd/dhcpcd/dist/src/logerr.c:120:8: error:unused variable 'err' [-Werror=unused-variable] FILE *err; ^~~ cc1: all warnings being treated as errors *** [logerr.o] Error code 1 ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error on amd64 -current
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 > > > > > > /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 *ci, vaddr_t target) > > > ^~~~ > > > > It started with this commit: > > > > 2020.06.25.14.52.26 jdolecek src/sys/conf/Makefile.kern.inc 1.274 > > > > enable gcc stack usage limit for kernel functions, set to 3.5 KiB for now > > as that seems to be enough to accomodate the current biggest stack usages > > > > there are about six functions which use over 3KiB local stack, and > > about a dozen between 2-3 KiB, so pushing this further needs more work > > if desired > > > > compile tested on amd64, i386, sparc64, sparc, powerpc (evbppc - BookE), > > m68k (mac68k) > > > > -- > > Andreas Gustafsson, g...@gson.org
Re: Build error on amd64 -current
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: error: stack > > usage is5408 bytes [-Werror=stack-usage=] > > mp_cpu_start(struct cpu_info *ci, vaddr_t target) > > ^~~~ > > It started with this commit: > > 2020.06.25.14.52.26 jdolecek src/sys/conf/Makefile.kern.inc 1.274 > > enable gcc stack usage limit for kernel functions, set to 3.5 KiB for now > as that seems to be enough to accomodate the current biggest stack usages > > there are about six functions which use over 3KiB local stack, and > about a dozen between 2-3 KiB, so pushing this further needs more work > if desired > > compile tested on amd64, i386, sparc64, sparc, powerpc (evbppc - BookE), > m68k (mac68k) > > -- > Andreas Gustafsson, g...@gson.org
Re: Build error on amd64 -current
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 *ci, vaddr_t target) > ^~~~ It started with this commit: 2020.06.25.14.52.26 jdolecek src/sys/conf/Makefile.kern.inc 1.274 enable gcc stack usage limit for kernel functions, set to 3.5 KiB for now as that seems to be enough to accomodate the current biggest stack usages there are about six functions which use over 3KiB local stack, and about a dozen between 2-3 KiB, so pushing this further needs more work if desired compile tested on amd64, i386, sparc64, sparc, powerpc (evbppc - BookE), m68k (mac68k) -- Andreas Gustafsson, g...@gson.org
Re: Build error on amd64 -current
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': /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 *ci, vaddr_t target) ^~~~ cc1: all warnings being treated as errors *** [cpu.o] Error code 1 nbmake[2]: stopped in /build/netbsd-compat/obj/amd64/sys/arch/amd64/compile/INSTALL_XEN3_DOMU 1 error ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ -- Hisashi T Fujinaka - ht...@twofifty.com BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee
Re: Build error with MKDEBUG=yes
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 missing files == *** [checkflist] Error code 1 This is with sources updated on 2020-06-07 at 19:48:54 UTC Should be fixed now. rin
Re: Build error when crypto and swcrypto are omitted from kernel
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 option later if needed (I don't like a SMALL option as it is very unspecific). Martin
Re: Build error when crypto and swcrypto are omitted from kernel
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 kernel
(and an entire ``build.sh release'') and it correctly included the
rijndael stuff (even without the two {,sw}crypto pseudo-devices).
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. Even an
#ifdef SMALL could be easier to maintain.
Yep, that would work, too. I'm open to either approach, just would
like to move forward.
++--+---+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org |
++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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 correctly included the
>rijndael stuff (even without the two {,sw}crypto pseudo-devices).
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. Even an
#ifdef SMALL could be easier to maintain.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
Re: Build error when crypto and swcrypto are omitted from kernel
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 expended, so why not?
FWIW, I have just successfully completed my build of my custom kernel
(and an entire ``build.sh release'') and it correctly included the
rijndael stuff (even without the two {,sw}crypto pseudo-devices).
I'd be happy to do the commit if you don't want to expend any further
effort here.
++--+---+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org |
++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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? ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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 Snark may lurk in every tree."
Re: Build error when crypto and swcrypto are omitted from kernel
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 add VM_SWAPCRYPT option to various kernels (GENERIC*, XEN3*, ...)? It's a default option in sys/conf/std. Individual kernels can disable it with 'no options VMSWAPCRYPT'. Yeah, found that. FWIW, here's an additional patch to update the options(4) man page: Index: share/man/man4/options.4 === RCS file: /cvsroot/src/share/man/man4/options.4,v retrieving revision 1.512 diff -u -p -r1.512 options.4 --- share/man/man4/options.424 Apr 2020 13:54:56 - 1.512 +++ share/man/man4/options.410 May 2020 17:11:27 - @@ -2221,6 +2221,9 @@ for port specific details including avai .It Cd options VMSWAP Enable paging device/file support. This option is on by default. +.It Cd options VMSWAPCRYPT +Enable encryption of swapfile. +This option is on by default. .It Cd options PDPOLICY_CLOCKPRO Use CLOCK-Pro, an alternative page replace policy. .El ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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*, ...)? Oh never mind - you already added it to std. :) Please commit. ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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. ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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 of the crypto module.) Even without 'pseudo-device crypto' some kernels still build, as long as the dependency to the rijndael files exists in the kernel configuration. This is e.g. true if you built with wlan drivers or cgd. 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 16kB). Otherwise you could just add the dependency to uvm unconditionally. Seems to me that any attempt to enable encrypted-swap should also trigger an auto-load for the crypto module. Appropriate module hooks should be used to avoid the undefined symbols. The rijndael code is not a module, and the crypto module is neither used nor referenced, it shouldn't be loaded then. You would be perfectly right if it wasn't rijndael but e.g. des. Ah, OK, I got it now. Thanks for your patience. ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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 'pseudo-device crypto' some kernels still build, as long as the dependency to the rijndael files exists in the kernel configuration. This is e.g. true if you built with wlan drivers or cgd. > > 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 16kB). > > > > Otherwise you could just add the dependency to uvm unconditionally. > > Seems to me that any attempt to enable encrypted-swap should also > trigger an auto-load for the crypto module. Appropriate module hooks > should be used to avoid the undefined symbols. The rijndael code is not a module, and the crypto module is neither used nor referenced, it shouldn't be loaded then. You would be perfectly right if it wasn't rijndael but e.g. des. Greetings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: Build error when crypto and swcrypto are omitted from kernel
> 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 16kB). LGTM, feel free to commit.
Re: Build error when crypto and swcrypto are omitted from kernel
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 rijndael_makeKey Since the two crypto devices are optional (and run-time loadable) components of the kernel, it seems to me that encrypted-swap should also be optional. rijndael isn't (yet) optional as it is required by ipsec and wlan code. We just miss the dependency for the encrypted swap functionality. 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.) 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 16kB). Otherwise you could just add the dependency to uvm unconditionally. Seems to me that any attempt to enable encrypted-swap should also trigger an auto-load for the crypto module. Appropriate module hooks should be used to avoid the undefined symbols. ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error when crypto and swcrypto are omitted from kernel
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 optional (and run-time loadable) >components of the kernel, it seems to me that encrypted-swap should >also be optional. rijndael isn't (yet) optional as it is required by ipsec and wlan code. We just miss the dependency for the encrypted swap functionality. 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 16kB). Otherwise you could just add the dependency to uvm unconditionally. -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: Build error for port-sparc
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 ===> external/bsd/pam-u2f/bin/pamu2fcfg #create pamu2fcfg/explicit_bzero.d CC=/build/netbsd-compat/tools/x86_64/sparc/bin/sparc--netbsdelf-gcc /build/netbsd-compat/tools/x86_64/sparc/bin/nbmkdep -f explicit_bzero.d.tmp -- -std=gnu99 --sysroot=/build/netbsd-compat/dest/sparc -I/build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist -I/build/netbsd-compat/src_ro/external/bsd/pam-u2f/bin/pamu2fcfg -DPACKAGE='"pam_u2f"' -DVERSION='"1.0.9"' -DHAVE_UNISTD_H /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/explicit_bzero.c && mv -f explicit_bzero.d.tmp explicit_bzero.d In file included from /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/explicit_bzero.c:16: /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/util.h:9:10: fatal error: security/pam_appl.h: No such file or directory #include ^ compilation terminated. nbmkdep: compile failed. *** [explicit_bzero.d] Error code 1 Again, I'm seeing this _only_ for sparc. I've done ``build.sh release'' for literally dozens of other $ARCH without any problems. Anyone got a clue? On Tue, 3 Mar 2020, Paul Goyette wrote: With sources updated on 2020-03-02 at 13:13:48 UTC I am getting the following build error when doing a ``build.sh release'' # compile ramdisk/gethost.o /build/netbsd-compat/tools/x86_64/sparc/bin/sparc--netbsdelf-gcc -Os -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Werror --sysroot=/build/netbsd-compat/dest/sparc -DSMALL -DLIBHACK -D_REENTRANT -c -I/build/netbsd-compat/src_ro/distrib/utils/libhack/../../../lib/libc/net /build/netbsd-compat/src_ro/distrib/utils/libhack/gethost.c /build/netbsd-compat/src_ro/distrib/utils/libhack/gethost.c:76:1: error: function declaration isn't a prototype [-Werror=strict-prototypes] int h_errno; ^~~ cc1: all warnings being treated as errors ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error for port-sparc
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 /build/netbsd-compat/tools/x86_64/sparc/bin/nbmkdep -f explicit_bzero.d.tmp -- -std=gnu99 --sysroot=/build/netbsd-compat/dest/sparc -I/build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist -I/build/netbsd-compat/src_ro/external/bsd/pam-u2f/bin/pamu2fcfg -DPACKAGE='"pam_u2f"' -DVERSION='"1.0.9"' -DHAVE_UNISTD_H /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/explicit_bzero.c && mv -f explicit_bzero.d.tmp explicit_bzero.d In file included from /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/explicit_bzero.c:16: /build/netbsd-compat/src_ro/external/bsd/pam-u2f/dist/util.h:9:10: fatal error: security/pam_appl.h: No such file or directory #include ^ compilation terminated. nbmkdep: compile failed. *** [explicit_bzero.d] Error code 1 Again, I'm seeing this _only_ for sparc. I've done ``build.sh release'' for literally dozens of other $ARCH without any problems. Anyone got a clue? On Tue, 3 Mar 2020, Paul Goyette wrote: With sources updated on 2020-03-02 at 13:13:48 UTC I am getting the following build error when doing a ``build.sh release'' # compile ramdisk/gethost.o /build/netbsd-compat/tools/x86_64/sparc/bin/sparc--netbsdelf-gcc -Os -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Werror --sysroot=/build/netbsd-compat/dest/sparc -DSMALL -DLIBHACK -D_REENTRANT -c -I/build/netbsd-compat/src_ro/distrib/utils/libhack/../../../lib/libc/net /build/netbsd-compat/src_ro/distrib/utils/libhack/gethost.c /build/netbsd-compat/src_ro/distrib/utils/libhack/gethost.c:76:1: error: function declaration isn't a prototype [-Werror=strict-prototypes] int h_errno; ^~~ cc1: all warnings being treated as errors ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: Build error
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 /build/netbsd-local/tools/x86_64/amd64/lib/gcc/x86_64--netbsd/7.4.0/../../../../x86_64--netbsd/bin/ld: /build/netbsd-local/dest/amd64/lib/libnpf.so: undefined reference to `nvlist_exists' /build/netbsd-local/tools/x86_64/amd64/lib/gcc/x86_64--netbsd/7.4.0/../../../../x86_64--netbsd/bin/ld: /build/netbsd-local/dest/amd64/lib/libnpf.so: undefined reference to `dnvlist_take_number' (several more undefined references follow) ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+ ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: build error with MKX11MOTIF=yes in mk.conf
> MKX11MOTIF=yes This is the first time that I hear of this make variable :) I'd file a PR. -- Benny
Re: Build error - ELF
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 from /build/netbsd-local/src/usr.sbin/crash/../../sys/sys/ksyms.h:33:0, from /build/netbsd-local/src/usr.sbin/crash/../../sys/ddb/db_sym.h:31, from /build/netbsd-local/src/usr.sbin/crash/../../sys/ddb/ddb.h:46, from /build/netbsd-local/src/usr.sbin/crash/../../sys/ddb/db_elf.c:40: /build/netbsd-local/src/usr.sbin/crash/../../sys/sys/exec_elf.h:1030:0: note: this is the location of the previous definition #define ELFSIZE ARCH_ELFSIZE ^ - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | - - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | -
Re: Build error spdmem.
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. - | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com| | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | -
Re: Build error spdmem.
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
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
