nabled
> How about #include_next "..."?
I read https://gcc.gnu.org/onlinedocs/cpp/Wrapper-Headers.html .
"The use #include_next can lead to great confusion.
We recommend it be used only when there is no other alternative."
--
Jun Ebihara
to the directory with netbsd.ub.
"/usr/src/sys/external/gpl2/dts/dist/arch/arm/boot/dts/sun8i-h3-orangepi-one.dts"
... original configration.
+
"/usr/src/sys/arch/arm/dts/sun8i-h3-orangepi-one.dts" .. config for NetBSD
+
"/usr/src/sys/arch/arm/dts/sun8i-h3.dtsi" ... framebuffer enabled
--
Jun Ebihara
231620Z-obj/home/source/ab/HEAD/src/sys/arch/evbarm/compile/RPI
evbarm
rpi-white# pkg_info
assertion "pthread__tsd_destructors[key] != NULL" failed: file
"/home/source/ab/HEAD/src/lib/libpthread/pthread_tsd.c", line 179, function
"pthread__add_specific"
[1] Abort trap (core dumped) pkg_info
--
Jun Ebihara
ro770 -X -M 512 hpcmipskernel/netbsd20091130 ... boot OK
gxemul -e mobilepro770 -X -M 512 hpcmipskernel/netbsd20091231 ... boot FAIL
see more information;
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=42934
--
jun ebihara
