2

I'm trying to cross-compile arm assembly code which is using shared library that's located in : /system/lib/libxyz.so (on host device), and using dynamic linker: /system/bin/linker - which is also located on host device.

So I compile:

arm-eabi-gcc -mcpu="cortex-a9"  -Wl,-dynamic-linker=/system/bin/linker -llibxyz.so -Wl,--unresolved-symbols=ignore-all -nostdlib topsecret.S -o topsecret

I also use:

-Wl,--unresolved-symbols=ignore-all

To ignore any undefined symbols as I dont really have them when compiling - I'm taking on the asm code the calling of right addresses.

The trivial error I'm getting is : 

arm-eabi/bin/ld cannot find -llibxyz.so, collect2: ld returned 1 exit status

And I dont actally want to have the libxyz.so library, I want the compiler to ignore the error, and add the dependency to the ELF Header. I tried -Wl,--no-as-needed, -Wl,--as-needed arguments but that didn't help.

The question is if I can either ignore the error, fake the library, or any other solution which will give me good binary that has the dependency in the header.

Link shared library in gcc without file? This solution is not good because I dont want to change the asm code, only the compiling mechanism.

Community
  • 1
  • 1
skoperst
  • 2,259
  • 1
  • 23
  • 35
  • 1
    Sorry, but what you want to do is not possible. The linker wants to see the shared library so it knows which symbols are defined there and which are not; it needs to know that to understand how the linkage will work. You'll have to copy the target's shared library to your development system, or else use explicit loading as suggested in the answer you reference (dlopen etc.) and create the linkage yourself with dlsym(). – MadScientist Jan 14 '14 at 15:05
  • 2
    You can transfer the file from *host* to *build*. If you cann't do this, then there is no way for the linker to know which library an un-resolved symbol exists in. You can create a fake *host* library with shims for implementation. This will work even if you can not transfer the *host* library (host locked down or something). This will allow you to link on the build machine and it should patch to the full implementation on the *host* by its loader. – artless noise Jan 14 '14 at 16:48
  • MadScientist: Thanks for the answer. What you say is probably going to work. If there will be no other 'hacky' solution, I'll use dlload/dlsym api. artless noise: Thank you for your answer, Thats also good option that can save alot of time. The only downside is that I need to create/maintain those fake libraries whenever I want to do the 'special linking' operation. I'll consider this unless theres no other way to force linking. Thank you. – skoperst Jan 14 '14 at 16:51
  • 1
    Isn't the format like '-L. -lxyz'? – auselen Jan 14 '14 at 19:03
  • Thank you for the answer.But thats not going to work, thats just path . to the lib dir . I dont actually have the libs anywhere. – skoperst Jan 16 '14 at 20:05
  • Looks like duplicate of [linux - Is it possible to link to a shared library without access to the library itself? - Stack Overflow](https://stackoverflow.com/questions/45014588/is-it-possible-to-link-to-a-shared-library-without-access-to-the-library-itself?noredirect=1&lq=1) but the situation here looks more specific – user202729 Nov 18 '22 at 20:19

1 Answers1

1

Sorry, but what you want to do is not possible. The linker wants to see the shared library so it knows which symbols are defined there and which are not; it needs to know that to understand how the linkage will work. You'll have to copy the target's shared library to your development system, or else use explicit loading as suggested in the answer you reference (dlopen etc.) and create the linkage yourself with dlsym(). – MadScientist

You can transfer the file from host to build. If you cann't do this, then there is no way for the linker to know which library an un-resolved symbol exists in. You can create a fake host library with shims for implementation. This will work even if you can not transfer the host library (host locked down or something). This will allow you to link on the build machine and it should patch to the full implementation on the host by its loader. – artless noise

Armali
  • 18,255
  • 14
  • 57
  • 171