daily CVS update output
Updating src tree: P src/distrib/sets/lists/xserver/md.bebox P src/distrib/sets/lists/xserver/md.cats P src/doc/TODO.modules P src/sbin/fsdb/fsdb.8 P src/sbin/fsdb/fsdb.c P src/share/mk/bsd.own.mk P src/sys/arch/amd64/conf/GENERIC P src/sys/arch/i386/conf/GENERIC P src/sys/arch/vax/conf/GENERIC P src/sys/arch/vax/conf/VAX780 P src/sys/compat/common/Makefile P src/sys/dev/sbus/mgx.c P src/sys/kern/vfs_bio.c P src/sys/netinet/in.c P src/sys/ufs/lfs/ulfs_vnops.c P src/usr.bin/gzip/gzip.1 P src/usr.bin/gzip/gzip.c P src/usr.bin/gzip/unbzip2.c P src/usr.bin/gzip/unpack.c P src/usr.bin/gzip/unxz.c P src/usr.sbin/acpitools/acpidump/acpi.c P src/usr.sbin/acpitools/acpidump/acpi_user.c P src/usr.sbin/acpitools/acpidump/acpidump.8 P src/usr.sbin/acpitools/acpidump/acpidump.c P src/usr.sbin/acpitools/acpidump/acpidump.h Updating xsrc tree: Killing core files: Updating tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory) pax: WARNING! These file names were not selected: src/gnu done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting... replacing... done src/config: collecting... replacing... done src: collecting... replacing... done xsrc/top-level: collecting... replacing... done xsrc/external: collecting... replacing... done xsrc/local: collecting... replacing... done xsrc: collecting... replacing... done Updating release-6 src tree (netbsd-6): Updating release-6 xsrc tree (netbsd-6): Updating release-6 tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting... replacing... done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting... replacing... done src/config: collecting... replacing... done src/x11: collecting... replacing... done xsrc/top-level: collecting... replacing... done xsrc/external: collecting... replacing... done xsrc/local: collecting... replacing... done xsrc/xfree: collecting... replacing... done Updating release-7 src tree (netbsd-7): Updating release-7 xsrc tree (netbsd-7): Updating release-7 tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting... replacing... done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting...
Re: cross-compiling kernel
On Fri, Aug 04, 2017 at 14:18:36 +0200, Riccardo Mottola wrote:
> Is building an x86 a "full cross compile"? I suppose yes and I
> followef the NetBSD build for sparc, just with x86.
Yes, it's full cross compilation.
> I want to use the standard kernel GENERIC, thus I did:
>
> ./build.sh -U -m i386 -u tools
>
> I don't get a full x86 toolchain though, in /usr/obj I find:
> $ ls /usr/obj/
> sys tools
> tooldir.NetBSD-8.99.1-amd64
>
> I expected instead something like:
> /usr/obj/tooldir.NetBSD-8.99.1-i386
[...]
> ===> TOOLDIR path: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64
[...]
> so it is expected apparently.
TOOLDIR defaults to tooldir.${host_ostype}, so it reflects your os.
> although I find inside multiple binaries, e.g. :
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-amd64
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386
>
> I thus tried:
> $ /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386 depend
>
> but this fails:
> /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbgenassym:
> /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-gcc: not found
>
> I have several i486 tools, but not all:
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-dbsym
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-fdisk
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-install
> /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-mdsetimage
This is strange. Anything in your /etc/mk.conf or environment? You
can look at the /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386
make wrapper script and check what does it set TOOLDIR too.
-uwe
Using NET_MPSAFE
hello. I'm excited to see the development of the MP-safe network stack in NetBSD. Now that some progress has been made in that regard and there are MP-safe drivers and stack components to use, I have some questions. I'm interested in using options NET_MPSAFE in NetBSD-8.0_BETA and the eventual netbsd-8 release. Here are my questions. I apologize if some of them seem obvious, but I don't want to make any assumptions when trying this new stuff. 1. If I enable NET_MPSAFE in the kernel, will non-MP-ify'd components work in that kernel using the kernel lock? In other words, if I enable NET_MPSAFE and use the wm(4) driver, I'll get MP performance out of the network stack. However, what if I try to use a non-MP-ify'd component on that same machine, i.e. agr(4) or pf(4)? It looks to me like things should work, but traffic through the non-MP-ify'd components will be single threaded. Is this correct? 2. Am I correct that when NET_MPSAFE is turned on, the network stack is runing as an LWP inside the kernel? And, am I correct that this means that even if a particular network component is single-threaded, it's able to execute on any CPU, thus reducing CPU congestion on CPU0 as happens on the stock NetBSD kernels? 3. How stable is the NET_MPSAFE stack? Is anyone using it in any sort of production environment? the BSDCAN paper I read suggests it's pretty stable, but I'm wondering if anyone can report their experience. -thanks -Brian
Re: cross-compiling kernel
Hi, co...@sdf.org wrote: ./build.sh -U -u -m i386 kernel=CONFNAME doesn't work? no it doesn't work: it fails with the same issue of nbmake-i386 depend: it wants an i486 gcc! Should I have it? should it have been built by the official amd64 tools or the i386 tools I tried to build? disc$ ./build.sh -U -u -m i386 kernel=GENERIC ===> build.sh command:./build.sh -U -u -m i386 kernel=GENERIC ===> build.sh started:Fri Aug 4 19:42:34 CEST 2017 ===> NetBSD version: 8.99.1 ===> MACHINE: i386 ===> MACHINE_ARCH:i386 ===> Build platform: NetBSD 8.99.1 amd64 ===> HOST_SH: /bin/sh ===> MAKECONF file: /etc/mk.conf #objdir /usr/obj/ ===> TOOLDIR path: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64 ===> DESTDIR path:/usr/src/obj/destdir.i386 ===> RELEASEDIR path: /usr/src/obj/releasedir ===> Updated makewrapper: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386 ===> Building kernel without building new tools #objdir /usr/obj/sys/arch/i386/compile ===> Building kernel: GENERIC ===> Build directory: /usr/src/sys/arch/i386/compile/obj/GENERIC Build directory is /usr/src/sys/arch/i386/compile/obj/GENERIC Don't forget to run "make depend" depending the kern library objects #create kern/__main.d CC=/usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-gcc /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmkdep -f __main.d.tmp -- -std=gnu99 --sysroot=/usr/src/obj/destdir.i386 -I/usr/src/sys/lib/libkern/arch/i386 --sysroot=/usr/src/obj/destdir.i386 -Di386 -I../../. -I/usr/src/sys/external/bsd/acpica/dist -I/usr/src/sys/../common/lib/libx86emu -I/usr/src/sys/../common/include -I/usr/src/sys/arch -I/usr/src/sys -nostdinc -DDIAGNOSTIC -D_KERNEL -D_KERNEL_OPT -std=gnu99 -I/usr/src/sys/lib/libkern/../../../common/lib/libc/quad -I/usr/src/sys/lib/libkern/../../../common/lib/libc/string -I/usr/src/sys/lib/libkern/../../../common/lib/libc/arch/i386/string -D_FORTIFY_SOURCE=2 -I/usr/src/sys/external/bsd/ipf -I/usr/src/sys/external/isc/atheros_hal/dist -I/usr/src/sys/external/isc/atheros_hal/ic -I/usr/src/sys/external/bsd/common/include -I/usr/src/sys/external/bsd/drm2/include -I/usr/src/sys/external/bsd/common/include -I/usr/src/sys/external/bsd/drm2/include -I/usr/src/sys/external/bsd/drm2/include/drm -I/usr/src/sys/external/bsd/drm2/dist -I/usr/src/sys/external/bsd/drm2/dist/include -I/usr/src/sys/external/bsd/drm2/dist/include/drm -I/usr/src/sys/external/bsd/drm2/dist/uapi -I/usr/src/sys/external/bsd/common/include -D__KERNEL__ -DCONFIG_FB=0 -DCONFIG_BACKLIGHT_CLASS_DEVICE=0 -DCONFIG_BACKLIGHT_CLASS_DEVICE_MODULE=0 -I/usr/src/sys/../common/include -DCONFIG_AGP -I/usr/src/sys/external/bsd/drm2/dist/drm/i915 -I/usr/src/sys/external/bsd/drm2/i915drm -DCONFIG_DRM_I915_FBDEV=1 -DCONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT=0 -I/usr/src/sys/external/bsd/drm2/dist/drm/radeon -I/usr/src/sys/external/bsd/drm2/include/radeon -I/usr/src/sys/external/bsd/drm2/radeon -I/usr/src/sys/external/bsd/drm2/dist/drm/nouveau -I/usr/src/sys/external/bsd/drm2/dist/drm/nouveau/core -I/usr/src/sys/external/bsd/drm2/dist/drm/nouveau/core/include -I/usr/src/sys/external/bsd/drm2/nouveau -DCONFIG_NOUVEAU_DEBUG=5 -DCONFIG_NOUVEAU_DEBUG_DEFAULT=3 -I/usr/src/sys/external/bsd/acpica/dist/include -I/usr/src/sys/lib/libkern/../../../common/lib/libc/quad -I/usr/src/sys/lib/libkern/../../../common/lib/libc/string -I/usr/src/sys/lib/libkern/../../../common/lib/libc/arch/i386/string -I/usr/src/sys/lib/libkern/../../../common/include /usr/src/sys/lib/libkern/__main.c && mv __main.d.tmp __main.d nbmkdep: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-gcc: not found: No such file or directory
Re: cross-compiling kernel
./build.sh -U -u -m i386 kernel=CONFNAME doesn't work?
cross-compiling kernel
Hi all, I want to build an x86 kernel on my faster amd64 machine, also to share and test the same patches prepared by Maya for the ACPI sleep problems on another laptop where actually I use "release 7.1" To build the "native" kernel I used: ./build.sh -U -u tools ./build kernel=CONFNAME Is building an x86 a "full cross compile" ? I suppose yes and I followef the NetBSD build for sparc, just with x86. I want to use the standard kernel GENERIC, thus I did: ./build.sh -U -m i386 -u tools I don't get a full x86 toolchain though, in /usr/obj I find: $ ls /usr/obj/ sys tools tooldir.NetBSD-8.99.1-amd64 I expected instead something like: /usr/obj/tooldir.NetBSD-8.99.1-i386 build.sh says: ===> build.sh command:./build.sh -U -m i386 -u tools ===> build.sh started:Fri Aug 4 14:11:18 CEST 2017 ===> NetBSD version: 8.99.1 ===> MACHINE: i386 ===> MACHINE_ARCH:i386 ===> Build platform: NetBSD 8.99.1 amd64 ===> HOST_SH: /bin/sh ===> MAKECONF file: /etc/mk.conf #objdir /usr/obj/ ===> TOOLDIR path: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64 ===> DESTDIR path:/usr/src/obj/destdir.i386 ===> RELEASEDIR path: /usr/src/obj/releasedir ===> Updated makewrapper: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386 so it is expected apparently. although I find inside multiple binaries, e.g. : /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-amd64 /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386 I thus tried: $ /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbmake-i386 depend but this fails: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/nbgenassym: /usr/src/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-gcc: not found I have several i486 tools, but not all: /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-dbsym /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-fdisk /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-install /usr/obj/tooldir.NetBSD-8.99.1-amd64/bin/i486--netbsdelf-mdsetimage Where am I doing something wrong? Riccardo
UEFI status? (was Re: GPT/UEFI booting)
Hi, all. A few days ago, I successfully booted from UP board. http://www.up-board.org/up/comparison-up-versus-edisongalileo-joule/ UP board's UEFI doesn't support legacy boot. Currently, our sysinst doesn't support creating UEFI bootable disk, so I tried creating disk with reading the first mail of this thread. I couldn't make bootable disk, too. But, I've noticed the info from doing "gpt show -a sd0" on a disk which contains images/NetBSD-8.xx.y-1-amd64-uefi-install.img. A bootable image has a attribute "bootme": uefi# gpt show -a sd0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 65536 1 GPT part - EFI System Type: efi TypeID: c12a7328-f81f-11d2-ba4b-00a0c93ec93b GUID: 64a9158f-099d-442d-9ae4-ddbb6b604114 Size: 32768 K Label: EFI System Attributes: None 65570 122486717 2 GPT part - NetBSD FFSv1/FFSv2 Type: ffs TypeID: 49f48d5a-b10e-11dc-b99b-0019d1879648 GUID: 63313eee-af70-4e00-90a1-e0443c02ce4d Size: 59808 M Label: amd64-current Attributes: bootme < This! 122552287 32 Sec GPT table 122552319 1 Sec GPT header so, This is what I’ve done so far: # # Create the GPT segments # gpt create -f ld0 gpt add -s 65536 -t efi -l "EFI System" ld0 gpt add -s 525168 -t ffs -l "NetBSD-root" ld0 "gpt set -a bootme -i N(parpahs 2) xx0" is required. gpt add -s 256000 -t swap -l "NetBSD-swap" ld0 gpt add -s 1024000 -t ffs -l "NetBSD-var" ld0 gpt add -s 16264934 -t ffs -l "NetBSD-usr" ld0 gpt add -t ffs -l "NetBSD-home” # # Initialize the wedges # To inform this flag, I modified gpt.8 yesterday (and thanks kre@ fixing typo!) After setup my environment, I've noticed that neither acpidump and nor pkgsrc/dmidecode didn't work. The reason is that those information are not near the beginning of the physical address on UEFI environment. For acpidump, the problem was fixed. Not yet for pkgsrc/dmidecode. I've not used grub2. If someone(TM) succeeded booting with grub2, it would be good to summarize the howto. Making sysinst UEFI friendly is important. Could someone do by 8.0-RELEASE? -- --- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)
