Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Sep 2003 13:33:28 +0200
From:      "Simon L. Nielsen" <simon@FreeBSD.org>
To:        Manuel Rabade - MiG <mig@mig-29.net>
Cc:        freebsd-doc@FreeBSD.org
Subject:   Re: Strange core dump of jade when building /usr/doc
Message-ID:  <20030905113327.GB411@FreeBSD.org>
In-Reply-To: <20030904230035.GA94554@mig-29.net>
References:  <20030902222708.GC341@mig-29.net> <20030904205509.GB674@FreeBSD.org> <20030904230035.GA94554@mig-29.net>

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

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

On 2003.09.04 18:00:35 -0500, Manuel Rabade - MiG wrote:
> On Thu, Sep 04, 2003 at 10:55:11PM +0200, Simon L. Nielsen wrote:
> > On 2003.09.02 17:27:08 -0500, Manuel Rabade - MiG wrote:
> > > Hi, i have updated /usr/doc (with only the documents in english and s=
panish) and
> > > when i do a 'make DOC_LANG=3Den_US.ISO8859-1 FORMATS=3Dhtml' jade cra=
shes in
> > > /usr/doc/en_US.ISO8859-1/articles/hubs, sometimes as a 'Bus error' an=
d other
> > > times as a 'Segmentation fault'.
> >=20
> > I can't remeber that I have ever experienced jade coredumping... The
> > fact that it dies with different errors make me suspect hardware error.
> > It could also be non-standard CFLAGS in make.conf.
> >=20
> > I don't really have any other ideas to why it dies.
>=20
> Humm .. i think that it isn't a hardware error, is my desktop machine and=
 i can
> compile and run everything fine except *that* :'(.
>=20
> I "fix" it yesterday installing jade from a package (jade-1.2.1_1), so i =
think
> that my CFLAGS ('CPUTYPE=3Dp4' and 'CFLAGS=3D-O2 -pipe') are breaking jad=
e, very
> strange if it's the problem because that flags are not too much agressive.

Actually they are a bit agressive. '-O2' have produced broken code for
varius versions of GCC, and at least one version of gcc 3.x has produced
broken code for CPUTYPE=3Dp4 (though this should be fixed now).  More
optimizations sometimes trigger coding bugs, which lower -O levels hide.

=46rom make.conf(5) :

     CFLAGS   (str) Controls the compiler setting when compiling C code.
              Optimization levels above -O (-O2, ...) are not supported.

In short, while higher -O levels might work, they are rarely worth all
the problems they create.

--=20
Simon L. Nielsen
FreeBSD Documentation Team

--K8nIJk4ghYZn606h
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/WHSHh9pcDSc1mlERAupIAJ9V2ZJZkauEsXOlPkCx47WUqKdM0wCdHb+h
Fcs7+AraMJbu44yykxhG+6E=
=pyXF
-----END PGP SIGNATURE-----

--K8nIJk4ghYZn606h--



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