Date: Mon, 11 Apr 2005 12:29:38 -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: <200504111229.39072.mi%2Bmx@aldan.algebra.com> In-Reply-To: <425AA274.2090604@samsco.org> References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <200504111212.25215.mi%2Bmx@aldan.algebra.com> <425AA274.2090604@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I don't really care to argue with you on this. If you want to be upset > that your special gcc flags don't work, that's your business. My whole point, Scott, is that there is nothing special about "my gcc flags". NOTHING. Setting CPUTYPE to match one's processor flavor is a long-documented way to do things -- fact. Such setting results in the corresponding -march=XXX automatically -- fact. All ports must handle this. Those that can not are broken. Plan and simple. There is nothing to argue: `-O -pipe -march=opteron' must work. > Meanwhile I'll continue using Mozilla on my amd64 machine. Even a broken thing can be useful to some. > Please refrain from making rash commits to the mozilla port in CVS that > would contradict this. I'm not the maintainer. I'll certainly submit any patches I come up with to both the maintainers and the vendor. I'll expect the maintainers to test and add them promptly to the port -- as is customary. But to even begin, I need to ram the simple point through: setting `-march=' MUST WORK. Otherwise, people like you will continue to deny a problem exists... > Working on correcting the code generation problems in either the mozilla > source or the gcc source would be a good way to positively contribute. -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504111229.39072.mi%2Bmx>