Date: Tue, 20 Mar 2012 10:41:49 -0700 From: Juli Mallett <juli@clockworksquid.com> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-mips@FreeBSD.org" <freebsd-mips@freebsd.org> Subject: Re: Unbreaking ports with n64 MIPS. Message-ID: <CACVs6=8afS6Dd8DmdJhi-36p5vNJH0otU=APe0mOOXxhbW3SSw@mail.gmail.com> In-Reply-To: <DEFF7F2C-0D27-4C00-BF4C-557C8C13CBBF@bsdimp.com> References: <CACVs6=8z4BYcpQ=jVKLLb7v2LmSD-MRxXQdYRrOj-hG1j572Cg@mail.gmail.com> <E580AB5B-AD2A-4E04-A040-8E9E5D667040@bsdimp.com> <CACVs6=_FXqM2vjx1B4C819kuapaCXek-RfVwo0YPsk74r4%2BgkA@mail.gmail.com> <CA%2B7sy7AROF0tmSse7Dx3%2BhmPNQ57MtGvqJe6ndqaYSMz240nFw@mail.gmail.com> <DEFF7F2C-0D27-4C00-BF4C-557C8C13CBBF@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 20, 2012 at 10:35, Warner Losh <imp@bsdimp.com> wrote: >> mips (default cpu type: mips32 r1, soft-float) >> =C2=A0kernel - o32 elf binary support >> =C2=A0userspace - o32 > > why not also support n32 binaries (apart from the need for someone to do = the work :)? Because n32 requires 64-bit registers. >> The only thing I see as an issue here is that if someone builds world >> with a specialized CPUTYPE, they will not be able to use standard >> ports binaries. This would mean that we would need to extend multi-lib >> with CPU types. > > Frist of all, why is that? > > Second of all, how would the extentions to multilib look and how would th= at enable people to run standard ports-built packages created by the projec= t? Packages are going to be a real killer for us given the bugs in our binutils that make it refuse to link "incompatible" cputypes together, even though there's no problem with doing so. We should probably just remove that behavior and stop complaining about it and then half this complexity goes away, except for the question of whether packages need to match world wrt soft- and hard-float. > I generally like this partitioning, but haven't been working with this st= uff enough day to day to know if all the details are correct.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACVs6=8afS6Dd8DmdJhi-36p5vNJH0otU=APe0mOOXxhbW3SSw>