Quote:
Originally Posted by twobob
http://people.defora.org/~khorben/place/blog/8
mentions this type of error in clibs on arm.
he also talks about digging into the errors originating code, which would no doubt help. It's beyond my skills.
I assume you have all the relevant kernel symbols in your keychain, although again I am not sure if that is even related to the issue. sorry mate
|
I'm not sure that it's safe to assume that all the relevant kernel symbols are in my keychain -- I don't even know what that means. You guys know way more about this, why am I so ignorant of all these things!? I'll do my homework.
Thanks for your efforts!
Quote:
Originally Posted by knc1
-fPIC
And why does that line show an unadorned "gcc" -
Are you native compiling this thing?
|
I'll give that a shot.
1: I don't know, what is unadorned about the gcc line?
2: Yes I'm native compiling.
Sure appreciate the help
Quote:
Originally Posted by NiLuJe
@projectdp: Oh, right, missed that, sorry  .
Then, yes, +1 on knc1 answer: build the *library* in PIC mode. (If it's using a decent buildsystem, there's a switch, if not, carefully messing around with the *PIC flags). |
Ok awesome I'll try that.
Thanks NiLuJe
