The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2018.04.04.06.30.09 msaitoh src/sys/dev/pci/ixgbe/ixgbe.c,v 1.143
2018.04.04.06.30.09 msaitoh src/sys/dev/pci/ixgbe/ixgbe_x550.c,v 1.11
Log files can be
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2018.04.04.15.08.59.
An extract from the build.sh output follows:
--- postinstall-fix-obsolete_stand ---
===
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2018.04.04.15.53.04 kamil src/tests/usr.bin/c++/Makefile,v 1.6
2018.04.04.16.01.05 bouyer src/sys/arch/arm/sunxi/sunxi_tcon.c,v 1.4
2018.04.04.16.23.
> On 01.04.2018 16:53, Havard Eidnes wrote:
>> And some of the internal functions in libexecinfo are apparently
>> static, so not present in the symbol table for display in the
>> debugger, making debugging all that much harder.
>>
>> Sigh!
>>
>> Hints, anyone?
>
> There is an internal LLVM suppo
On 05.04.2018 00:55, Havard Eidnes wrote:
> Hm, I am suspecting that nobody has actually tested whether
> backtrace() really works on NetBSD/powerpc... I'll write a
> simple test of that in C tomorrow.
>
Yes, this looks more like dysfunctional backtrace(3).
We have got an ATF test for this:
Updating src tree:
P src/crypto/external/bsd/netpgp/dist/src/lib/libnetpgp.3
P src/crypto/external/bsd/netpgp/dist/src/libbn/libnetpgpbn.3
P src/crypto/external/bsd/netpgp/dist/src/libmj/libmj.3
P src/crypto/external/bsd/netpgp/dist/src/netpgpverify/netpgpverify.1
P src/distrib/sets/lists/comp/mi
