Compile shared library with link to other .so

Question

I want to link an existing shared library (FlashRuntimeExtensions.so) to my C-code while compiling my own shared library. But whatever I try I always get the same error; that the file is in a wrong format. Does anybody have an idea on how to solve this?

Here is my compile command:

$ g++ -Wall ane.c FlashRuntimeExtensions.so -o aneObject FlashRuntimeExtensions.so: could not read symbols: File in wrong format collect2: ld gaf exit-status 1 terug

$ file FlashRuntimeExtensions.so what's the output of this command ? — SirDarius
– SirDarius, Commented Dec 13, 2012 at 9:04
@SirDarius: FlashRuntimeExtensions.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, stripped — Wessel van der Linden
– Wessel van der Linden, Commented Dec 13, 2012 at 9:14
@tsurko Yes but I am not sure about the cross-compiling. I just want to compile a shared library that can be used on Android devices. — Wessel van der Linden
– Wessel van der Linden, Commented Dec 13, 2012 at 9:20

SirDarius · Accepted Answer · 2012-12-13 10:15:57Z

Your command line tries to generate x86 code and link it to ARM code using the native g++ available in your distribution.

This will not work. Use the Android NDK available here: http://developer.android.com/tools/sdk/ndk/index.html

The NDK includes a set of cross-toolchains (compilers, linkers, etc..) that can generate native ARM binaries on Linux, OS X, and Windows (with Cygwin) platforms.

Community · Accepted Answer · 2017-05-23 10:32:17Z

0

In general .so will be linked using -l.

for example, pthread -lpthread we use.

gcc sample.c -o myoutput -lpthread

But as per @chill's statement, what you are doing in command is correct only.

I suggest you to refer the following link.

C++ Linker Error SDL Image - could not read symbols

edited May 23, 2017 at 10:32

CommunityBot

11 silver badge

answered Dec 13, 2012 at 9:05

Jeyaram

9,5847 gold badges44 silver badges65 bronze badges

3 Comments

chill Over a year ago

The OP command line by itself is perfectly OK. There's no such requirement to link libraries (shared or not) only using -l option.

Wessel van der Linden Over a year ago

Hmm when I try that it gives me the error that it can not find the specified library, even if I specify the path with the -L option.. But it could be a compatibility problem reading from the link.

Wessel van der Linden Over a year ago

When I try to compile it as a 32 bit library with the -m32 option the result is not different from the previous result

Naseef Chowdhury · Accepted Answer · 2013-04-22 08:47:38Z

It should be an architecture mismatch. I faced this problem once, I have solved it by building the libs in same target platform and it is obvious. If you are using linux or Unix like OS you can see that by file command and if you are using windows you can see that using Dependency Walker. You need to make sure that all the libs matches architecture.

Collectives™ on Stack Overflow

Compile shared library with link to other .so

3 Answers 3

Comments

3 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

3 Comments

Comments

Linked

Related