Date: Tue, 20 Mar 2007 14:21:25 -0400 From: Mike Meyer <mwm@mired.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: Andriy Gapon <avg@icyb.net.ua>, freebsd-amd64@freebsd.org Subject: Re: 32-bit/i386 ports/packges on amd64 Message-ID: <17920.9765.726023.526080@bhuda.mired.org> In-Reply-To: <20070320073030.GC76696@turion.vk2pj.dyndns.org> References: <45FE7615.3090606@icyb.net.ua> <20070320073030.GC76696@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In <20070320073030.GC76696@turion.vk2pj.dyndns.org>, Peter Jeremy <peterjeremy@optushome.com.au> typed: > Solaris (and I suspect Linux) has taken the approach that the kernel > is 64-bit but userland is primarily 32-bit with applications able to > build/run as 64-bit if desired. Linux (at least the rhe distribution) doesn't do this. The system binaries are all 64-bit, the toolchains build 64-bit binaries by default, etc. However, the toolchains are also configured so that passing -m32 to gcc will do the right thing all the way down the line; last time I tried that (6.1 or so) it didn't work. The first step in getting the ports/packages to work properly is to either 1) get the system c cmopiler to correctly handle requests to build 32-bit binaries, or 2) add a port that adds a C compiler that does that. FWIW, OSX has a 32-bit kernel and userland, but can run (and build) 64-bit binaries. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17920.9765.726023.526080>