This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Porting of GLIBC on new platform


Hi,

>In most of the docs we refered we came across GOT & PLT is being
>resolved
>by the ld.so itself for application  program but for ld.so who does this
>resolution of adresses in the GOT & PLT?
For ld.so also, the self relocation will be done at the beginning
of loader entry point execution. This code has to be written carefully
to avoid any relocations until self relocation completes. Take
a look at the file dl-machine.h and RTLD_START macros

-MS

-----Original Message-----
From: vivek@conjoinsys.com [mailto:vivek@conjoinsys.com]
Sent: Thursday, December 30, 2004 3:08 PM
To: libc-alpha@sources.redhat.com; nug-glibc@gnu.org
Subject: Porting of GLIBC on new platform


Hello

We are trying to port GLIBC 2.2.5 on the ABACUS (processor similar to
SPARC) platform. We have done much of the porting work.

At this stage we are trying to get the 'ld-2.2.5.so' working. We are
facing problems in this. We are trying to run this on again on our own
Linux kernel for ABACUS processor. The GOT & PLT generated through the
GCC
for ld-2.2.5.so is causing the problems.

We need some more information regarding the resolution of the GOT & PLT
at
the run time for ld-2.2.5.so

In most of the docs we refered we came across GOT & PLT is being
resolved
by the ld.so itself for application  program but for ld.so who does this
resolution of adresses in the GOT & PLT?

Please throw some light on this issue.

Thanks & Warm Regards

VIVEK



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]