Unbreaking ports with n64 MIPS.

[Andrew Duane]

I'd be fine with this. There should be a simple default for mips64, and big endian does seem to be the default assumption.

I've never used the n32 port though.

 ...................................
Andrew Duane
Juniper Networks
+1 978-589-0551 (o)
+1 603-770-7088 (m)
aduane at juniper.net

 


> -----Original Message-----
> From: owner-freebsd-mips at freebsd.org [mailto:owner-freebsd-
> mips at freebsd.org] On Behalf Of Juli Mallett
> Sent: Thursday, March 15, 2012 3:47 AM
> To: freebsd-mips at FreeBSD.org
> Subject: Unbreaking ports with n64 MIPS.
> 
> All,
> 
> Does anyone object to changing the target name of mips64eb to be
> rendered as mips64?  It's difficult to build ports because although
> the redundant "mipseb" as widely-recognized as synonymous as "mips",
> our quirky use of "mips64eb" instead of "mips64" just plain breaks
> stuff.  "mips64el" is, of course, recognized, but it's generally
> assumed that MIPS is big-endian by default.  I understand this
> assumption wasn't made in FreeBSD because the port that was committed
> focused early on a number of little-endian MIPS systems, but it seems
> worthwhile to switch.  I'm happy to make the relevant changes.
> 
> Thanks,
> Juli.
> 
> PS: This may only need to be changed in how we name things in our GCC
> and binutils to fix ports, but I'd rather change everything else to
> match for the sake of consistency.
> 
> PPS: What to do for n32?  I think mips64{,el} is right for GCC and
> binutils, with something like "n32" in the OS name, but I haven't
> booted IRIX in almost a decade, so I can't remember what the
> convention is.  I don't even know if there's software in ports that
> would care.
> _______________________________________________
> freebsd-mips at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to "freebsd-mips-unsubscribe at freebsd.org"