Dennis Clarke wrote:
ELF Header ei_magic: { 0x7f, E, L, F } ei_class: ELFCLASS32 ei_data: ELFDATA2LSB ei_osabi: ELFOSABI_SOLARIS ei_abiversion: EAV_SUNW_CURRENT e_machine: EM_386 e_version: EV_CURRENT e_type: ET_EXEC e_flags: 0 e_entry: 0x8056800 e_ehsize: 52 e_shstrndx: 36 e_shoff: 0x6a5d0 e_shentsize: 40 e_shnum: 37 e_phoff: 0x34 e_phentsize: 32 e_phnum: 6Anyone know what "ELFOSABI_SOLARIS" is ?
Well, yes... When I enter ELFOSABI_SOLARIS into google, the first hit is the Nevada CR under which it was integrated, and the second is the PSARC case. If you read the PSARC case, you'll see that ei_osabi and ei_abiversion are ELF header fields that have always been there, which we have begun to tag correctly for our platform, and which are ignored by the runtime. Since they're ignored by ld.so.1, this shouldn't be a concern. Has this change caused a problem?
Well what happens if you take that binary and try to run it on Solaris 10?
You can take an old object to a new system (which you also discuss), but taking an object built on a new system to run on an older system has never been supported as far as I know. I'm confused about what you're trying to show with this point. Regards.... - Ali _______________________________________________ opensolaris-discuss mailing list [email protected]
