Date: Thu, 21 Sep 2006 18:29:52 -0700 (PDT) From: backyard <backyard1454-bsd@yahoo.com> To: freebsd-questions@freebsd.org Subject: Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6 Message-ID: <20060922012952.79405.qmail@web83108.mail.mud.yahoo.com> In-Reply-To: <20060922011759.GA32442@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Kris Kennaway <kris@obsecurity.org> wrote: > On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard > wrote: > > Hello, > > > > I'm having trouble building tcl84. These issues > did > > not seem to exist until I updated the ports tree > and > > world the other day > > > > Heres the basic stuff: > > > > FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 > > is what uname -a spits out ports were updated > right > > before the system source update. > > > > make.conf has > > > > > CXXFLAGS+=-O3 -fno-strict-aliasing > > Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing > > > MAKEOPTS="-j5" > > Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. > > kris dazed confused and ignorant... -brian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060922012952.79405.qmail>