From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 09:46:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 823E116A41C for ; Fri, 3 Jun 2005 09:46:27 +0000 (GMT) (envelope-from chu@kemia.me.tut.fi) Received: from kemia.me.tut.fi (kemia.me.tut.fi [130.230.40.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1A1943D49 for ; Fri, 3 Jun 2005 09:46:26 +0000 (GMT) (envelope-from chu@kemia.me.tut.fi) Received: from kempc17.me.tut.fi (kempc32.me.tut.fi [130.230.40.50]) by kemia.me.tut.fi (8.13.1/8.13.1) with ESMTP id j539kPn4030908 for ; Fri, 3 Jun 2005 12:46:25 +0300 In-Reply-To: Organization: Tampere University of Technology References: To: freebsd-current@freebsd.org Message-ID: From: "Vladimir Chukharev" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Fri, 03 Jun 2005 12:46:25 +0300 User-Agent: Opera M2/8.0 (FreeBSD, build 1095) Subject: Newest loader from CVS now working! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 09:46:27 -0000 I can confirm that the two patches by obrien to src/sys/boot/ficl/Makefile and src/lib/libstand/Makefile make loader work with CPUTYPE?=pentium-m in /etc/make.conf on my notebookPC with pentium-m. Thanks to Pawel Worach, David O'Brien and others! I want to ask two questions in this connection. First, is -mno-sse3 needed in the same places or is it known to be safe for processors with SSE3? Second. Having CPUTYPE?=pentium-m actually breaks some ports which are compiled with older gcc since it does not know pentium-m. The diagnostic is rather unclear, something like 'compiler cannot produce executable'. I reported it to -ports, and recieved no comments. Can this type of errors (wrong architecture name) be checked in bsd.gcc.mk and either changed to a close known one or diagnosed more clearly? Best regards, -- V.Chukharev