| 1 |
On 3/21/06, m h <sesquile@×××××.com> wrote: |
| 2 |
> ARGHHH! |
| 3 |
> |
| 4 |
> gcc bombs out on me now! (internal compiler error) |
| 5 |
> I'm running RHEL 4 under vmware. I guess I need to try on bare hardware.... |
| 6 |
> |
| 7 |
> I'm assumming no one else has run into this? |
| 8 |
> |
| 9 |
> emerge -av gcc |
| 10 |
> |
| 11 |
|
| 12 |
My initial attempt to fix this was to try and install binutils |
| 13 |
(instead of providing it). In order to do so, I had to add the |
| 14 |
binutils-config ebuild into the tree. To do that I needed to add |
| 15 |
EAPI="prefix" which caused the digest check to fail. To recreate the |
| 16 |
digest I needed pycrypto. So I tried installing pycrypto, which |
| 17 |
failed. |
| 18 |
|
| 19 |
>>> Compiling source in |
| 20 |
/tmp/Mar20/var/tmp/portage/pycrypto-2.0.1/work/pycrypto-2.0.1 ... |
| 21 |
python: error while loading shared libraries: libpython2.4.so.1.0: |
| 22 |
cannot open shared object file: No such file or directory |
| 23 |
|
| 24 |
!!! ERROR: dev-python/pycrypto-2.0.1 failed. |
| 25 |
Call stack: |
| 26 |
ebuild.sh, line 1658: Called dyn_compile |
| 27 |
ebuild.sh, line 1056: Called src_compile |
| 28 |
ebuild.sh, line 1368: Called distutils_src_compile |
| 29 |
|
| 30 |
!!! compilation failed |
| 31 |
!!! If you need support, post the topmost build error, and the call |
| 32 |
stack if relevant. |
| 33 |
|
| 34 |
--------------------- |
| 35 |
Apparently (according to strace) python is looking for the 2.4 |
| 36 |
libraries (libpython2.4.so.1.0) in /usr/lib instead of |
| 37 |
${PREFIX}/usr/lib... |
| 38 |
|
| 39 |
|
| 40 |
Guess I'll try the bare hardware route.... |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-osx@g.o mailing list |
Archives