Unbreaking ports with n64 MIPS.

Juli Mallett juli at clockworksquid.com
Tue Mar 20 17:42:10 UTC 2012


On Tue, Mar 20, 2012 at 10:35, Warner Losh <imp at bsdimp.com> wrote:
>> mips (default cpu type: mips32 r1, soft-float)
>>  kernel - o32 elf binary support
>>  userspace - 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 that enable people to run standard ports-built packages created by the project?

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 stuff enough day to day to know if all the details are correct.


More information about the freebsd-mips mailing list