From owner-freebsd-ports@FreeBSD.ORG Mon Apr 11 20:34:55 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 52A9B16A516; Mon, 11 Apr 2005 20:34:55 +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 1C01343D5C; Mon, 11 Apr 2005 20:34:54 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) j3BKYh6n084680; Mon, 11 Apr 2005 22:34:43 +0200 (CEST) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.3/8.13.3/Submit) id j3BKYe13000921; Mon, 11 Apr 2005 22:34:40 +0200 (CEST) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-ports@freebsd.org Date: Mon, 11 Apr 2005 22:34:39 +0200 User-Agent: KMail/1.8 References: <200504102137.j3ALbm0h079084@corbulon.video-collage.com> <425AA728.7050809@samsco.org> <20050411194439.GA98521@isis.sigpipe.cz> In-Reply-To: <20050411194439.GA98521@isis.sigpipe.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504112234.40840.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: doc@freebsd.org cc: Scott Long cc: Roman Neuhauser cc: Mikhail Teterin 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:34:55 -0000 El Monday 11 April 2005 21:44, Roman Neuhauser escribi=F3: > # scottl@samsco.org / 2005-04-11 10:34:48 -0600: > > Mikhail Teterin wrote: > > >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. > > > I think this thread shows that there is a need for a written > policy on -march / -mcpu / -mtune gcc options in ports. Heated > discussions like this one could be avoided if the Porters Handbook > included an article or chapter on this. > And more work in /usr/share/mk/bsd.cpu.mk. Beggining with a way to take=20 in account what gcc will be used (we can't use -mtune for gcc=20 <3.4 ...). And a more conservative approach (-march=3Dpentium/pentiun-mmx/i686 and=20 =2Dmtune/-mcpu to the real cpu). But my skill are not in the way. I prefer cut CFLAGS in conflictive=20 ports. =2D- josemi > Whether that policy was "-march=3D must work" or "-march=3D is > unsupported" or "ports should filter out -march=3D if they break > with it, patches for -march-related bugs welcome" (most reasonable > IMNSHO) would be a matter of consensus, but would be a boon to have. > > MFT set to ports@ and doc@.