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
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
I have lost my boot menu
Hi There, I need your help. I have reinstalled my NetBSD 10_RC1 on a partition of my GPT partitioned disk. However for some reason, the installation was unsuccessful when writing the OS sets to the disk. I assume the installer wanted to write the USB stick accidentally. The phenomena was that the copy operation was getting more and more time, then stalled. So, I abandoned the installation and went to the console. There I have installed manually. Unfortunately I could not install the boot chain. This means, I have to use my linux's grub2 to start NetBSD now. You can see my disk layout here: -bash-5.2# gpt show ld0 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 342014 Unused 2048 262144 1 GPT part - EFI System 26419233554432 2 GPT part - Linux swap 33818624 134217728 3 GPT part - Linux data 168036352 201326592 4 GPT part - NetBSD FFSv1/FFSv2 369362944 1584160768 5 GPT part - Linux data 19535237121423 Unused 1953525135 32 Sec GPT table 1953525167 1 Sec GPT header -bash-5.2# The EFI partition for NetBSD is like this: -bash-5.2# ls -l /boot/efi/EFI/boo-bash-5.2# ls -l /boot/efi/EFI/boot/bootx64.efi -r-xr-xr-x 1 root wheel 235690 Nov 15 13:56 /boot/efi/EFI/boot/bootx64.efit/bootx64.efi I have copied the boot.cfg into the root of the / partition (dk3) If I want to boot the EFI directly, then it runs the boot program, however it does not show the menu at all. I can boot only like this: boot NAME=NetBSD:netbsd Or, as I mentioned, with GRUB2 directly with the kernel. So, I want to have the menu back as normally. I hope my description makes sense for you. Thank you, FeZ
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 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
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
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
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: X on 10.0 RC1 is unusable on my laptop
On 18/11/2023 11:34, tlaro...@kergis.com wrote: On Sat, Nov 18, 2023 at 11:14:12AM +, Mike Pumford wrote: Yes, there has been a major refactoring in the Linux code regarding headers for example. The whole Linux drm-kms is a (fast) moving target... I found a better source for patch inspiration :). The FreeBSD drm_kmod repositories. I've had some success by looking at the 5.6 branch there which is a nice close match to what NetBSD 10 has. Found this change: https://github.com/freebsd/drm-kmod/commit/1e9cdf6cddb369f7f5ad14203c4bb487520369f7 And translated it into the patch attached to this message. A kernel with this patch boots and runs X successfully Still see a little bit of cache tearing but its better than it was on 9.x (and there are some other patches I've found that might address those). So this fixes kern/57268 (which I raised). I'll send the patch to that later but I thought I'd share as I know a couple of you are also suffering with similar issues that this might fix Snippet from Xorg.0.log [30.585]ABI class: X.Org ANSI C Emulation, version 0.4 [30.623] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) Haswell Desktop [30.623] (II) modeset(0): glamor initialized Tested both firefox and thunderbird including video playback in firefox with no issues. Mike? sys/external/bsd/drm2/dist/drm/i915/gt/intel_workarounds-mp.c ? sys/external/bsd/drm2/dist/drm/i915/gt/intel_workarounds_linux.c Index: sys/external/bsd/drm2/dist/drm/i915/i915_pci.c === RCS file: /cvsroot/src/sys/external/bsd/drm2/dist/drm/i915/i915_pci.c,v retrieving revision 1.4 diff -u -r1.4 i915_pci.c --- sys/external/bsd/drm2/dist/drm/i915/i915_pci.c 19 Dec 2021 01:44:49 - 1.4 +++ sys/external/bsd/drm2/dist/drm/i915/i915_pci.c 22 Nov 2023 20:32:34 - @@ -442,7 +442,7 @@ .has_rc6 = 1, \ .has_rc6p = 1, \ .has_rps = true, \ - .ppgtt_type = INTEL_PPGTT_FULL, \ + .ppgtt_type = INTEL_PPGTT_ALIASING, \ .ppgtt_size = 31, \ IVB_PIPE_OFFSETS, \ IVB_CURSOR_OFFSETS, \ @@ -499,7 +499,7 @@ .has_rps = true, .display.has_gmch = 1, .display.has_hotplug = 1, - .ppgtt_type = INTEL_PPGTT_FULL, + .ppgtt_type = INTEL_PPGTT_ALIASING, .ppgtt_size = 31, .has_snoop = true, .has_coherent_ggtt = false,
Re: X on 10.0 RC1 is unusable on my laptop
On Wed, Nov 22, 2023 at 08:34:22PM +, Mike Pumford wrote: > > And translated it into the patch attached to this message. A kernel with > this patch boots and runs X successfully Still see a little bit of cache > tearing but its better than it was on 9.x (and there are some other patches > I've found that might address those). > Yes! This makes X work for me too. I had gone down the rabbit hole of trying to get the drmkms to apply the workarounds for gen 8 to my gen 7 GPU in the hope that it would work - it did once but never again. I still have those work arounds applied, there are only a couple that are reported to not stick but I haven't noticed any issues yet. Suspend and resume works. Oddly, the backlight comes up at minimum brightness on resume but intel_backlight from pkgsrc sorts that. I can clean up the debug rubbish and send a diff if you are interested to try to see if that fixes the artifacts you are seeing. -- Brett Lymn -- Sent from my NetBSD device. "We are were wolves", "You mean werewolves?", "No we were wolves, now we are something else entirely", "Oh"
