SOLVED Re: build current from source amd64 error "bootxx_msdos 7840 is larger than 7680

On 2025-09-19 19:33, chytraeu wrote: I'm trying to build current from source and I get this error: bootxx_msdos 7840 is larger than 7680. I am using the following line to build: sudo ./build.sh -r -O ../obj/ -T ../tools/ -U distribution I solved this by commenting out a line in my /etc/mk.con

daily CVS update output

Updating src tree: P src/distrib/sets/lists/base32/ad.mips64eb P src/distrib/sets/lists/base32/ad.mips64el P src/distrib/sets/lists/comp/ad.arm P src/distrib/sets/lists/comp/ad.mips P src/distrib/sets/lists/comp/ad.powerpc P src/distrib/sets/lists/comp/ad.riscv P src/distrib/sets/lists/comp/md.sp

build current from source amd64 error "bootxx_msdos 7840 is larger than 7680

I'm trying to build current from source and I get this error: bootxx_msdos 7840 is larger than 7680. I am using the following line to build: sudo ./build.sh -r -O ../obj/ -T ../tools/ -U distribution

build current from source amd64 error "bootxx_msdos 7840 is larger than 7680

I'm trying to build current from source and I get this error: bootxx_msdos 7840 is larger than 7680. I am using the following line to build: sudo ./build.sh -r -O ../obj/ -T ../tools/ -U distribution

Re: 11: libssl not having NEEDED on crypto?

On Fri, Sep 19, 2025 at 11:22:15AM +0100, Greg Troxel wrote: > I'm rebuilding packages on multiple platforms for the pkgsrc freeze. > > On a domU with netbsd-11 from about August 21, erlang-fast_tls fails to > build, and the issue is linking libssl and not ending up with libcrypto: > > $ objdum

Automated report: NetBSD-current/i386 build success

The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the first successful build: 2025.09.19.19.30.17 mrg src/external/gpl3/gcc/usr.bin/backend/Makefile 1.80 2025.09.19.19.32.33 mrg src/external/gpl3/gcc/dist/libsanitizer/saniti

Re: 11: libssl not having NEEDED on crypto?

wiz: [fixed in current, submitted pullup] I see that the pullup to 11 has happened. Thanks! Robert Swindells writes: > Greg Troxel wrote: >> I'm rebuilding packages on multiple platforms for the pkgsrc freeze. >> >> On a domU with netbsd-11 from about August 21, erlang-fast_tls fails to >

Automated report: NetBSD-current/i386 build failure

This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon4.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2025.09.19.18.41.58. An extract from the build.sh output follows: --- dependall-lm_isa --- /tmp/build/2025.09.19

Re: GCC 14 in -current status: almost ready

On Fri, 19 Sep 2025 17:18:13 +1000 matthew green wrote: > i don't recommend using it yet, but if you're keen, you can try builds > with -V HAVE_GCC=14 and see what happens. I did and found one problem not mentioned in the README. I think is an mknative problem? GCC on aarch64 generates reference

Re: 11: libssl not having NEEDED on crypto?

Greg Troxel wrote: > I'm rebuilding packages on multiple platforms for the pkgsrc freeze. > > On a domU with netbsd-11 from about August 21, erlang-fast_tls fails to > build, and the issue is linking libssl and not ending up with libcrypto: Are you sure about the date? > I'd appreciate a clue

11: libssl not having NEEDED on crypto?

I'm rebuilding packages on multiple platforms for the pkgsrc freeze. On a domU with netbsd-11 from about August 21, erlang-fast_tls fails to build, and the issue is linking libssl and not ending up with libcrypto: $ objdump -x /usr/lib/libssl.so|egrep NEEDED\|RPATH NEEDED libc

GCC 14 in -current status: almost ready

hi folks. avid readers of source-changes will have notiecd GCC 14 action has been happening lately. we're at the point that amd64 works, most things may build but some platform specific issues will crop up. arm64 has a weird ctf issue and doesn't build yet. i don't recommend using it yet, but