1 |
Dnia 2013-08-25, o godz. 23:55:59 |
2 |
Thomas Sachau <tommy@g.o> napisał(a): |
3 |
|
4 |
> Michał Górny schrieb: |
5 |
> > Dnia 2013-08-25, o godz. 21:34:09 |
6 |
> > Thomas Sachau <tommy@g.o> napisał(a): |
7 |
> > |
8 |
> >> Ulrich Mueller schrieb: |
9 |
> >>>>>>>> On Sun, 25 Aug 2013, Thomas Sachau wrote: |
10 |
> >>> |
11 |
> >>>> workaround: add a variable, which changes the return of the function |
12 |
> >>>> checking for the current ABI (always true with variable, without |
13 |
> >>>> only true, when $ABI == $DEFAULT_ABI) |
14 |
> >>> |
15 |
> >>> Would this variable be set by the user, in profiles, or in ebuilds? |
16 |
> >> |
17 |
> >> This variable can be set by users and profiles, when they want binaries |
18 |
> >> for a different ABI (e.g. 64bit toolchain with 32bit userland). |
19 |
> > |
20 |
> > Where it simply won't work since executables for the native ABI will |
21 |
> > overwrite earlier ones. |
22 |
> > |
23 |
> |
24 |
> You obviously dont read my complete mails, otherwise you would have seen |
25 |
> my later example, which works perfectly fine, once this patch applied: |
26 |
> For the complete userland, set ABI_X86=32, so no 64bit target, no |
27 |
> executables for the native ABI, nothing overwriting the 32bit binaries |
28 |
> => it works. |
29 |
|
30 |
This is forbidden by profiles and as you noticed above would cause more |
31 |
screwup than benefit. |
32 |
|
33 |
> Of course, if there are further issues with the ebuilds (like only parts |
34 |
> of the dependencies converted with those needed for the binaries left |
35 |
> out), it may cause issues with the current situation of the eclass and |
36 |
> ebuild, but will again allow users of multilib-portage to do exactly, |
37 |
> what i described, since they already are able to build the dependencies |
38 |
> for their target ABI. :-) |
39 |
|
40 |
multilib-portage can set DEFAULT_ABI=$ABI as I suggested and you |
41 |
happily ignored. I can understand that this could cause issues but you |
42 |
didn't seem to care to reply. |
43 |
|
44 |
Instead, you are trying to mess up gx86 with more hacks for your fancy |
45 |
out-of-tree project. Hacks that will convince people something works |
46 |
while it doesn't. And didn't I write this already? |
47 |
|
48 |
-- |
49 |
Best regards, |
50 |
Michał Górny |