Date: Thu, 07 Jun 2012 23:35:32 +0200 From: Mel Flynn <rflynn@acsalaska.net> To: Warren Block <wblock@wonkity.com> Cc: freebsd-ports@freebsd.org Subject: Re: Firefox 13 Message-ID: <4FD11EA4.3090904@acsalaska.net> In-Reply-To: <alpine.BSF.2.00.1206071520001.55980@wonkity.com> References: <alpine.BSF.2.00.1206070943010.53425@wonkity.com> <4FD0D0BB.5020509@daemonic.se> <alpine.BSF.2.00.1206071304480.55320@wonkity.com> <4FD10C46.902@acsalaska.net> <alpine.BSF.2.00.1206071520001.55980@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7-6-2012 23:25, Warren Block wrote: > On Thu, 7 Jun 2012, Mel Flynn wrote: > >> On 7-6-2012 21:55, Warren Block wrote: >> >>> gcc46, and I do have CPUTYPE?=native in make.conf... >>> >>> Interesting! Built without CPUTYPE set, Firefox seems fine. >>> Compiler bug? >> >> Shot in the dark: SSE support? Based on threads earlier on this list >> with respect to chrome. > > SSE support by gcc, you mean? No idea, but just to make sure I rebuilt > with CPUTYPE?=native again, and that's definitely the problem. I was referring to this post: http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/075290.html While it's related to clang, CPUTYPE seems to have an effect on selected extensions and perhaps the root cause is there. Like I said, shot in the dark. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD11EA4.3090904>