Re: how to solve a non pic code in an shlib due to assembly code

Ove Kaaven writes: > Goswin von Brederlow skrev: >> Ove Kaaven 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, >>>

Re: how to solve a non pic code in an shlib due to assembly code

Goswin von Brederlow skrev: > Ove Kaaven 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

Re: how to solve a non pic code in an shlib due to assembly code

Ove Kaaven 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

Re: how to solve a non pic code in an shlib due to assembly code

Picca Frédéric-Emmanuel skrev: > Is someone on this mailing have the assembly skills to help me, and the > upstream, solve this problem. > > I already contact the main upstream but it does not know how to > solve this. The idea of position-independent code (PIC) is that no absolute memory offsets

how to solve a non pic code in an shlib due to assembly code

hello, mentors This mail to speak about a problematic issue that I have when packaging a new package for debian tango-7.0.2. http://tango-controls.org you can find this package on mentors: dget http://mentors.debian.net/debian/pool/main/t/tango/tango_7.0.2-1.dsc lintian complain about non pic co