[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] Microblaze C++ pthreads linking problems

Hi Otto,

Otto Blomqvist wrote:
Just wanted to post an update on the strange linking message mentioned earlier. Using objdump I tracked it down to gets() function calls. Removing all those makes the linking message disappear.
As Falk suggested, I think it's probably a library link order issue. Sometimes I've had to do strange things like add the same -l... option at the start and end of the list, just to resolve strange link order dependencies. No doubt there's a science to it but that's a quick hack that can make it go away. 

Regards,

John
/Otto
On 4/29/08, *Brettschneider Falk* <fbrettschneider@xxxxxxxxxxxxxxx <mailto:fbrettschneider@xxxxxxxxxxxxxxx>> wrote: 

    Hi,

    try to remove your first -lpthread, only use the last one. The
    linker walks the arguments from left to right and will prevent
    linking against all functions which are not seen as used till that
    moment. That's why the base libs should always be placed in the list
    of linker arguments as right as they can be, otherwise the object
    code may be missed in the end.
    I have no idea about your strange warning though...

    CU, Falk

    ___________________________
    microblaze-uclinux mailing list
    microblaze-uclinux@xxxxxxxxxxxxxx
    <mailto:microblaze-uclinux@xxxxxxxxxxxxxx>
    Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
    Mailing List Archive :
    http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/




___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/