1 |
Am 07.03.2011 11:24, schrieb Mike Frysinger: |
2 |
> i plan on punting these (hardly used) functions from the |
3 |
> multilib.eclass (once the handful of open bugs are closed): |
4 |
> get_ml_incdir |
5 |
> prep_ml_includes |
6 |
> create_ml_includes |
7 |
> create_ml_includes-absolute |
8 |
> create_ml_includes-tidy_path |
9 |
> create_ml_includes-listdirs |
10 |
> create_ml_includes-makedestdirs |
11 |
> create_ml_includes-allfiles |
12 |
> create_ml_includes-sym_for_dir |
13 |
> further, the CDEFINE_xxx multilib vars will go with them |
14 |
> |
15 |
> for the most part, these were really only used by the glibc ebuilds. |
16 |
> for the ones that dont support multilib natively (and necessitated |
17 |
> these funcs in the first place), i'll simply punt the ebuilds. this |
18 |
> will probably be just the glibc-2.5 ebuilds for now. |
19 |
> |
20 |
> also, i'll be converting the glibc ebuilds do always invoke the |
21 |
> multilib_env helper functions. this will allow us to drop the |
22 |
> {C,LD}FLAGS_xxx and friends from profiles since glibc was the main |
23 |
> consumer. i imagine this inadvertently break some other packages, so |
24 |
> if people want to test this on their own systems before i make the |
25 |
> commit, that'd be cool. the plan would be for said breakage will go |
26 |
> through bugzilla to get the ebuild updated rather than reverting the |
27 |
> profile. |
28 |
> -mike |
29 |
> |
30 |
> |
31 |
|
32 |
Please leave those vars in the profile, i depend on them in multilib-portage to crosscompile e.g. |
33 |
for x86 on the amd64 profile. If you remove them now, they would be re-added again once |
34 |
multilib-portage (and the related EAPI) become official, so imho we can just leave them in for now. |
35 |
|
36 |
-- |
37 |
Thomas Sachau |
38 |
|
39 |
Gentoo Linux Developer |