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