On Tue, Oct 18, 2005 at 12:04:09PM +0200, Quentin Garnier wrote:
> On Tue, Oct 18, 2005 at 11:58:14AM +0200, Jaka Jejcic wrote:
> > On Tue, Oct 18, 2005 at 11:43:06AM +0200, Quentin Garnier wrote:
> > > On Tue, Oct 18, 2005 at 11:38:28AM +0200, Jaka Jejcic wrote:
> > > > Maybe you will all find this ridiculous but I find myself
> > > > adding '= 0' or '= NULL' to many of the files and many of
> > > > the variables each time I build the source tree just to
> > > > get it compiled, because the build fails for uninitialized vars.
> > > > 
> > > > Am I doing something wrong? If not, why aren't those vars set to
> > > > some appropriate value?
> > > 
> > > You'd better give a precise example.  And are you adding -W flags to
> > > the build?
> > 
> > example:
> > ./build.sh -T /usr/build/alpha/tools -M /usr/build/alpha/obj -D /usr/build/alpha/dist -R /usr/build/alpha/release -m alpha release
> > 
> > it doesn't matter which arch i build for
> > 
> > mk.conf:
> > COPTS +=	-pipe -O
> > MKNLS =         yes
> > OBJMACHINE =    yes
> > MKOBJDIRS =     yes
> > MKHOSTOBJ =     yes
> > UPDATE =        no
> > BUILD =         yes
> > X11SRCDIR =     /usr/xsrc
> > X11_TYPE =      native
> > 
> > well that's it...
> 
> I meant an example of the error you get.  What's the version of the
> source tree, etc.

sources checked out yesterday, but i have this problem for at least a year or
so. examples of files and lines with uninitialized vars: (taken from different
arch builds - since not all files are used in all builds)

/usr/src/dist/ntp/libntp/ieee754io.c:386
/usr/src/sys/compat/osf1/osf1_misc.c:306
/usr/src/sys/arch/hp700/dev/sti_sgc.c:135

and the list goes on...