| 1 |
Douglas Campos wrote: |
| 2 |
> I've found that using gcc-3.4.4-r1 made a lot of python modules going |
| 3 |
> with "unresolved symbols", even when they compiled shamelessly |
| 4 |
> |
| 5 |
> I switched to gcc-3.3.6 and then everything went right! |
| 6 |
|
| 7 |
Well I have had no such luck. :-( |
| 8 |
|
| 9 |
I set up an alternate root and switched it to gcc-3.3.6, emerged |
| 10 |
Subversion, but still got an unresolved symbol error with the Python |
| 11 |
bindings. I updated to python 2.4 (since the stage only has 2.3), which |
| 12 |
successfully compiled but now python2.4 itself dies with |
| 13 |
|
| 14 |
/usr/bin/python: can't resolve symbol 'dl_iterate_phdr' |
| 15 |
|
| 16 |
I guess for some reason, gcc, python, and uclibc are not playing nicely |
| 17 |
together, at least not on my system, and I lack the necessary skills to |
| 18 |
figure out exactly what's going on ... |
| 19 |
|
| 20 |
I'm really starting to wish that there were a big-endian ARM stage |
| 21 |
available that uses regular old glibc, I expect that would eliminate all |
| 22 |
these problems ... |
| 23 |
|
| 24 |
-- |
| 25 |
Dan C <djc@××××××.au> |
| 26 |
-- |
| 27 |
gentoo-embedded@g.o mailing list |
Archives