Displaying 3 results from an estimated 3 matches for "000030f4".
Did you mean:
000000f4
2004 Sep 10
3
patches for flac build
> > > Unfortunately, there is a bigger problem that affects both SDL
> > > and FLAC,
> > > which is that the assembly routines are not PIC.
> >
> > It's not? I think all the IA32 code only references data on the
> > stack, and
> > it doesn't call outside the library or export any functions outside
> > the
> > library. The
2004 Sep 10
0
patches for flac build
...at causes this problem is linking with ``gcc
N: -Wl,-shared'' instead of ``gcc -shared''.
N: Refer to Policy Manual, section 11.2 for details.
N:
This is triggered by the presence of a rel.text section in the shared object
as reported by objdump -h:
5 .rel.text 00000020 000030f4 000030f4 000030f4 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
Whereas the rest of the code lives in a plain old .text section. If you look
at other shared libraries, like libc, you see no rel.text section, only .text.
I believe the rationale for this is that relocation causes...
2004 Sep 10
2
patches for flac build
...> N: -Wl,-shared'' instead of ``gcc -shared''.
> N: Refer to Policy Manual, section 11.2 for details.
> N:
>
> This is triggered by the presence of a rel.text section in the shared
> object
> as reported by objdump -h:
>
> 5 .rel.text 00000020 000030f4 000030f4 000030f4 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
>
> Whereas the rest of the code lives in a plain old .text section. If
> you look
> at other shared libraries, like libc, you see no rel.text section,
> only .text.
> I believe the rationale...