Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!sun-barr!cs.utexas.edu!uunet!mcsun!sun4nl!tuegate.tue.nl!blade.stack.urc.tue.nl!jim
From: jim@blade.stack.urc.tue.nl (Jim Rump)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Gcc 2.3.1 & kernel -> SUCCESS/2
Message-ID: <6344@tuegate.tue.nl>
Date: 18 Nov 92 07:35:27 GMT
References: <1992Nov16.134717.22679@dde.dk>
Sender: root@tuegate.tue.nl
Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
Lines: 44
X-Newsreader: TIN [version 1.1 PL6]
Kim Andersen (kim@dde.dk) wrote:
: I would like to report a partial success with using gcc-2.3.1 for kernel
: compiling.
:
: I had to do the following in order to be able to link/boot this new kernel:
:
: compile init_main.c with gcc-1.39, otherwise the link stage would fail with
: symbol error for "___main".
:
: compile machdep.c with gcc-1.39, otherwise the kernel will enter a endless
: reboot loop.
: (This has to do with some differences in packing between 1.39 & 2.3.1 )
:
: compile pccons_{vga,out,kbd} with gcc-1.39, else multiply defined symbols.
: (This is really weird.)
:
: My machine have been running this kernel since saturday night, with "only"
: 2 crashes/hangs.
: The hanging is seen when running a gcc-1.39 kernel, probably has something to
: do with swapping.
: The crash happens when running the byte-benchmarks (4 concurrents shells),
: and gives a "vm_fault(blah....) trap code 12".
: It also happens when using a gcc-1.39 compiled kernel.
:
: I haven't tried comparing the performance using the different kernels.
: .
:
: kim
: --
: --
: Kim Andersen @ Dansk Data Elektronik A/S, Herlev, Denmark.
: E-mail: kim@dde.dk or ...!uunet!mcsun!dkuug!dde!kim
Hi,
I too had succes compiling the kernel with gcc-2.3.1.
No crashes and no other behavior than I'm used too.
JIm
--
\_ \_ \_\_ \_ \_ Jim@stack.urc.tue.nl
\_ \_ \_ \_ \_
\_ \_ \_ \_
\_\_ \_ \_ \_ I,m always seeing an opinion.