Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Sep 2006 21:34:20 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        backyard <backyard1454-bsd@yahoo.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
Message-ID:  <20060922013420.GA32796@xor.obsecurity.org>
In-Reply-To: <20060922012952.79405.qmail@web83108.mail.mud.yahoo.com>
References:  <20060922011759.GA32442@xor.obsecurity.org> <20060922012952.79405.qmail@web83108.mail.mud.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 21, 2006 at 06:29:52PM -0700, backyard wrote:
>=20
>=20
> --- Kris Kennaway <kris@obsecurity.org> wrote:
>=20
> > On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard
> > wrote:
> > > Hello,
> > >=20
> > > I'm having trouble building tcl84. These issues
> > did
> > > not seem to exist until I updated the ports tree
> > and
> > > world the other day
> > >=20
> > > Heres the basic stuff:
> > >=20
> > > FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38=20
> > > is what uname -a spits out ports were updated
> > right
> > > before the system source update.=20
> > >=20
> > > make.conf has
> > >=20
> >=20
> > > CXXFLAGS+=3D-O3 -fno-strict-aliasing
> >=20
> > Don't do that, it can cause problems
>=20
> can you be a little more specific? I was just using=20
> CXXFLAGS+=3D-O3=20
> 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.=20
>=20
> should it be
> CXXFLAGS+=3D
> dafaulting to O2 with no strict aliasing? given my=20
> CFLAGS=3D-pipe -O2 -fno-strict-aliasing

Just use the defaults (which is currently the same as your CFLAGS).

> > > MAKEOPTS=3D"-j5"
> >=20
> > Don't do that, it can cause problems
>=20
> I know doing=20
> 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.

The base system is fine, but many ports of third party software fail
to build (or the build misbehaves) with make -j.

Kris

--mYCpIKhGyMATD0i+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFEz2cWry0BWjoQKURAkI4AKCvjek5WEWltKyl0Ksd89FZHWBBkACfdVed
0wiIJBu2Pw5OFFyomlpusT4=
=geyR
-----END PGP SIGNATURE-----

--mYCpIKhGyMATD0i+--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060922013420.GA32796>