From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 30 19:31:36 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 3D1BA16A4CE for ; Thu, 30 Sep 2004 19:31:36 +0000 (GMT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69D9543D39 for ; Thu, 30 Sep 2004 19:31:35 +0000 (GMT) (envelope-from henrik.w.lund@broadpark.no) Received: from [10.0.0.3] (52.80-202-129.nextgentel.com [80.202.129.52]) by mail.broadpark.no (Postfix) with ESMTP id F3CC27524; Thu, 30 Sep 2004 21:32:16 +0200 (MEST) Message-ID: <415CDCF0.4020302@broadpark.no> Date: Thu, 30 Sep 2004 21:28:32 -0700 From: Henrik W Lund User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: nb, en-us, en MIME-Version: 1.0 To: Peter Wemm References: <415C3C61.1010705@pythonemproject.com> <200409301144.13174.peter@wemm.org> In-Reply-To: <200409301144.13174.peter@wemm.org> Content-Type: text/plain; charset=us-ascii; 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 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Sep 2004 19:31:36 -0000 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. > > Greetings! Will this be resolved for 5.3-RELEASE, or is the problem complicated on a deeper level? If not for -RELEASE, will it ever happen in -STABLE? I got the impression that one of the developers (I believe it was David O'Brien) wanted to see a 64-bit kernel and (mostly) 32-bit world, as having a 64-bit world isn't really all that beneficial. This, of course, led me to thinking that work is being done to accomodate this in a non-hackish way. Am I way off the mark here? -- Henrik W Lund