On Sunday 18 October 2009 14:49:09 Thomas Sachau wrote: > Robin H. Johnson schrieb: > > On Mon, Oct 12, 2009 at 04:50:23PM -0400, Mike Frysinger wrote: > >> what exactly does this "lib32" do ? naming USE flags according to > >> specific ABI implementations is a bad idea. you have to forget special > >> casing anything to "lib32 vs lib64". amd64, while the most common, is > >> hardly extensible. we must handle multiple ABIs which easily might have > >> the same bitsize. > > > > The canonical example for this does still remain MIPS I believe. > > > > The most common ABIs in MIPS are: > > o32, n32 - Both in Gentoo releases > > n64 - Was experimentally done in Gentoo > > (default-linux/mips/2007.1-dev/generic-be/n64) o64, eabi, meabi, nubi - > > Not sure if they were were ever released in any way. > > > > Crossdev DOES support the full swath of these last I checked it. > > There is a difference between creating a toolchain and supporting all > packages for that arch and every possible ABI you can crosscompile. > > Currently i only support amd64 since thats the only ARCH i know and have > access to. If i get enough details to implement other ARCHes and some way > to test it there, i might try it for those other ARCHes too.
we're not asking you to implement support for these ABIs, just to keep in mind that any implementation that does not scale and/or hardcodes to a single set of ABIs isnt a proper solution -mike
signature.asc
Description: This is a digitally signed message part.
