Hi Alan, Sorry for the inconvenience. Forwarding the thread to your correct e-mail id once again.
----- Forwarded message from Mohan Kumar M <[EMAIL PROTECTED]> ----- Date: Tue, 1 Aug 2006 20:52:31 +0530 From: Mohan Kumar M <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Fastboot] .rela.opd sections in PPC64 Reply-To: [EMAIL PROTECTED] Hi Alan, As per kexec requirement, purgatory code is compiled with relocatable option and during the runtime of kexec-tools, we apply the relocation to the purgatory code based on the load address. But the relocatable object file contains some of STN_UNDEF entries in the .rela.opd section. However .rela.text section does not have any STN_UNDEF entries. We linked all the object files and hence there is no *undefined symbols* in the final purgatory object file. Even though the .rela.opd section has undefined entries, we skipped applying relocation for these entries and the code is working as expected. But we need to fix this STN_UNDEF issue in the PPC64 code. Can you tell me how I can resolve the STN_UNDEF entries in the .rela.opd section? I am attaching the partial output from 'readelf -r purgatory.ro' for your reference. Relocation section '.rela.text' at offset 0x9558 contains 69 entries: Offset Info Type Sym. Value Sym. Name + Addend 000000000160 004a0000000a R_PPC64_REL24 0000000000000708 .sha256_starts + 0 00000000016a 00070000003f R_PPC64_TOC16_DS 0000000000000000 .toc + 0 Relocation section '.rela.opd' at offset 0x9bd0 contains 30 entries: Offset Info Type Sym. Value Sym. Name + Addend 0000000000b0 004a00000026 R_PPC64_ADDR64 0000000000000708 .sha256_starts + 0 0000000000b8 000000000033 R_PPC64_TOC 0000000000000000 Regards, Mohan. _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot ----- End forwarded message ----- _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
