Date: Thu, 24 Mar 2005 12:50:13 -0800 From: Astrodog <astrodog@gmail.com> To: freebsd-amd64@freebsd.org Subject: Re: AMD64 Ports Message-ID: <2fd864e05032412501c001a5d@mail.gmail.com> In-Reply-To: <20050324201036.GF60666@dragon.NUXI.org> References: <2fd864e05032316492d805751@mail.gmail.com> <20050324011220.GA81046@isis.sigpipe.cz> <2fd864e050323182432f78eaa@mail.gmail.com> <20050324201036.GF60666@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Mar 2005 12:10:36 -0800, David O'Brien <obrien@freebsd.org> wrote: > On Wed, Mar 23, 2005 at 06:24:24PM -0800, Astrodog wrote: > > How could we denote a linux32 dependancy? > > I don't follow. The current idea is that the linux_base port when > installed for FreeBSD will install both 32-bit and 64-bit[*] bits. > > [*] When 64-bit Linux support is later added. We have enough polishing > to do to just support all the things we've already got to the standards > people expect of FreeBSD. > -- > -- David (obrien@FreeBSD.org) > We have 2 problems, that I see. #1. Linux32 doesn't appear to be addressed for dependancies at all, almost every linux-something port I've found, calls itsself i386 only, and sometimes has minor RPM issues. #2. With IA32 Compatibility, it should be possible to install i386-only ports, and packages in quite a few cases, because of the binary compatibility stuff. I'm not sure how this could be handled either, since it would require a specific kernel option be enabled.... much like Linux32, I suppose.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fd864e05032412501c001a5d>