1 |
On 16/05/10 14:44, Alan McKinnon wrote: |
2 |
> On Sunday 16 May 2010 15:10:16 Simon wrote: |
3 |
> |
4 |
>> Hi, |
5 |
>> |
6 |
>> Please help me to get rid of this error while emerging portage: |
7 |
>> # emerge portage |
8 |
>> |
9 |
> [snip] |
10 |
> |
11 |
> Yea gods, the youth of today. In my day, when I was a little whipper-snapper, |
12 |
> we actually read the ebuild. Why because? Because there was no-one else around |
13 |
> to do our looking by proxy for us! |
14 |
> |
15 |
> So, in the interest of decomming the proxy in my head, herewith the magic |
16 |
> incantations to make your problem go "Poof!" and disappear: |
17 |
> |
18 |
> Firstly, you have tools to help. equery, euse, and many more. Learn how to use |
19 |
> them, and use them. |
20 |
> |
21 |
> Secondly, read the ebuild. portage does what the ebuild says so the master |
22 |
> reference to figure out why portage wants to do something is in the ebuild (or |
23 |
> eclasses that it inherits). |
24 |
> |
25 |
> |
26 |
>> * "bsddb" module is out-of-date and no longer maintained inside |
27 |
>> dev-lang/python. It has |
28 |
>> * been additionally removed in Python 3. You should use external, |
29 |
>> still maintained "bsddb3" |
30 |
>> * module provided by dev-python/bsddb3 which supports both Python 2 |
31 |
>> and Python 3. |
32 |
>> * |
33 |
>> * ERROR: dev-lang/python-2.5.4-r4 failed. |
34 |
>> * Call stack: |
35 |
>> * ebuild.sh, line 49: Called pkg_setup |
36 |
>> * python-2.5.4-r4.ebuild, line 64: Called built_with_use |
37 |
>> 'pkg_setup' 'pkg_setup' |
38 |
>> * eutils.eclass, line 1862: Called die |
39 |
>> * The specific snippet of code: |
40 |
>> * die) die "$PKG does not |
41 |
>> actually support the $1 USE flag!";; |
42 |
>> * The die message: |
43 |
>> * sys-devel/gcc-4.1.2 does not actually support the libffi USE flag! |
44 |
>> |
45 |
> From the ebuild: |
46 |
> pkg_setup() { |
47 |
> if use berkdb; then |
48 |
> ewarn "\"bsddb\" module is out-of-date and no longer |
49 |
> maintained inside dev-lang/python. It has" |
50 |
> ewarn "been additionally removed in Python 3. You should use |
51 |
> external, still maintained \"bsddb3\"" |
52 |
> ewarn "module provided by dev-python/bsddb3 which supports |
53 |
> both Python 2 and Python 3." |
54 |
> fi |
55 |
> |
56 |
> if built_with_use sys-devel/gcc libffi; then |
57 |
> die "Reinstall sys-devel/gcc with \"libffi\" USE flag |
58 |
> disabled" |
59 |
> fi |
60 |
> } |
61 |
> |
62 |
> |
63 |
> So, to get rid of the bsddb ewarn, you need to remove that "berkdb" from USE. |
64 |
> |
65 |
> And the build failure is staring you right there in the face. As we say here |
66 |
> at the tip of Africa, "As dit 'n slang was, het dit jou gepik" [If it were a |
67 |
> snake, it would have already bitten you]. |
68 |
> |
69 |
> |
70 |
> You have "USE=libffi" which doesn't work. Remove it, sync the tree, rebuild |
71 |
> world. (your portage and gcc versions have updates available, even on stable) |
72 |
> |
73 |
> |
74 |
> |
75 |
> |
76 |
How do i unsubscribe from the list? I love it, but i subscribed in error |
77 |
and I cant seem to stop it! |