Date: Fri, 5 Sep 2003 07:48:50 -0500 From: Manuel Rabade - MiG <mig@mig-29.net> To: "Simon L. Nielsen" <simon@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org Subject: Re: Strange core dump of jade when building /usr/doc Message-ID: <20030905124850.GA37813@mig-29.net> In-Reply-To: <20030905113327.GB411@FreeBSD.org> References: <20030902222708.GC341@mig-29.net> <20030904205509.GB674@FreeBSD.org> <20030904230035.GA94554@mig-29.net> <20030905113327.GB411@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Sep 05, 2003 at 01:33:28PM +0200, Simon L. Nielsen wrote:
> 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=
spanish) and
> > > > when i do a 'make DOC_LANG=3Den_US.ISO8859-1 FORMATS=3Dhtml' jade c=
rashes in
> > > > /usr/doc/en_US.ISO8859-1/articles/hubs, sometimes as a 'Bus error' =
and 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 erro=
r.
> > > 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 a=
nd 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 j=
ade, very
> > strange if it's the problem because that flags are not too much agressi=
ve.
>=20
> 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.
>
Hum .. i am not an expert compiling and tweaking, i have read that the -O2 =
is
not too much agresive, thanks for the tip :-D.
I will overide the flags and compile jade in the evening, i have to go scho=
ol
now :-P, and i will tell you what happens.
Thanks.
> From make.conf(5) :
>=20
> CFLAGS (str) Controls the compiler setting when compiling C code.
> Optimization levels above -O (-O2, ...) are not supported.
>=20
> In short, while higher -O levels might work, they are rarely worth all
> the problems they create.
--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/WIYyOZtXZaozJcARAqsFAJ9mn2uvXPofHTMWJASC6dHTItQUrwCgobGy
whJu65ysWM2UL/JjrhG+LUU=
=qqxP
-----END PGP SIGNATURE-----
--YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030905124850.GA37813>