[gccsdk] Unable to load Shared library with GCC 220.127.116.11
leenoar at sky.com
Mon Jun 29 09:30:03 PDT 2015
On 28/06/15 20:34, pdmiller at pdmiller1.plus.com wrote:
> On Sun, June 28, 2015 8:00 pm, Lee Noar <leenoar at sky.com> wrote:
>>> The path variable DRW: is set to
>>> This setup works when compiling, linking and loading using GCC 4.1.2.
>>> Has anything changed in GCC 18.104.22.168 that means I need to change my
>>> library scheme to work with GCC 22.214.171.124?
>> I can't see anything that would prevent a library name prefixed with
>> a path variable from working in a symlink. I did make some changes to
>> where the dynamic linker searches for libraries to support VFP, but
>> that's before symlink processing.
>> Where are the symlink files stored?
> They are copied to RAM::RamDisc0.$.Resources.!DRWDEF.DRW. during system
> The shared library itself happens to be in the same library.
> I set an <appname>$LD$ENV variable for each application that uses the
> library. It is usually just set to "LD_LIBRARY_PATH=DRW:" but can also
> include path variables to any application specific shared libraries.
It looks like I may have made a mistake in r6733 from about a year ago
when dealing with LD_LIBRARY_PATH.
If I email you a new dynamic linker, can you try it and see if it fixes
More information about the gcc