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