Re: Porting of GLIBC on new platform

[Vivek Takalkar]

Hello Madhvesh

 

Thanks for the last suggestion once again.

 

I would like some more help from your side.

 

This time in the relocation of symbols. For the very first symbol in the test case it is giving error that symbol could not be found in the loaded library. Where as we have verified that symbol is there in the LIBC, which is loaded through the file libc.so.6 

 

We tried to trace out the problem. We found out that it is looking for the required symbol in the test case itself and not going into the dependancies list. Either it is not getting the dependency list or it could not found the required symbol in that. The program is going through the dl-lookup.c and do-lookup.h files and _dl-lookup_versioned_symbol and do_lookup_versioned functions.

 

My opinion is there is some problem in the scope->r_list from where the program should get the required list. I tried to trace back from where this list is being prepared. This list is being prepared and updated in the add_to_global function in the dl-open.c file. I am not getting any clue for call of function __libc_dlopen, from where eventualy this add_to_global is being called.

 

Please guide me if you have any info on this.

 

Thanks in anticipation.

 

VIVEK

----- Original Message -----

From: Madhvesh R S

To: address@hidden

Cc: address@hidden

Sent: Thursday, December 30, 2004 2:46 PM

Subject: 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: address@hidden [mailto:address@hidden
Sent: Thursday, December 30, 2004 3:08 PM
To: address@hidden; address@hidden
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