[ELDK] ld.so.1 needed by libpthread.so.0 not found

[Larry Baker]

Ed,

I do not understand why the version of SUSE has anything to do with your linker failure.  Your cross-development environment should be compiling with target headers and linking with target static and shared libraries only.  Those should all be contained in the ELDK 3.1.1 cross-development kit -- they have nothing to do with the host O/S release.  I suspect your environment variables or configure commands from the original system are not quite the same as the ones you are using on your new system.  That could explain, for example, why the linker could not locate the ld.so.1 it was looking for.  If this is the true cause of your link failure, then you will encounter this linker error on any system you build -- old or new x86/x86_64 Linux release -- that does not search for the proper target system libraries.  Pay special attention that you are compiling with the proper headers for your target system.  You won't typically get compile-time errors when you use the wrong headers.  But, as you know, PPC and x86 are different endian architecture, which must be properly defined in the header files.

Larry Baker
US Geological Survey
650-329-5608
baker at usgs.gov



On 24 Jan 2014, at 6:59 AM, Ed Jubenville wrote:

> Hi Wolfgang,
> 
> Thanks for the suggestions.  Updating to the latest ELDK for that particular project is not an option because the project is in maintenance mode.  We are obligated to do bug fixes and minor enhancements on products that have already shipped.  We have an infrastructure for easily updating the application software in the field, but not the whole kernel, ramdisk, etc..
> 
> I will pursue your other suggestion of using an older SUSE in the VM, as that is what runs in the original development hardware.
> 
> Thanks again,
> Ed
> 
> -----Original Message-----
> From: Wolfgang Denk [mailto:wd at denx.de] 
> Sent: Friday, January 24, 2014 12:34 AM
> To: Ed Jubenville
> Cc: eldk at lists.denx.de
> Subject: Re: [ELDK] ld.so.1 needed by libpthread.so.0 not found
> 
> Dear Ed,
> 
> In message <016901cf18a2$6d8e13b0$48aa3b10$@att.net> you wrote:
>> 
>> I have a very old project in maintenance mode, based on the IceCube 
>> board built upon ELDK 3.1.1.  I am trying to move the development 
>> environment to a new PC running SUSE Linux 3.11.6.  I installed the 
>> ELDK using the same ISO image and instructions that I had used many 
>> years ago.  My application compiled fine, but wouldn't link due to 
>> undefined references.  I found that even a simple empty main() program would produce these errors:
> 
> You cannot really expect to run 9 (in words: nine!) year old software in the context of a recent operating system.  dependign on your requirements you should chose between two options:
> 
> - Update the development environment to a recent version of the ELDK,
>  that supports your (also recent) OS environment.
> 
> - Stick with the old development tools, and run it under an OS that
>  was recent at the time of the release; if you prefer SuSE, then ELDK
>  v3.1.1 (Release date March 2005) should behave fine with SuSE 9.x
>  (release dates from Oct 2003 [SuSE 9.0] ... Apr 2005 [SuSE 9.3]).
> 
>  If needed, install a virtual machine on your development host, where
>  you can then run the older SuSE distro code.  I am aware that there
>  will be a performance penalty, but that will still save you lots of
>  time compared to trying to get the ancient code running in a current
>  distro.
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> You can do this in a number of ways.     IBM chose to do all of them.
> Why do you find that funny?        -- D. Taylor, Computer Science 350
> 
> _______________________________________________
> eldk mailing list
> eldk at lists.denx.de
> http://lists.denx.de/mailman/listinfo/eldk