Re: how to solve a non pic code in an shlib due to assembly code
Ove Kaaven <email@example.com> writes:
> However, if they can't or won't fix it, there's *some* good news. In
> general, shared libraries must be compiled as PIC because on some
> platforms, the library just won't work properly if you don't. However,
> i386 and amd64 are not among those platforms. Since the MMX code is only
> compiled for those, it might be safe to ignore the lintian error in this
> particular case, if there's no other way.
Slight correction for the books. No insult intended. Amd64 is verry
much among those. You usualy end up with a 4 byte offset that is
computed at runtime link time. But with a shared library there is no
garanty that the offset will fit in 4 bytes and during compile time
the linker will complain about a 32bit offset being used where 64bit
might be needed. Sorry, don't know the exact error message by hard.
So there is good and bad news. You can generally ignore the lintian
error if you can compile and use some application with it.