On Thu, Apr 05, 2012 at 01:16:27PM +1200, Michael Hope wrote: >On 5 April 2012 12:07, Joseph S. Myers <jos...@codesourcery.com> wrote: >> >> No. A system is either purely hard-float or purely soft-float, and the >> same paths are used for both so they can't coexist. (Mismatches at >> *static* link time are detected through object attributes.) > >Ah, the same as ARM then. The MIPS community would need something >similar to this patch if they wanted to support soft and hard float >side by side.
Yes, definitely. >>> Big endian is extremely uncommon on ARM and I'd rather define it when >>> needed. For strictness sake I'll change the patch to use the new path >>> for hard float little endian only. >> >> I don't think that's correct; the new path should be used independent of >> endian, just as the existing path is. > >OK. > >> But any multiarch support patch >> should presumably define separate multiarch paths for each endianness. > >That's up to Debian. I've asked for documentation on the final tuples >and what they mean as the one at: > http://wiki.debian.org/Multiarch/Tuples > >is out of date. I prefer defining what is needed now and doing others >as needed. I'm most of the way through an update for that page now; I'll ask for comments/review shortly. Cheers, -- Steve McIntyre steve.mcint...@linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs