Date: Mon, 11 Apr 2005 14:06:12 -0400 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: Scott Long <scottl@samsco.org> Cc: gnome@freebsd.org Subject: Re: mozilla's install hanging on amd64 Message-ID: <200504111406.13047.mi%2Bmx@aldan.algebra.com> In-Reply-To: <425AA728.7050809@samsco.org> References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <200504111229.39072.mi%2Bmx@aldan.algebra.com> <425AA728.7050809@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Even a broken thing can be useful to some. > > Is my car broken because it can't go 300km/hr? A Porshe can, so > shouldn't mine be able to? A better analogy would be a car running only 87-rated gasoline. Nothing in its manual would suggest anything about it, but it just would not run on anything else. BTW, a complete rebuild with `-O0 -g -march=opteron' causes the same problem. If, however, I cd into /opt/lib/mozilla and run the hanging command manually it succeeds instantly... > But I don't play with custom gcc options. You keep saying "play" and "custom" -- there is nothing like that. I'm just following the documented (in example and in manual page) procedure -- setting the CPUTYPE. This just in, however: http://hardware.slashdot.org/comments.pl?sid=145676&cid=12201753 :-) > Shouting to everyone that mozilla is BROKEN doesn't help this very much. If you scroll up this thread, you'll notice, that I only began to "shout" in response to suggestion, that the failure is my own fault, because I added a "non-standard and un-supported" compiler flag. The suggestion was yours and you should admit -- if only for the record -- you were wrong. Most likely there is a subtle bug somewhere inside Mozilla, that is exposed by the -march=opteron setting. We should be thankful, a reliable way to reproduce it is now known :-) -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504111406.13047.mi%2Bmx>