| 1 |
I've pared down my system to a minimal state. |
| 2 |
|
| 3 |
emerge --depclean returns no actions needed, but I think it may have |
| 4 |
gotten a litte too exuberant. |
| 5 |
|
| 6 |
revdep-rebuild wants to rebuild python but the emerge fails here: |
| 7 |
|
| 8 |
>>> Source unpacked. |
| 9 |
>>> Compiling source in /var/tmp/portage/dev-lang/python-2.5.1-r4/work/Python-2.5.1 . |
| 10 |
.. |
| 11 |
* econf failed |
| 12 |
[...] |
| 13 |
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.5.1- |
| 14 |
r4/temp/environment'. |
| 15 |
* |
| 16 |
|
| 17 |
[...] |
| 18 |
|
| 19 |
* ERROR: dev-lang/python-2.5.1-r4 failed. |
| 20 |
* Call stack: |
| 21 |
|
| 22 |
|
| 23 |
* ebuild.sh, line 46: Called src_compile |
| 24 |
* environment, line 3304: Called econf 'src_compile' 'src_compile' '--w |
| 25 |
ith-fpectl' '--enable-shared' '--disable-ipv6' '--infodir=${prefix}/share/info' '--ma |
| 26 |
ndir=${prefix}/share/man' '--with-libc=' |
| 27 |
* ebuild.sh, line 507: Called die |
| 28 |
* The specific snippet of code: |
| 29 |
* die "econf failed" |
| 30 |
* The die message: |
| 31 |
* econf failed |
| 32 |
|
| 33 |
I'm not finding this line `ebuild.sh 507' or even the file anywhere in |
| 34 |
the build area or elsewhere for that matter. |
| 35 |
|
| 36 |
Not able to devine any clues from: |
| 37 |
/var/tmp/portage/dev-lang/python-2.5.1-r4/temp/environment |
| 38 |
either. |
| 39 |
|
| 40 |
Its not at all clear where the * Call stack leads. At least not to |
| 41 |
me. But apparently it has something to do with src_compile in the |
| 42 |
ebuild. |
| 43 |
|
| 44 |
Anyone recognize this kind of error? |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-user@g.o mailing list |
Archives