1 |
Dnia 2015-03-29, o godz. 19:59:19 |
2 |
Nikos Chantziaras <realnc@×××××.com> napisał(a): |
3 |
|
4 |
> On 29/03/15 19:24, Michał Górny wrote: |
5 |
> > Dnia 2015-03-29, o godz. 19:14:43 |
6 |
> > Nikos Chantziaras <realnc@×××××.com> napisał(a): |
7 |
> > |
8 |
> >> On 17/03/15 18:29, Michał Górny wrote: |
9 |
> >>> Dnia 2015-03-17, o godz. 16:55:32 |
10 |
> >>> René Neumann <lists@××××××.eu> napisał(a): |
11 |
> >>> |
12 |
> >>>> Am 17.03.2015 um 16:33 schrieb Michał Górny: |
13 |
> >>>>> However, some |
14 |
> >>>>> users may prefer setting ABI_X86 globally to enable 32-bit libraries |
15 |
> >>>>> in all packages that support building them. This can be done using |
16 |
> >>>>> the following package.use entry: |
17 |
> >>>>> |
18 |
> >>>>> */* abi_x86_32 |
19 |
> >>>>> |
20 |
> >>>> |
21 |
> >>>> I'm confused: Has this a different semantics from adding |
22 |
> >>>> USE+='abi_x86_32' to make.conf? If no, why mention this strange way |
23 |
> >>>> (which is new to me) for setting default global useflags. |
24 |
> >>> |
25 |
> >>> Because this is how users learn new fun stuff. Like sane configuration. |
26 |
> >> |
27 |
> >> I don't see why ABI_X86 is not the sane option. Using wildcards in |
28 |
> >> package.use is what sounds insane to me. |
29 |
> > |
30 |
> > Because it overrides the defaults without providing a way to append to |
31 |
> > them. |
32 |
> |
33 |
> According to emerge --info, ABI_X86 seems to append, not override. In |
34 |
> make.conf: |
35 |
> |
36 |
> ABI_X86="32" |
37 |
> |
38 |
> Then: |
39 |
> |
40 |
> $ emerge --info | grep -i abi_x86 |
41 |
> |
42 |
> You get: |
43 |
> |
44 |
> ABI_X86="32 64" |
45 |
> |
46 |
> |
47 |
> "64" seems to be always there. You cannot override it. Using |
48 |
> ABI_X86="32" in make.conf seems to only append "32" to the default. |
49 |
|
50 |
Portage may do that because it's forced by default. But some packages |
51 |
'unforce' it, and that's when it matters. |
52 |
|
53 |
> |
54 |
> If this is not the case, and "*/* abi_x86_32" in package.use really does |
55 |
> something different, then this is implemented in a way too confusing for |
56 |
> people and should be considered a bug :-/ |
57 |
|
58 |
Yes, USE support in make.conf is a big pile of random misbehaviors |
59 |
and bugs that need to be killed with fire. |
60 |
|
61 |
|
62 |
-- |
63 |
Best regards, |
64 |
Michał Górny |