Subject: Re: Re: Re: Re: "overlaps section .rodata" on kernel build
To: Joel CARNAT <joel@carnat.net>
From: Andrey Petrov <petrov@netbsd.org>
List: port-sparc64
Date: 01/08/2005 16:52:28
On Sat, Jan 08, 2005 at 11:09:07PM +0100, Joel CARNAT wrote:
> On Sat, Jan 08 2005 - 13:54, Andrey Petrov wrote:
> > On Sat, Jan 08, 2005 at 10:33:20PM +0100, Joel CARNAT wrote:
> > > right, so I commented out a lots of things (thX sysutils/adjustkernel ;) and 
> > > the kernel compiled till the end !
> > > 
> > > what looks strange is that the kernel is 5.6M... the same size as GENERIC...
> > > 
> > 
> > File size doesn't mean much, you need to use size(1) or objdump(1). Also
> 
>  ah ? I thought having code (or not) for devices would make it bigger (or smaller),
>  especially when everything is inside the kernel.
> 

Not sure I follow. Try 'size netbsd' on both kernels and you should see difference.

> > I would not set commonly used definitions as CFLAGS and friends in mk.conf,
> > they just have too global impact. For kernel build look at sys/conf/Makefile.kern.inc
> > and set specificly what you need. I also don't see a reason not to use compiler
> > optimisation.
> > 
> 
>  hum... I don't really know... after a few testings I discovered that stilling linux/gentoo
>  optimization flags just made buggy netbsd binaries, so I used "Benedikt Meurer's NetBSD tips & tricks"
>  to delete any optimization.
> 

It was true for older 2.95.x version of compiler, since gcc3.3 was integrated the
situation was changed dramitically especially for sparc64. You can use optimisation
now.

	Andrey