Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-29 Thread Stuart Henderson
On 2012-01-28, Stefan Midjich  wrote:
> Also the reason I wanted to compile is something I should have stated,
> there's a kernel config online for pcengines alix boards so I wanted to use
> it on mine thinking it was better optimized for the tiny board with very
> few peripherals.
>
> https://raw.github.com/openbsd/flashboot/master/PCENGINES

That's for flashboot not for OpenBSD (flashboot is an OpenBSD derivative
but I wouldn't exactly call it OpenBSD...)

Only reason I'd consider doing this on OpenBSD is if I was really stuck
with a system running software that uses *slightly* more RAM than I have
available and I needed to stretch things short-term until the hardware
could be replaced with something suitable for the task... For everything
else I think the disadvantages outweigh the benefits.

> I wanted to do a kernel compile from the 5.0 generic system I installed on
> the CF at first, but I ran out of space before the cvs was even done.
>
> So my only option now is to find a machine that can run 5.0 i386, do the
> compile from there. Alternatively be satisified with a binary install and
> generic kernel.

Or mount /usr/src over NFS.



Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-29 Thread Stefan Midjich
Thanks David, I tried different settings for the type of VM and in the end
the random results I got seem to have been caused by my Alcor CF card
reader. Whenever that device was plugged into the vm OpenBSD would find it
very hard to boot. Sometimes hanging at mtrr, other times at fdc0.
Seemingly random sometimes.

Either way, I've got my alix router setup now and mostly thanks to the
support of the community, thank you all.

P.S. I did end up compiling my own kernel after all, I realize there was
probably no need for this. I didn't use the github link I pasted because
that config was outdated and in fact produced a kernel binary of 50MB in
size while the GENERIC one is 8MB.

So I ended up with a kernel binary of 5MB with no optimizations at all
other than removing devices I wouldn't need on an embedded board. So
clearly there's little to gain from compiling your own kernel, as the
community so gladly will remind me of.

2012/1/28 David Higgs 

> On Sat, Jan 28, 2012 at 12:42 PM, Stefan Midjich 
> wrote:
> > Thanks everyone for the info, I clearly didn't read the whole FAQ but
> only
> > the parts I needed.
> >
> > The reason I was using 4.9 was because 5.0 i386 didn't boot in vmware
> > fusion 3, it hangs at mtrr. And since I was formatting a CF card from the
> > vm I thought I had to use the same arch as the kernel that will run from
> > it, so I ended up trying on a 4.9.
>
> I do exactly the same thing: use VMWare Fusion 3 to build release(8)
> whenever there's changes to -stable that I need (otherwise I just
> install -release directly).  I've been doing this since 4.8 and have
> never had a problem using stock i386 GENERIC.  You might try changing
> the VM type to "Other" or disabling some peripheral emulation.  FWIW,
> amd64 works like a champ too using "Other 64-bit".  I haven't tried
> running i386 on "Other 64-bit".
>
> > Also the reason I wanted to compile is something I should have stated,
> > there's a kernel config online for pcengines alix boards so I wanted to
> use
> > it on mine thinking it was better optimized for the tiny board with very
> > few peripherals.
> >
> > https://raw.github.com/openbsd/flashboot/master/PCENGINES
>
> Keep reading the FAQ: http://www.openbsd.org/faq/faq5.html#Why
>
> I run i386 GENERIC on my ALIX 2D13, no custom anything required.  I
> included my dmesg below for posterity.  Everything I need fits more
> than comfortably on a 16GB CF card.
>
> I performed the initial install using the VM as well.  I gave my
> OpenBSD VM access to the CF via USB card reader, booted the VM into
> bsd.rd, did a fresh install to the CF card, added tty items to
> /etc/boot.conf, and tweaked /etc/fstab.  Then I installed the CF card
> into the ALIX board and from there just configured everything else
> over serial / network.
>
> Good luck,
>
> --david
>
> OpenBSD 5.0-stable (GENERIC) #1: Tue Nov  8 02:05:22 EST 2011
>root@vm.localdomain:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
> 586-class) 499 MHz
> cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
> real mem  = 267976704 (255MB)
> avail mem = 253542400 (241MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 11/05/08, BIOS32 rev. 0 @ 0xfd088
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: pcibios_get_intr_routing - function not supported
> pcibios0: PCI IRQ Routing information unavailable.
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xe/0xa800
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
> glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
> address 00:0d:b9:1e:60:7c
> ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
> address 00:0d:b9:1e:60:7d
> ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15,
> address 00:0d:b9:1e:60:7e
> ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
> 32-bit 3579545Hz timer, watchdog, gpio
> gpio0 at glxpcib0: 32 pins
> pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 1-sector PIO, LBA, 15296MB, 31326208 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12,
> version 1.0, legacy support
> ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "AMD EHCI root hub" 

Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread David Higgs
On Sat, Jan 28, 2012 at 12:42 PM, Stefan Midjich  wrote:
> Thanks everyone for the info, I clearly didn't read the whole FAQ but only
> the parts I needed.
>
> The reason I was using 4.9 was because 5.0 i386 didn't boot in vmware
> fusion 3, it hangs at mtrr. And since I was formatting a CF card from the
> vm I thought I had to use the same arch as the kernel that will run from
> it, so I ended up trying on a 4.9.

I do exactly the same thing: use VMWare Fusion 3 to build release(8)
whenever there's changes to -stable that I need (otherwise I just
install -release directly).  I've been doing this since 4.8 and have
never had a problem using stock i386 GENERIC.  You might try changing
the VM type to "Other" or disabling some peripheral emulation.  FWIW,
amd64 works like a champ too using "Other 64-bit".  I haven't tried
running i386 on "Other 64-bit".

> Also the reason I wanted to compile is something I should have stated,
> there's a kernel config online for pcengines alix boards so I wanted to use
> it on mine thinking it was better optimized for the tiny board with very
> few peripherals.
>
> https://raw.github.com/openbsd/flashboot/master/PCENGINES

Keep reading the FAQ: http://www.openbsd.org/faq/faq5.html#Why

I run i386 GENERIC on my ALIX 2D13, no custom anything required.  I
included my dmesg below for posterity.  Everything I need fits more
than comfortably on a 16GB CF card.

I performed the initial install using the VM as well.  I gave my
OpenBSD VM access to the CF via USB card reader, booted the VM into
bsd.rd, did a fresh install to the CF card, added tty items to
/etc/boot.conf, and tweaked /etc/fstab.  Then I installed the CF card
into the ALIX board and from there just configured everything else
over serial / network.

Good luck,

--david

OpenBSD 5.0-stable (GENERIC) #1: Tue Nov  8 02:05:22 EST 2011
root@vm.localdomain:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
586-class) 499 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem  = 267976704 (255MB)
avail mem = 253542400 (241MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/08, BIOS32 rev. 0 @ 0xfd088
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
address 00:0d:b9:1e:60:7c
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
address 00:0d:b9:1e:60:7d
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15,
address 00:0d:b9:1e:60:7e
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
32-bit 3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 1-sector PIO, LBA, 15296MB, 31326208 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12,
version 1.0, legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
mtrr: K6-family MTRR support (2 registers)
nvram: invalid checksum
ugen0 at uhub1 port 2 "American Power Conversion Back-UPS ES 750
FW:841.I3 .D USB FW:I3" rev 1.10/1.01 addr 2
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid0: 256 targets
root on wd0a (295fd65258ac0a48.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout



Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread Stefan Midjich
Thanks everyone for the info, I clearly didn't read the whole FAQ but only
the parts I needed.

The reason I was using 4.9 was because 5.0 i386 didn't boot in vmware
fusion 3, it hangs at mtrr. And since I was formatting a CF card from the
vm I thought I had to use the same arch as the kernel that will run from
it, so I ended up trying on a 4.9.

Also the reason I wanted to compile is something I should have stated,
there's a kernel config online for pcengines alix boards so I wanted to use
it on mine thinking it was better optimized for the tiny board with very
few peripherals.

https://raw.github.com/openbsd/flashboot/master/PCENGINES

I wanted to do a kernel compile from the 5.0 generic system I installed on
the CF at first, but I ran out of space before the cvs was even done.

So my only option now is to find a machine that can run 5.0 i386, do the
compile from there. Alternatively be satisified with a binary install and
generic kernel.

2012/1/28 Christer Solskogen 

> On Sat, Jan 28, 2012 at 5:25 PM, Stefan Midjich  wrote:
> > So what do I do to get 5.0 compiled?
> >
>
> You upgrade to 5.0 first.
>
> --
> chs,
>



--
Hdlsningar / Greetings

Stefan Midjich
[De omnibus dubitandum]



Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread Dave Anderson
On Sat, 28 Jan 2012, Stefan Midjich wrote:

>I have a brand spanking new 4.9 i386 system that I reinstalled with just
>base, etc, comp, man and bash, vim--no_x11, curl.
>
>Using CVSROOT=anon...@anoncvs.eu.openbsd.org:/cvs I cd /usr && cvs checkout
>-rOPENBSD_5_0 -P src; and it downloads.
>
>Then I follow the generic instructions and go to sys/arch/i386/conf; config
>GENERIC; cd ../compile/GENERIC; make clean && make depend && make and I get
>a ton of errors almost instantly. Same happens without make depend.

RTFM!  Well, RTF FAQ.  Building from source is explicitly not supported
unless the system you're building on is 'close enough' to the one you're
trying to build -- and it appears that 4.9 is not close enough to 5.0.

Install 5.0 from your CD set (you did buy one, didn't you?) then update
your source tree and try building again; this time it should work.  I'd
install all of the sets; it doesn't cost much, and there are sometimes
non-obvious dependencies.

Well, maybe.  I note that you're using bash rather than the standard
shell; this _might_ cause problems.  (I don't know enough to be sure.)

Dave

>bash-4.1# make clean && make depend && make
>rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s  [Ee]rrs linterrs assym.h
>cat ../../../../arch/i386/i386/genassym.cf ../../../../arch/i386/i386/
>genassym.cf |  sh ../../../../kern/genassym.sh cc  -Werror -Wall
>-Wstrict-prototypes -Wmi
>ssing-prototypes  -Wno-main -Wno-uninitialized -Wno-format
> -Wstack-larger-than-2047  -fno-builtin-printf -fno-builtin-snprintf
> -fno-builtin-vsnprintf -fno-bu
>iltin-log  -fno-builtin-log2 -fno-builtin-malloc -O2 -pipe -nostdinc -I.
>-I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING
>-DKMEMSTATS
>-DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK
>-DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
>-DPPP_BSDCOMP -DPPP_DEFLA
>TE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF -DKVM86 -DUSER_LDT
>-DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
>-DCOMCONSOLE -DCONSPEED="0
>x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE -DUSBVERBOSE
>-DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
>-DWSDISPLAY_DEFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT
>-DMAXUSERS=32 -D_KERNEL -MD -MP -MF assym.P > assym.h.tmp
>sed '1s/.*/assym.h: \\/' assym.P > assym.d
>sort -u assym.h.tmp > assym.h
>cc -D_LOCORE -x assembler-with-cpp  -fno-builtin-printf
>-fno-builtin-snprintf  -fno-builtin-vsnprintf -fno-builtin-log
> -fno-builtin-log2 -fno-builtin-malloc -
>nostdinc -I. -I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE
>-DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
>-DFFS -DMFS
>-DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
>-DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF
>-DKVM86 -DU
>SER_LDT -DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
>-DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE
>-DUSBVERBOSE -DWSD
>ISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
>-DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP -c
>../../../../arch/i386/i38
>6/locore.s
>cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
>-Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
> -fno-builtin-printf -fno-builti
>n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
>-fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
>-I../../../../arch -DDDB -DDIA
>GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
>-DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
>-DINET -DALTQ
> -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
>-DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
>-DMINIROOTSIZE="0x18000"
> -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
>-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
>-DWSDISPLAY_D
>EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
> -c param.c
>cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
>-Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
> -fno-builtin-printf -fno-builti
>n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
>-fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
>-I../../../../arch -DDDB -DDIA
>GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
>-DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
>-DINET -DALTQ
> -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
>-DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
>-DMINIROOTSIZE="0x18000"
> -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
>-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
>-DWSDISPLAY_D
>EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
> -c ioconf.c
>cc1: 

Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread Christer Solskogen
On Sat, Jan 28, 2012 at 5:25 PM, Stefan Midjich  wrote:
> So what do I do to get 5.0 compiled?
>

You upgrade to 5.0 first.

-- 
chs,



Re: 5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread Matthieu Herrb
On Sat, Jan 28, 2012 at 05:25:53PM +0100, Stefan Midjich wrote:
> I have a brand spanking new 4.9 i386 system that I reinstalled with just
> base, etc, comp, man and bash, vim--no_x11, curl.
> 

you need to update config(8) to the 5.0 version first.

> Using CVSROOT=anon...@anoncvs.eu.openbsd.org:/cvs I cd /usr && cvs checkout
> -rOPENBSD_5_0 -P src; and it downloads.
> 
> Then I follow the generic instructions and go to sys/arch/i386/conf; config
> GENERIC; cd ../compile/GENERIC; make clean && make depend && make and I get
> a ton of errors almost instantly. Same happens without make depend.
> 
> bash-4.1# make clean && make depend && make
> rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s  [Ee]rrs linterrs assym.h
> cat ../../../../arch/i386/i386/genassym.cf ../../../../arch/i386/i386/
> genassym.cf |  sh ../../../../kern/genassym.sh cc  -Werror -Wall
> -Wstrict-prototypes -Wmi
> ssing-prototypes  -Wno-main -Wno-uninitialized -Wno-format
>  -Wstack-larger-than-2047  -fno-builtin-printf -fno-builtin-snprintf
>  -fno-builtin-vsnprintf -fno-bu
> iltin-log  -fno-builtin-log2 -fno-builtin-malloc -O2 -pipe -nostdinc -I.
> -I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING
> -DKMEMSTATS
> -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK
> -DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
> -DPPP_BSDCOMP -DPPP_DEFLA
> TE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF -DKVM86 -DUSER_LDT
> -DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
> -DCOMCONSOLE -DCONSPEED="0
> x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE -DUSBVERBOSE
> -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
> -DWSDISPLAY_DEFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT
> -DMAXUSERS=32 -D_KERNEL -MD -MP -MF assym.P > assym.h.tmp
> sed '1s/.*/assym.h: \\/' assym.P > assym.d
> sort -u assym.h.tmp > assym.h
> cc -D_LOCORE -x assembler-with-cpp  -fno-builtin-printf
> -fno-builtin-snprintf  -fno-builtin-vsnprintf -fno-builtin-log
>  -fno-builtin-log2 -fno-builtin-malloc -
> nostdinc -I. -I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE
> -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
> -DFFS -DMFS
> -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
> -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF
> -DKVM86 -DU
> SER_LDT -DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
> -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE
> -DUSBVERBOSE -DWSD
> ISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
> -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP -c
> ../../../../arch/i386/i38
> 6/locore.s
> cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
> -Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
>  -fno-builtin-printf -fno-builti
> n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
> -fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
> -I../../../../arch -DDDB -DDIA
> GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
> -DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
> -DINET -DALTQ
>  -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
> -DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
> -DMINIROOTSIZE="0x18000"
>  -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
> -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
> -DWSDISPLAY_D
> EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
>  -c param.c
> cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
> -Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
>  -fno-builtin-printf -fno-builti
> n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
> -fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
> -I../../../../arch -DDDB -DDIA
> GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
> -DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
> -DINET -DALTQ
>  -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
> -DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
> -DMINIROOTSIZE="0x18000"
>  -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
> -DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
> -DWSDISPLAY_D
> EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
>  -c ioconf.c
> cc1: warnings being treated as errors
> ioconf.c:218: warning: excess elements in struct initializer
> ioconf.c:218: warning: (near initialization for 'cfdata[0]')
> ioconf.c:220: warning: excess elements in struct initializer
> ioconf.c:220: warning: (near initialization for 'cfdata[1]')
> ioconf.c:222: warning: excess elements in struct initializer
> ioconf.c:222: warning: (near initialization for 'cfdata[2]')
> ioconf.c:224: warning: excess elements 

5.0 kernel won't compile on 4.9 i386 system

2012-01-28 Thread Stefan Midjich
I have a brand spanking new 4.9 i386 system that I reinstalled with just
base, etc, comp, man and bash, vim--no_x11, curl.

Using CVSROOT=anon...@anoncvs.eu.openbsd.org:/cvs I cd /usr && cvs checkout
-rOPENBSD_5_0 -P src; and it downloads.

Then I follow the generic instructions and go to sys/arch/i386/conf; config
GENERIC; cd ../compile/GENERIC; make clean && make depend && make and I get
a ton of errors almost instantly. Same happens without make depend.

bash-4.1# make clean && make depend && make
rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s  [Ee]rrs linterrs assym.h
cat ../../../../arch/i386/i386/genassym.cf ../../../../arch/i386/i386/
genassym.cf |  sh ../../../../kern/genassym.sh cc  -Werror -Wall
-Wstrict-prototypes -Wmi
ssing-prototypes  -Wno-main -Wno-uninitialized -Wno-format
 -Wstack-larger-than-2047  -fno-builtin-printf -fno-builtin-snprintf
 -fno-builtin-vsnprintf -fno-bu
iltin-log  -fno-builtin-log2 -fno-builtin-malloc -O2 -pipe -nostdinc -I.
-I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE -DACCOUNTING
-DKMEMSTATS
-DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK
-DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
-DPPP_BSDCOMP -DPPP_DEFLA
TE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF -DKVM86 -DUSER_LDT
-DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
-DCOMCONSOLE -DCONSPEED="0
x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE -DUSBVERBOSE
-DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
-DWSDISPLAY_DEFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT
-DMAXUSERS=32 -D_KERNEL -MD -MP -MF assym.P > assym.h.tmp
sed '1s/.*/assym.h: \\/' assym.P > assym.d
sort -u assym.h.tmp > assym.h
cc -D_LOCORE -x assembler-with-cpp  -fno-builtin-printf
-fno-builtin-snprintf  -fno-builtin-vsnprintf -fno-builtin-log
 -fno-builtin-log2 -fno-builtin-malloc -
nostdinc -I. -I../../../.. -I../../../../arch -DDDB -DDIAGNOSTIC -DKTRACE
-DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM -DSYSVSHM
-DFFS -DMFS
-DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO -DINET -DALTQ -DINET6 -DIPSEC
-DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG -DUSER_PCICONF
-DKVM86 -DU
SER_LDT -DPROCFS -DRAMDISK_HOOKS -DMINIROOTSIZE="0x18000" -DNKPTP="0x10"
-DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1" -DPCIVERBOSE
-DUSBVERBOSE -DWSD
ISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6"
-DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP -c
../../../../arch/i386/i38
6/locore.s
cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
-Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
 -fno-builtin-printf -fno-builti
n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
-fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
-I../../../../arch -DDDB -DDIA
GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
-DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
-DINET -DALTQ
 -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
-DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
-DMINIROOTSIZE="0x18000"
 -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
-DWSDISPLAY_D
EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
 -c param.c
cc  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -Wno-main
-Wno-uninitialized -Wno-format  -Wstack-larger-than-2047
 -fno-builtin-printf -fno-builti
n-snprintf  -fno-builtin-vsnprintf -fno-builtin-log  -fno-builtin-log2
-fno-builtin-malloc -O2 -pipe -nostdinc -I. -I../../../..
-I../../../../arch -DDDB -DDIA
GNOSTIC -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG
-DSYSVSEM -DSYSVSHM -DFFS -DMFS -DTCP_SACK -DTCP_ECN -DTCP_SIGNATURE -DFIFO
-DINET -DALTQ
 -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE -DMROUTING -DPIM -DBOOT_CONFIG
-DUSER_PCICONF -DKVM86 -DUSER_LDT -DPROCFS -DRAMDISK_HOOKS
-DMINIROOTSIZE="0x18000"
 -DNKPTP="0x10" -DCOMCONSOLE -DCONSPEED="0x9600" -DBUFCACHEPERCENT="1"
-DPCIVERBOSE -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD
-DWSDISPLAY_D
EFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DMAXUSERS=32 -D_KERNEL -MD -MP
 -c ioconf.c
cc1: warnings being treated as errors
ioconf.c:218: warning: excess elements in struct initializer
ioconf.c:218: warning: (near initialization for 'cfdata[0]')
ioconf.c:220: warning: excess elements in struct initializer
ioconf.c:220: warning: (near initialization for 'cfdata[1]')
ioconf.c:222: warning: excess elements in struct initializer
ioconf.c:222: warning: (near initialization for 'cfdata[2]')
ioconf.c:224: warning: excess elements in struct initializer
ioconf.c:224: warning: (near initialization for 'cfdata[3]')
ioconf.c:226: warning: excess elements in struct initializer
ioconf.c:226: warning: (near initialization for 'cfdata[4]')
ioconf.c:228: warning: excess elements in struct initializer
ioconf.c:228: warning: (near initiali