DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 28th January 2012
nocturnal nocturnal is offline
New User
 
Join Date: Oct 2011
Posts: 6
Thanked 0 Times in 0 Posts
Default Compiler warning halting make of 5.0 kernel on 4.9 i386 system

I have a pretty vanilla 4.9 i386 system that I've even reinstalled a couple of times to combat this issue, but to no avail. It's installed with base, etc, man, comp and packages bash, vim--no_x11, curl.

I follow generic instructions by fetching source code into /usr/src.

Code:
export CVSROOT=anoncvs@anoncvs.eu.openbsd.org:/cvs
cd /usr
cvs checkout -rOPENBSD_5_0 -P src
cd src/sys/arch/i386/conf
config GENERIC
cd ../compile/GENERIC
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 initialization for 'cfdata[5]')
ioconf.c:230: warning: excess elements in struct initializer
ioconf.c:230: warning: (near initialization for 'cfdata[6]')
ioconf.c:232: warning: excess elements in struct initializer
ioconf.c:232: warning: (near initialization for 'cfdata[7]')
ioconf.c:234: warning: excess elements in struct initializer
ioconf.c:234: warning: (near initialization for 'cfdata[8]')
And the last error goes on for 68 times before make exits. I must be missing something because this is happening on fresh systems with unpolluted source trees. I've also tried without the make depend since that's what the docs do, same issue.

I've found some list posts describing the same issue but none had a solution for my situation, one discussion just ended with no resolution posted.
Reply With Quote
  #2   (View Single Post)  
Old 28th January 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,879
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by nocturnal View Post
I have a pretty vanilla 4.9 i386 system...
...
Code:
export CVSROOT=anoncvs@anoncvs.eu.openbsd.org:/cvs
cd /usr
cvs checkout -rOPENBSD_5_0 -P src
...
It appears you are attempting to compile OpenBSD 5.0-stable on a 4.9 system. This is not supported.

While you have OpenBSD 4.9 (& I am assuming 4.9-release...) installed, the only supported choices you have in downloading source is to either choose:
  • OpenBSD 4.9-release which is designated by the CVS OPENBSD_4_9_BASE tag.
  • OpenBSD 4.9-stable which is specified by the OPENBSD_4_9 tag.
If you are wanting to upgrade from 4.9 to 5.0, study the transition table shown in Section 5.3.2 of the FAQ. You will also want to study the Upgrade Guide going from 4.9 to 5.0 too.
Reply With Quote
  #3   (View Single Post)  
Old 28th January 2012
nocturnal nocturnal is offline
New User
 
Join Date: Oct 2011
Posts: 6
Thanked 0 Times in 0 Posts
Default

Thanks, this was very good to know.

I am forced to use VirtualBox instead to compile the 5.0 kernel I wanted because vmware fusion 3 would not boot the 5.0 i386 system.
Reply With Quote
  #4   (View Single Post)  
Old 28th January 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,879
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by nocturnal View Post
I am forced to use VirtualBox instead to compile the 5.0 kernel...
I see you have made the exact same post on misc@, & have gotten similar answers. Until you can install 5.0, you will not be able to compile the 5.0 kernel.

If you were having installation problems with 5.0-release, describing the issues may allow us to suggest an alternative. Updating to 5.0 may be an alternative, & this path is supported.
Reply With Quote
  #5   (View Single Post)  
Old 28th January 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,879
Thanked 190 Times in 160 Posts
Default

Having seen your latest post to misc@, if you are wanting to install OpenBSD 5.0 on a CF card to be inserted into an Alix system, it will be far simpler to set up a PXE & TFTP server, & boot the Alix system from it.

The PXE/TFTP server can be running OpenBSD 4.9 while hosting the 5.0 bsd.rd installation kernel. This information is described in Section 6.10 of the FAQ.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenBSD 4.6 i386 boot hangs with old gateway system - resolved comet--berkeley OpenBSD Installation and Upgrading 6 22nd July 2011 08:15 AM
Ninja, a replacement for make, in Chrome's build system J65nko News 7 14th February 2011 04:14 AM
FreeBSD 8.0-RELEASE as DomU(hvm; i386): kernel panic deadeyes FreeBSD Installation and Upgrading 6 5th January 2010 09:55 PM
FreeBSD 7 i386, PAE and kernel modules eztiger FreeBSD Installation and Upgrading 7 1st April 2009 06:07 PM
I386 ELF32 binary on AMD64 system can't find shared libraries Gemini FreeBSD General 0 9th December 2008 06:49 AM


All times are GMT. The time now is 02:28 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick