Date: Mon, 11 Apr 2005 16:45:07 -0400 From: Mikhail Teterin <Mikhail.Teterin@murex.com> To: Jose M Rodriguez <josemi@freebsd.jazztel.es> Cc: freebsd-gnome@freebsd.org Subject: Re: mozilla's install hanging on amd64 Message-ID: <200504111645.07948.Mikhail.Teterin@murex.com> In-Reply-To: <200504112221.21758.freebsd@redesjm.local> References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <200504111229.39072.mi%2Bmx@aldan.algebra.com> <200504112221.21758.freebsd@redesjm.local>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. > This is a very agressive aproach. -march=opteron is supported in > previous versions of gcc(3)? I think no. Can you try a more > conservative approach like -march=pentium-mmx -mtune=optetron? Now that -- setting -march manually -- would, indeed, be "playing with unsupported gcc flags" and as such qualify for immediate dismissal of any and all bug reports. I'll stick to setting CPUTYPE to the processor I have, and leave the rest to the system. -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504111645.07948.Mikhail.Teterin>