From owner-freebsd-ports@FreeBSD.ORG Mon Apr 11 20:21:47 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48DC416A4CE; Mon, 11 Apr 2005 20:21:47 +0000 (GMT) Received: from 62-15-209-148.inversas.jazztel.es (62-15-209-148.inversas.jazztel.es [62.15.209.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC43F43D4C; Mon, 11 Apr 2005 20:21:45 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) j3BKLVt8084643; Mon, 11 Apr 2005 22:21:31 +0200 (CEST) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.3/8.13.3/Submit) id j3BKLM0Q000804; Mon, 11 Apr 2005 22:21:22 +0200 (CEST) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-gnome@freebsd.org Date: Mon, 11 Apr 2005 22:21:20 +0200 User-Agent: KMail/1.8 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <425AA274.2090604@samsco.org> <200504111229.39072.mi+mx@aldan.algebra.com> 0.73a on corbulon.video-collage.com In-Reply-To: <200504111229.39072.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504112221.21758.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.30.0.7; VDF: 6.30.0.45; host: antares.redesjm.local) cc: ports@freebsd.org cc: gnome@freebsd.org cc: Mikhail Teterin cc: Scott Long Subject: Re: mozilla's install hanging on amd64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 20:21:47 -0000 El Monday 11 April 2005 18:29, Mikhail Teterin escribi=F3: > > 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=3DXXX automatically -- fact. All ports must handle > this. Those that can not are broken. Plan and simple. There is > nothing to argue: `-O -pipe -march=3Dopteron' must work. > This is a very agressive aproach. -march=3Dopteron is supported in=20 previous versions of gcc(3)? I think no. Can you try a more=20 conservative approach like -march=3Dpentium-mmx -mtune=3Doptetron? But, in the meantime, I think that behave as firefox maybe a better=20 aproach: =2E... =2Eif defined(WITH_OPTIMIZED_CFLAGS) CFLAGS:=3D -O2 -fno-strict-aliasing ${CFLAGS:N-O*} =2Eelse CFLAGS:=3D -O ${CFLAGS:N-O*:N-m*} CONFIGURE_ARGS+=3D --enable-optimize=3D-O =2Eendif =2D- josemi