From owner-freebsd-stable@FreeBSD.ORG Tue May 2 14:29:52 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21BCF16A424; Tue, 2 May 2006 14:29:52 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 210C243D62; Tue, 2 May 2006 14:29:44 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.6/8.13.6) with ESMTP id k42ETebr095965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 May 2006 10:29:40 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.6/8.13.6/Submit) id k42ETetP095964; Tue, 2 May 2006 10:29:40 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: Giorgos Keramidas Date: Tue, 2 May 2006 10:29:39 -0400 User-Agent: KMail/1.9.1 References: <200605011604.26507.mi+mx@aldan.algebra.com> <20060502062258.GA62901@gothmog.pc> In-Reply-To: <20060502062258.GA62901@gothmog.pc> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Mikhail Teterin , stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 14:29:52 -0000 On Tuesday 02 May 2006 02:22, Giorgos Keramidas wrote: = cc can build binaries just fine if you also use the -B option: = =         % cc -m32 -B/usr/lib32 ... Yes, this is a work-around. It is not a solution... /usr/lib32 should be there automatically. = I know it does because I've used it on my laptop a while ago [...] Unfortunately, according to the compiler-maintainer, there are some cases, when the different include files should also be used in the -m32 case, and that appears harder to fix. Until that is fixed, David is unwilling to pick this very low-hanging fruit either. Evidently, he does not "subscribe" to the 80/20 principle :-( -mi