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