From owner-freebsd-amd64@FreeBSD.ORG Sun Mar 27 16:45:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7939D16A4CE for ; Sun, 27 Mar 2005 16:45:48 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E41D43D48 for ; Sun, 27 Mar 2005 16:45:48 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j2RGjmN1097365; Sun, 27 Mar 2005 08:45:48 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j2RGjlWm097364; Sun, 27 Mar 2005 08:45:47 -0800 (PST) (envelope-from sgk) Date: Sun, 27 Mar 2005 08:45:47 -0800 From: Steve Kargl To: Robert Wideman Message-ID: <20050327164547.GA97330@troutmask.apl.washington.edu> References: <4246D5B0.309@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4246D5B0.309@sbcglobal.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: 32 bit compatibility on FreeBSD 5.3 Amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2005 16:45:48 -0000 On Sun, Mar 27, 2005 at 09:48:00AM -0600, Robert Wideman wrote: > I'm running FreeBSD 5.3-Release AMD64 version. When I try to compile my > source that im writing for 32 bit compatibility I receive errors. > > gcc -m32 > I don't think you can use the -m32 multilib options, yet. AMD64 has compatibility for *running* 32-bit binaries. It does not have 32-bit *building* capabilities. > Ive read that 5.3 has problems with 32 bit compatibility and that 5.4 > should resolve this. Does anyone know of a workaround on this? 32-bit compatibility for executions appears to work fine on my system. One work-around you can use is to actually use a 32-bit system to build your software. -- Steve