From owner-freebsd-ports@FreeBSD.ORG Mon Sep 13 19:15:08 2004 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 3B56F16A4CE for ; Mon, 13 Sep 2004 19:15:08 +0000 (GMT) Received: from thor.piquan.org (adsl-66-125-235-59.dsl.sntc01.pacbell.net [66.125.235.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id D508543D2F for ; Mon, 13 Sep 2004 19:15:07 +0000 (GMT) (envelope-from joelh@piquan.org) Received: from thor.piquan.org (joelh@localhost [127.0.0.1]) by thor.piquan.org (8.12.10/8.12.10) with ESMTP id i8DJEOcR037781; Mon, 13 Sep 2004 12:14:24 -0700 (PDT) (envelope-from joelh@piquan.org) Received: (from joelh@localhost) by thor.piquan.org (8.12.10/8.12.10/Submit) id i8DJENv8037780; Mon, 13 Sep 2004 12:14:23 -0700 (PDT) (envelope-from joelh@piquan.org) X-Authentication-Warning: thor.piquan.org: joelh set sender to joelh@piquan.org using -f To: "Walter Venable" Precedence: first-class References: From: Joel Ray Holveck Date: Mon, 13 Sep 2004 12:14:22 -0700 In-Reply-To: (Walter Venable's message of "Mon, 13 Sep 2004 09:22:17 -0400") Message-ID: <87656it20h.fsf@thor.piquan.org> User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on thor.piquan.org X-Virus-Status: Clean cc: ports@freebsd.org Subject: Re: gcc295 and -march X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 19:15:08 -0000 > Does this behavior not already happen automatically? I thought that > if gcc 2 were used it would set it to the closest possible machine > achitecture to what you specified in make.conf, such as "i686" if you > had set "athlon". > > Note that 2.95 is still the default compiler on 4.x. Hmmm... When I tried to build lang/clisp, which specifies USE_GCC=295, it did pass -march=athlon to the compile. GNU configure said that the compiler couldn't produce an executable, so I checked the log and gcc295 had flagged the athlon arch as an error. I checked my CFLAGS in make.conf and my environment and they were both '-O -pipe'. When I then did a "make clean all CPUTYPE=''" it configured fine (although it bombed during the build... haven't troubleshooted that yet, sigh). So I conclude that the USE_GCC doesn't prevent athlon from being passed in the Makefile. It may be the case that /usr/share/mk/* on 4.x does downgrade athlon to i686 or whatever in all cases. joelh -- Joel Ray Holveck - joelh@piquan.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped