From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 1 03:53:28 2004 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 A71DE16A4CE for ; Fri, 1 Oct 2004 03:53:28 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E14D43D31 for ; Fri, 1 Oct 2004 03:53:28 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from pythonemproject.com (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc11) with ESMTP id <2004100103532701300c4j34e> (Authid: europax); Fri, 1 Oct 2004 03:53:27 +0000 Message-ID: <415CD53C.7060606@pythonemproject.com> Date: Thu, 30 Sep 2004 20:55:40 -0700 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <415C3C61.1010705@pythonemproject.com> <200409301144.13174.peter@wemm.org> <415C5ADA.2030007@pythonemproject.com> <415C7977.5040602@withagen.nl> In-Reply-To: <415C7977.5040602@withagen.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: grub port question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2004 03:53:28 -0000 Willem Jan Withagen wrote: > Rob wrote: > >> Peter Wemm wrote: >> >>> On Thursday 30 September 2004 10:03 am, Rob wrote: >>> >>> >>>> I was going to try to use grub for booting from my multidisk system, >>>> as I was told that the bootup process is done in i386, then it is >>>> transfered to 64 bit mode. So grub works OK. But last nite I tried >>>> to install grub from ports and got the message immediately >>>> (paraphrasing) "that I could not compile a 32 bit application on a 64 >>>> bit OS." >>>> >>>> So now I'm really confused LOL. >>>> >>> >>> >>> >>> In a nutshell, the toolchain has various flags/switches to control >>> its operating mode. For example, gcc has -m32 and -m64. The catch >>> is that we do not install the 32 bit version of the include files >>> yet. And you have to use tools/lib32/build32.sh to build the 32 bit >>> libraries. The rest of the toolchain has various mode switches. >>> eg: as --32 etc. gcc could be slightly tweaked to use the correct >>> include and library paths, but for now it needs horrible -I and -L >>> switches. >>> >>> However, the port problem is that it doesn't know any of these magic >>> options. I hate to say it, but the easiest thing is probably to >>> just fetch the i386 package for now. If pkg_add won't do it, then >>> it should be possible to extract the tarball by hand and do the >>> deed. Not pretty, I know. >>> >>> > This was probably due to the cryptic information I mailed. > I should have mentioned that you need to compile it on the i386 > platform, which is also the location where I installed it. > This all under the assumption that you would also like to install a > FreeBSD-i386, like I did. > > Sorry for the misinformation. > --WjW > > Oh OK, I thought that might be the case. Perhaps a mini-FBSD 32 bit system on my AMD-64 box would be a good addition. Rob