Re: buildworld failure due to md5 not supported by openssl3
Date:Fri, 24 Nov 2023 19:45:00 +0100 From:Ede Wolf Message-ID: <6b8e764f-6f34-4f4e-82e1-2c7e7b724...@nebelschwaden.de> | I am having somewhat cosmetic wm(4) issues though, but that is more for | the alpha-port list, as at least on vbox - the only other machine I have | with wm drivers - those issues do not appear. As I understand it, which isn't very much, hardware issues aren't really my thing, many hardware wm devices have errata that need working around, and there's no guarantee that we have workarounds for all the varieties that exist in the tree. Things generally basically work anyway, but there can be issues. A software implementation (like on vbox) is less likely to have problems like that, as any issues that arise can just get fixed in the next vbox update - that's like many many orders of magnitude harder to do with hardware that's already been sold and doesn't rely upon loadable firmware. | Talking about virtualbox. On vbox 7.0.12 (running on a linux host) I was | unable to install amd64 10RC1 with vitio-net. Sorry, can't help with that one either, or certainly without a lot more debugging info as to what was actually happening. | No issues with the emulated Pro/1000MT. Good enough for me Yes, when I did use virtualbox (needed on my laptop before previously so I could run NetBSD) there were several cases like that - just find the emulated hardware that works, and use that - forget anything that doesn't... The change to the order of the lines in that libsaslc/lib/Makefile has been made in the HEAD sources - it needs fixing in NetBSD 10 as well, and it looks as if Christos didn't send a pullup for the change, so I will ... kre
Re: buildworld failure due to md5 not supported by openssl3
Am 24.11.23 um 18:53 schrieb Robert Elz: Date:Fri, 24 Nov 2023 17:21:42 +0100 From:Ede Wolf Message-ID: <5b8928a4-32b5-4015-8eb1-2432d3eb6...@nebelschwaden.de> | For what it is worth, as you have probably known it before, here my | confirmation: Swapping those lines and disabling kerberos the build | finished without problems. Thanks - I hadn't actually tested it, but I was fairly confident that would be what happened. | So I cannot comment on how usable this build is. Aside from not having Kerberos, it should be identical to the previous one - if you haven't tested that either, ie: you haven't run HEAD at all on your alpha yet, then please do send a message if there are any issues when you do get a chance to try it. I've been running 10RC1 on the alpha for around two weeks, but just from the install sets, not yet rebuild, as it was failing so far (most likely due to my mistakes). buildworld has now been running for over 24h, a new record. So I am cautiosly optimistic this time. Kernel build and runs nicely from the start. I am having somewhat cosmetic wm(4) issues though, but that is more for the alpha-port list, as at least on vbox - the only other machine I have with wm drivers - those issues do not appear. Talking about virtualbox. On vbox 7.0.12 (running on a linux host) I was unable to install amd64 10RC1 with vitio-net. Tried multiple times across reboots, but I would always loose network connection at somepoint during the download of the sets. The download would stall and despite claiming to still having a link, the default gw was not reachable any more. Nothing in /var/log/messages I could identify. But that may well be due to virtualbox and fixed with the next update - or my setup. No issues with the emulated Pro/1000MT. Good enough for me So only very minor stuff to report so far. The isp/scsi issue (adapter resource shortage) has already been reported, and has also been an issue with 9.x, so no regression here. And is very alpha specific anyway. It is tier 2 after all. Big thanks for keeping it alive to all involved! Have a great weekend Ede
Re: buildworld failure due to md5 not supported by openssl3
Date:Fri, 24 Nov 2023 17:21:42 +0100 From:Ede Wolf Message-ID: <5b8928a4-32b5-4015-8eb1-2432d3eb6...@nebelschwaden.de> | For what it is worth, as you have probably known it before, here my | confirmation: Swapping those lines and disabling kerberos the build | finished without problems. Thanks - I hadn't actually tested it, but I was fairly confident that would be what happened. | So I cannot comment on how usable this build is. Aside from not having Kerberos, it should be identical to the previous one - if you haven't tested that either, ie: you haven't run HEAD at all on your alpha yet, then please do send a message if there are any issues when you do get a chance to try it. I have asked if those 2 lines can be swapped around in the distribution sources, and I suspect that will happen soon, unless there was some obscure reason (rather than just an editing error) for the positioning. kre
Re: buildworld failure due to md5 not supported by openssl3
Am 23.11.23 um 13:34 schrieb Robert Elz: Date:Thu, 23 Nov 2023 12:13:42 +0100 From:Ede Wolf Message-ID: <77602506-626c-4fff-90ec-48e2f4aaf...@nebelschwaden.de> | Ok, I did not see this as yet verified, because, as with MKKERBEROS=yes | and USE_KERBEROS=yes the build fails as well. Even though at a slightly | different place, but still crypto related. | | But very likely that those are related. I'll just sit back, relax and wait. I'll do a build in a minute, using your mk.conf settings, and see if I can work out what other hidden dependency that we have that is causing the problem. This one isn't as obvious as the last one. If you want to do something other than wait (and perhaps, just perhaps, get a usable build) you can try altering src/crypto/external/bsd/libsaslc/lib/Makefile Swap the order of the two lines: COPTS.crypto.c+=-Wno-error=deprecated-declarations .endif (so you get: .endif COPTS.crypto.c+=-Wno-error=deprecated-declarations instead) and then go back to your original mk.conf with MKKERBEROS=no (etc) and see what happens. For what it is worth, as you have probably known it before, here my confirmation: Swapping those lines and disabling kerberos the build finished without problems. ===> Built sets to /data/release/alpha/binary/sets ===> build.sh ended: Fri Nov 24 16:40:28 CET 2023 ===> Summary of results: build.sh command:./build.sh -a alpha -m alpha -j 4 -r -M /data/obj -D /data/destdir -R /data/release distsets build.sh started:Fri Nov 24 16:22:45 CET 2023 NetBSD version: 10.0_RC1 MACHINE: alpha MACHINE_ARCH:alpha Build platform: NetBSD 10.0_RC1 amd64 HOST_SH: /bin/sh No $TOOLDIR/bin/nbmake, needs building. Bootstrapping nbmake MAKECONF file: /etc/mk.conf TOOLDIR path: /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64 DESTDIR path:/data/destdir RELEASEDIR path: /data/release Removing /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64 Removing /data/destdir Created /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake Updated makewrapper: /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake-alpha Successful make distribution Building sets from pre-populated /data/destdir Built sets to /data/release/alpha/binary/sets build.sh ended: Fri Nov 24 16:40:28 CET 2023 ===> . real 1063.70 user 2772.26 sys503.11 buildbsd# grep -A1 -B1 "COPTS.crypto" /data/src/crypto/external/bsd/libsaslc/lib/Makefile .endif COPTS.crypto.c+=-Wno-error=deprecated-declarations buildbsd# I have however not installed these sets, as my alpha also is still trying to build itself, which may go on for another couple of days. If successful this time, that is. So I cannot comment on how usable this build is. Thanks again for your help
Re: buildworld failure due to md5 not supported by openssl3
So one thing to check is that while you didn't seem to be doing an update build, so everything should have been cleaned before it started, you might want to try making certain of that by manually cleaning it all (rm -fr on relevant directories) and trying again. It is possible that the change of MKKERBEROS allowed something to not get properly cleaned, which later messed up the build. kre That hit the nail. While I was eagerly cleaning the objdir after each build, I did not pay attention to destdir, probably as I was assuming this only to being populated at the end of a successfull build. Cleaning this directory and the build finishes (with kerberos enabled, of course). Thanks very much again for your time and effort. I will try swapping the lines in the libsasl Makefile and rebuilding world tomorrow. ===> Built sets to /data/release/alpha/binary/sets ===> build.sh ended: Thu Nov 23 17:08:03 CET 2023 ===> Summary of results: build.sh command:./build.sh -a alpha -m alpha -j 4 -r -M /data/obj -D /data/destdir -R /data/release distsets build.sh started:Thu Nov 23 16:49:26 CET 2023 NetBSD version: 10.0_RC1 MACHINE: alpha MACHINE_ARCH:alpha Build platform: NetBSD 10.0_RC1 amd64 HOST_SH: /bin/sh No $TOOLDIR/bin/nbmake, needs building. Bootstrapping nbmake MAKECONF file: /etc/mk.conf TOOLDIR path: /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64 DESTDIR path:/data/destdir RELEASEDIR path: /data/release Removing /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64 Removing /data/destdir Created /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake Updated makewrapper: /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake-alpha Successful make distribution Building sets from pre-populated /data/destdir Built sets to /data/release/alpha/binary/sets build.sh ended: Thu Nov 23 17:08:03 CET 2023 ===> . real 1117.69 user 2933.00 sys544.16 Interestingly, gpufw did get it's own set, despite not being defined. Same goes for rescue. Not an issue at all, though, of course.
Re: buildworld failure due to md5 not supported by openssl3
I just did an alpha build as follows. The -V's are what's in your mk.conf I believe (with MKKERBEROS=yes and USE_KERBEROS=yes) and it worked without issue. The build host is close enough to yours (kernel is 10.99.10 but that's irrelevant - userland is HEAD from before -10 was branched, but not all that long before). The sources don't have the Makefile change that would allow building with MKKERBEROS=no so I didn't try that. build.sh command:build.sh -j 16 -V MKATF=no -V MKCLEANSRC=yes -V MK CLEANVERIFY=yes -V MKCOMPAT=no -V MKCVS=yes -V MKDEBUGLIB=no -V MKDOC=yes -V MKD TRACE=no -V MKGDB=no -V MKHOSTOBJ=no -V MKHTML=no -V MKINFO=no -V MKIPFILTER=no -V MKISCSI=yes -V MKKERBEROS=yes -V USE_KERBEROS=yes -V MKLDAP=no -V USE_LDAP=no -V MKLVM=no -V MKMANZ=yes -V MKMDNS=no -V MKNOUVEAUFIRMWARE=no -V MKNPF=yes -V MKPF=no -V MKPOSTFIX=yes -V MKPROFILE=no -V MKRADEONFIRMWARE=no -V MKREPRO=yes - V MKRUMP=no -V MKX11=no -V MKX11FONTS=no -V MKX11MOTIF=no -V MKZFS=no -V MKYP=no -V USE_YP=no -V MKHESIOD=no -V USE_HESIOD=no -V MKPAM=yes -V USE_PAM=yes -V MKS KEY=no -V USE_SKEY=no -m alpha -D /release/testing/alpha -O /usr/obj/testing/alp ha -R /local/snap/20231123-testing-10.99.10-alpha -T /usr/obj/testing/tools -X / readonly/release/testing/src/xsrc -u -x iso-image build.sh started:Thu Nov 23 20:04:16 +07 2023 NetBSD version: 10.99.10 MACHINE: alpha MACHINE_ARCH:alpha Build platform: NetBSD 10.99.10 amd64 HOST_SH: /bin/sh getenv MAKECONF: /dev/null MAKECONF file: /dev/null TOOLDIR path:/usr/obj/testing/tools DESTDIR path:/release/testing/alpha RELEASEDIR path: /local/snap/20231123-testing-10.99.10-alpha Updated makewrapper: /usr/obj/testing/tools/bin/nbmake-alpha MKREPRO_TIMESTAMPWed Nov 22 14:51:55 UTC 2023 Successful make iso-image build.sh ended: Thu Nov 23 20:06:04 +07 2023 While I use '-u' (update build) this is the first alpha build I've done in decades I think (certainly the first on this system) so everything was clean to start with (no .o files, no .d (dependency) files, I had to actually mkdir the target (DESTDIR) directory - so that was certainly empty). So one thing to check is that while you didn't seem to be doing an update build, so everything should have been cleaned before it started, you might want to try making certain of that by manually cleaning it all (rm -fr on relevant directories) and trying again. It is possible that the change of MKKERBEROS allowed something to not get properly cleaned, which later messed up the build. kre ps: I actually did a release build - rather than the same as yours, not really by design, but just because that's what I normally always do, and I didn't think to change it! I was expecting the build to fail the way you reported, so I didn't thing it would make any real difference.
Re: buildworld failure due to md5 not supported by openssl3
Date:Thu, 23 Nov 2023 12:13:42 +0100 From:Ede Wolf Message-ID: <77602506-626c-4fff-90ec-48e2f4aaf...@nebelschwaden.de> | Ok, I did not see this as yet verified, because, as with MKKERBEROS=yes | and USE_KERBEROS=yes the build fails as well. Even though at a slightly | different place, but still crypto related. | | But very likely that those are related. I'll just sit back, relax and wait. I'll do a build in a minute, using your mk.conf settings, and see if I can work out what other hidden dependency that we have that is causing the problem. This one isn't as obvious as the last one. If you want to do something other than wait (and perhaps, just perhaps, get a usable build) you can try altering src/crypto/external/bsd/libsaslc/lib/Makefile Swap the order of the two lines: COPTS.crypto.c+=-Wno-error=deprecated-declarations .endif (so you get: .endif COPTS.crypto.c+=-Wno-error=deprecated-declarations instead) and then go back to your original mk.conf with MKKERBEROS=no (etc) and see what happens. kre kre
Re: buildworld failure due to md5 not supported by openssl3
Am 23.11.23 um 12:00 schrieb Martin Husemann: On Thu, Nov 23, 2023 at 11:58:08AM +0100, Ede Wolf wrote: Btw, this does not seem to be alpha-port specific. I've just tried to compile on amd64 for amd64, exactly the same mk.conf (with the obvious exception of CPUFLAGS) and of course changing -a and -m for build.sh: As Robert noted, it is MKKERBEROS=no that breaks it. The CWARNFLAGS setting in the makefile needs to be rearragend. Martin Ok, I did not see this as yet verified, because, as with MKKERBEROS=yes and USE_KERBEROS=yes the build fails as well. Even though at a slightly different place, but still crypto related. But very likely that those are related. I'll just sit back, relax and wait. Thanks very much again to all of you for your support Ede
Re: buildworld failure due to md5 not supported by openssl3
On Thu, Nov 23, 2023 at 11:58:08AM +0100, Ede Wolf wrote: > Btw, this does not seem to be alpha-port specific. I've just tried to > compile on amd64 for amd64, exactly the same mk.conf (with the obvious > exception of CPUFLAGS) and of course changing -a and -m for build.sh: As Robert noted, it is MKKERBEROS=no that breaks it. The CWARNFLAGS setting in the makefile needs to be rearragend. Martin
Re: buildworld failure due to md5 not supported by openssl3
Am 23.11.23 um 10:21 schrieb Ede Wolf: Am 22.11.23 um 17:00 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: My build says somethig different about warnings and errors (Marking by me, of course): /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hex': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 233 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ My build says: # compile lib/crypto.o /work/tools/bin/alpha--netbsd-gcc -O2 -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -mieee --sysroot=/work/hosts/alpha -I/work/src/crypto/external/bsd/libsaslc/lib/../dist/include -c -Wno-error=deprecated-declarations /work/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c -o crypto.o Note that it has: -Wno-error=deprecated-declarations (which comes from COPTS.crypto.c in the Makefile there). So something in your setup must override that, but it is not obvious to me right now. If you go into src/crypto/external/bsd/libsaslc/lib and invoke your $TOOLDIR/bin/nbmake-alpha with "-v COPTS.crypto.c" - what does it say? Or it may override the construction of the final flags from that variable, maybe due to your CPUFLAGS settings? The output is, as you have expected: buildbsd# cd /data/src/crypto/external/bsd/libsaslc/lib/ buildbsd# /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake-alpha -v COPTS.crypto.c -Wno-error=deprecated-declarations buildbsd# And it is not the CPUFLAGS, I've just tried a rebuild without any COPT/CPU- or CFAGS at all (with objdir completely clean) and am running into the same error: --- crypto.pico --- /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hash': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 218 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ In file included from /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50: /data/destdir/usr/include/openssl/md5.h:52:38: note: declared here 52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned char *d, size_t n, | ^~~ /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hex': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 233 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ Btw, this does not seem to be alpha-port specific. I've just tried to compile on amd64 for amd64, exactly the same mk.conf (with the obvious exception of CPUFLAGS) and of course changing -a and -m for build.sh: # compile lib/crypto.pico /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/x86_64--netbsd-gcc -O2 -fdebug-prefix-map=\$DESTDIR= -fdebug-prefix-map=\$NETBSDSRCDIR=/usr/src -fdebug-prefix-map=\$X11SRCDIR=/usr/xsrc -fdebug-prefix-map=\$NETBSDOBJDIR=/usr/obj -fdebug-regex-map='/usr/src/(.*)/obj$=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj/(.*)=/usr/obj/\1/\2' -fdebug-regex-map='/usr/src/(.*)/obj\..*=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj\..*/(.*)=/usr/obj/\1/\2' -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -march=znver2 -mtune=znver2 -fPIE--sysroot=/data/destdir -I/data/src/crypto/external/bsd/libsaslc/lib/../dist/include -Wp,-iremap,/data/destdir: -Wp,-fno-canonical-system-headers -Wp,-iremap,/data/src:/usr/src -Wp,-iremap,/usr/xsrc:/usr/xsrc -c -fPIC /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c -o crypto.pico /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hash': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 218 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ In file included from /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50: /data/destdir/usr/include/openssl/md5.h:52:38: note: declared here 52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned
Re: buildworld failure due to md5 not supported by openssl3
Am 22.11.23 um 17:59 schrieb tlaro...@kergis.com: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: [...] My mk.conf should be rather unspectacular as well: # cat /etc/mk.conf CPUFLAGS = -mcpu=21164a # world related stuff: NETBSDSRCDIR=/data/src BSDOBJDIR=/data/obj INSTALLWORLDDIR=/data/install DESTDIR=/data/destdir RELEASEDIR=/data/release USETOOLS=yes INSTALLSETS=base comp etc games man misc text modules FWIW, your INSTALLSETS should probably include gpufw (gpu firmware). We are talking here about a headless machine, that does not even have a graphics card installed, nor have one onboard. Unless the firmware serves any further purpose, other than the name suggests, I would not see a reason. But thanks very much for following this issue and checking carefully through my settings
Re: buildworld failure due to md5 not supported by openssl3
Am 22.11.23 um 17:49 schrieb Robert Elz:
Date:Wed, 22 Nov 2023 16:21:01 +0100
From:Ede Wolf
Message-ID:
| # cat /etc/mk.conf
| MKKERBEROS=no
That one is the problem, the COPTS.crypto.c entry that Martin mentioned
is not included if MKKERBEROS is "no".
I have no idea why.
kre
Thanks. Setting MKKERBEROS=yes at least somewhat changes the failure:
--- dependall ---
--- /data/destdir/usr/include/krb5/krb5_err.h ---
--- /data/destdir/usr/include/krb5/heim_err.h ---
--- /data/destdir/usr/include/krb5/k524_err.h ---
--- /data/destdir/usr/include/krb5/krb_err.h ---
nbmake[6]: nbmake[6]: don't know how to make /libcrypto.a. Stop
nbmake[6]: stopped in /data/src/crypto/external/bsd/heimdal/lib/libkrb5
nbmake[5]: stopped in /data/src/crypto/external/bsd/heimdal/lib/libkrb5
*** Failed target: dependall-../crypto/external/bsd/heimdal/lib/libkrb5
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1";
shift; case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .)
this="lib/"; real="/data/src/lib" ;; *) this="lib/${dir}/";
real="/data/src/lib/${dir}" ;; esac; show=${this:-.}; echo "${target}
===> ${show%/}${1:+ (with: $@)}"; cd "${real}" &&
/data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake
_THISDIR_="${this}" "$@" ${target}; }; _makedirtarget
../crypto/external/bsd/heimdal/lib/libkrb5 dependall
*** Error code 2
Stop.
nbmake[4]: stopped in /data/src/lib
*** Failed target: build_install
*** Failed commands:
${MAKEDIRTARGET} . ${SUBDIR_GROUP.${:U1}:C/^/dependall-/}
By the way, I am not setting any build related stuff in my environment:
buildbsd# env
ENV=/root/.shrc
BLOCKSIZE=1k
PWD=/root
MAIL=/var/mail/root
HOME=/root
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/usr/games:/usr/X11R7/bin:/usr/local/sbin:/usr/local/bin
HOST=buildbsd.nebelschwaden.de
SSH_CONNECTION=192.168.17.1 58006 192.168.17.22 22
SSH_TTY=/dev/pts/1
TERM=xterm-256color
USER=root
SSH_AUTH_INFO_0=keyboard-interactive/pam
SSH_CLIENT=192.168.17.1 58006 22
CVSROOT=anon...@anoncvs.netbsd.org:/cvsroot
LOGNAME=root
SHELL=/bin/sh
Re: buildworld failure due to md5 not supported by openssl3
Am 22.11.23 um 17:00 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: My build says somethig different about warnings and errors (Marking by me, of course): /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hex': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 233 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ My build says: # compile lib/crypto.o /work/tools/bin/alpha--netbsd-gcc -O2 -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -mieee --sysroot=/work/hosts/alpha -I/work/src/crypto/external/bsd/libsaslc/lib/../dist/include -c -Wno-error=deprecated-declarations /work/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c -o crypto.o Note that it has: -Wno-error=deprecated-declarations (which comes from COPTS.crypto.c in the Makefile there). So something in your setup must override that, but it is not obvious to me right now. If you go into src/crypto/external/bsd/libsaslc/lib and invoke your $TOOLDIR/bin/nbmake-alpha with "-v COPTS.crypto.c" - what does it say? Or it may override the construction of the final flags from that variable, maybe due to your CPUFLAGS settings? The output is, as you have expected: buildbsd# cd /data/src/crypto/external/bsd/libsaslc/lib/ buildbsd# /data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/nbmake-alpha -v COPTS.crypto.c -Wno-error=deprecated-declarations buildbsd# And it is not the CPUFLAGS, I've just tried a rebuild without any COPT/CPU- or CFAGS at all (with objdir completely clean) and am running into the same error: --- crypto.pico --- /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hash': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 218 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ In file included from /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50: /data/destdir/usr/include/openssl/md5.h:52:38: note: declared here 52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned char *d, size_t n, | ^~~ /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hex': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 233 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^
Re: buildworld failure due to md5 not supported by openssl3
On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: >[...] > My mk.conf should be rather unspectacular as well: > > > # cat /etc/mk.conf > > CPUFLAGS = -mcpu=21164a > > # world related stuff: > > NETBSDSRCDIR=/data/src > BSDOBJDIR=/data/obj > INSTALLWORLDDIR=/data/install > DESTDIR=/data/destdir > RELEASEDIR=/data/release > USETOOLS=yes > INSTALLSETS=base comp etc games man misc text modules FWIW, your INSTALLSETS should probably include gpufw (gpu firmware). -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: buildworld failure due to md5 not supported by openssl3
Date:Wed, 22 Nov 2023 16:21:01 +0100 From:Ede Wolf Message-ID: | # cat /etc/mk.conf | MKKERBEROS=no That one is the problem, the COPTS.crypto.c entry that Martin mentioned is not included if MKKERBEROS is "no". I have no idea why. kre
Re: buildworld failure due to md5 not supported by openssl3
Date:Wed, 22 Nov 2023 16:21:01 +0100 From:Ede Wolf Message-ID: | My command: | | ./build.sh -a alpha -m alpha -j 4 -r -M /data/obj -D /data/destdir -R | /data/release distsets | | My mk.conf should be rather unspectacular as well: | | | # cat /etc/mk.conf That all looks clean enough - but what about your environment? Do you have CFLAGS or COPTS or anything similar in the environment? kre
Re: buildworld failure due to md5 not supported by openssl3
On Wed, Nov 22, 2023 at 04:21:01PM +0100, Ede Wolf wrote: > My build says somethig different about warnings and errors (Marking by me, > of course): > > /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function > 'saslc__crypto_md5_hex': > /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: > error: 'MD5' is deprecated: Since OpenSSL 3.0 > [-Werror=deprecated-declarations] > 233 | (void)MD5((const unsigned char *)buf, buflen, digest); > | ^ My build says: # compile lib/crypto.o /work/tools/bin/alpha--netbsd-gcc -O2 -std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -mieee --sysroot=/work/hosts/alpha -I/work/src/crypto/external/bsd/libsaslc/lib/../dist/include -c -Wno-error=deprecated-declarations /work/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c -o crypto.o Note that it has: -Wno-error=deprecated-declarations (which comes from COPTS.crypto.c in the Makefile there). So something in your setup must override that, but it is not obvious to me right now. If you go into src/crypto/external/bsd/libsaslc/lib and invoke your $TOOLDIR/bin/nbmake-alpha with "-v COPTS.crypto.c" - what does it say? Or it may override the construction of the final flags from that variable, maybe due to your CPUFLAGS settings? Martin
Re: buildworld failure due to md5 not supported by openssl3
Am 22.11.23 um 12:25 schrieb Martin Husemann: On Wed, Nov 22, 2023 at 12:00:10PM +0100, Ede Wolf wrote: Hello, just trying to crosscompile world, which fails with crypto not being able to be build, as MD5 is claimed to not be supported by openssl3. Is it just me or is anything known? cvs updated just an hour or so ago: /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hash': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 218 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ This warnings are not treated as errors in the build usually, how are you doing this build? Anything special in /etc/mk.conf? Martin My build says somethig different about warnings and errors (Marking by me, of course): /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function 'saslc__crypto_md5_hex': /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2: error: 'MD5' is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 233 | (void)MD5((const unsigned char *)buf, buflen, digest); | ^ In file included from /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50: /data/destdir/usr/include/openssl/md5.h:52:38: note: declared here 52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned char *d, size_t n, | ^~~ cc1: all warnings being treated as errors <<< --- *** Failed target: crypto.pico *** Failed commands: My command: ./build.sh -a alpha -m alpha -j 4 -r -M /data/obj -D /data/destdir -R /data/release distsets My mk.conf should be rather unspectacular as well: # cat /etc/mk.conf CPUFLAGS = -mcpu=21164a # world related stuff: NETBSDSRCDIR=/data/src BSDOBJDIR=/data/obj INSTALLWORLDDIR=/data/install DESTDIR=/data/destdir RELEASEDIR=/data/release USETOOLS=yes INSTALLSETS=base comp etc games man misc text modules MKATF=no MKCLEANSRC=yes MKCLEANVERIFY=yes MKCOMPAT=no MKCVS=yes MKDEBUGLIB=no MKDOC=yes MKDTRACE=no MKGDB=no MKHOSTOBJ=no MKHTML=no MKINFO=no MKIPFILTER=no MKISCSI=yes MKKERBEROS=no USE_KERBEROS=no MKLDAP=no USE_LDAP=no MKLVM=no MKMANZ=yes MKMDNS=no MKNOUVEAUFIRMWARE=no MKNPF=yes MKPF=no MKPOSTFIX=yes MKPROFILE=no MKRADEONFIRMWARE=no MKREPRO=yes MKRUMP=no MKX11=no MKX11FONTS=no MKX11MOTIF=no MKZFS=no MKYP=no USE_YP=no MKHESIOD=no USE_HESIOD=no MKPAM=yes USE_PAM=yes MKSKEY=no USE_SKEY=no Thanks again for your time. The host that is doing the build is a standard NetBSD 10RC1 on amd64, Generic Kernel, generic sets. Ede
Re: buildworld failure due to md5 not supported by openssl3
On Wed, Nov 22, 2023 at 12:00:10PM +0100, Ede Wolf wrote: > Hello, > > just trying to crosscompile world, which fails with crypto not being able to > be build, as MD5 is claimed to not be supported by openssl3. > Is it just me or is anything known? cvs updated just an hour or so ago: > > > /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In function > 'saslc__crypto_md5_hash': > /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3: > error: 'MD5' is deprecated: Since OpenSSL 3.0 > [-Werror=deprecated-declarations] > 218 | (void)MD5((const unsigned char *)buf, buflen, digest); > | ^ This warnings are not treated as errors in the build usually, how are you doing this build? Anything special in /etc/mk.conf? Martin
buildworld failure due to md5 not supported by openssl3
Hello,
just trying to crosscompile world, which fails with crypto not being
able to be build, as MD5 is claimed to not be supported by openssl3.
Is it just me or is anything known? cvs updated just an hour or so ago:
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In
function 'saslc__crypto_md5_hash':
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:218:3:
error: 'MD5' is deprecated: Since OpenSSL 3.0
[-Werror=deprecated-declarations]
218 | (void)MD5((const unsigned char *)buf, buflen, digest);
| ^
In file included from
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50:
/data/destdir/usr/include/openssl/md5.h:52:38: note: declared here
52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned char
*d, size_t n,
| ^~~
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c: In
function 'saslc__crypto_md5_hex':
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:233:2:
error: 'MD5' is deprecated: Since OpenSSL 3.0
[-Werror=deprecated-declarations]
233 | (void)MD5((const unsigned char *)buf, buflen, digest);
| ^
In file included from
/data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c:50:
/data/destdir/usr/include/openssl/md5.h:52:38: note: declared here
52 | OSSL_DEPRECATEDIN_3_0 unsigned char *MD5(const unsigned char
*d, size_t n,
| ^~~
cc1: all warnings being treated as errors
*** Failed target: crypto.pico
*** Failed commands:
${_MKTARGET_COMPILE}
=> @echo '# ' "compile " lib/crypto.pico
${COMPILE.c} ${COPTS.${.IMPSRC:T}} ${CPUFLAGS.${.IMPSRC:T}}
${CPPFLAGS.${.IMPSRC:T}} ${CSHLIBFLAGS} ${.IMPSRC} -o ${.TARGET}
=>
/data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/alpha--netbsd-gcc
-O2 -mcpu=21164a -fdebug-prefix-map=\$DESTDIR=
-fdebug-prefix-map=\$NETBSDSRCDIR=/usr/src
-fdebug-prefix-map=\$X11SRCDIR=/usr/xsrc
-fdebug-prefix-map=\$NETBSDOBJDIR=/usr/obj
-fdebug-regex-map='/usr/src/(.*)/obj$=/usr/obj/\1'
-fdebug-regex-map='/usr/src/(.*)/obj/(.*)=/usr/obj/\1/\2'
-fdebug-regex-map='/usr/src/(.*)/obj\..*=/usr/obj/\1'
-fdebug-regex-map='/usr/src/(.*)/obj\..*/(.*)=/usr/obj/\1/\2'
-std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional
-Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual
-Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare
-Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -mieee
-mcpu=21164a--sysroot=/data/destdir
-I/data/src/crypto/external/bsd/libsaslc/lib/../dist/include
-Wp,-iremap,/data/destdir: -Wp,-fno-canonical-system-headers
-Wp,-iremap,/data/src:/usr/src -Wp,-iremap,/usr/xsrc:/usr/xsrc -c
-fPIC /data/src/crypto/external/bsd/libsaslc/lib/../dist/src/crypto.c
-o crypto.pico
${OBJCOPY} ${OBJCOPYLIBFLAGS} ${.TARGET}
=>
/data/obj/data/src/tooldir.NetBSD-10.0_RC1-amd64/bin/alpha--netbsd-objcopy
-x crypto.pico
*** [crypto.pico] Error code 1
