Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Sep 2004 20:55:40 -0700
From:      Rob <rob2@pythonemproject.com>
To:        Willem Jan Withagen <wjw@withagen.nl>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: grub port question
Message-ID:  <415CD53C.7060606@pythonemproject.com>
In-Reply-To: <415C7977.5040602@withagen.nl>
References:  <415C3C61.1010705@pythonemproject.com> <200409301144.13174.peter@wemm.org> <415C5ADA.2030007@pythonemproject.com> <415C7977.5040602@withagen.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?415CD53C.7060606>