From: Mahesh Bodapati <maheshbodapati90@gmail.com>
To: Felix Fietkau <nbd@openwrt.org>, musl@lists.openwall.com
Subject: Re: musl mips n64 dynamic build
Date: Fri, 22 Jan 2016 13:21:00 +0530 [thread overview]
Message-ID: <CAKd0kD+cuBqn3T=292aUS9p9QSDbBbfs3RB8xHrEVotmQzG8ZQ@mail.gmail.com> (raw)
In-Reply-To: <56A12D5F.6070407@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
yes,This is working.MIPS64 relocation type is a combination of 3 relocation
types each of size 1 byte.
typedef struct
{
Elf32_Word r_sym; /* Symbol index */
unsigned char r_ssym; /* Special symbol for 2nd relocation */
unsigned char r_type3; /* 3rd relocation type */
unsigned char r_type2; /* 2nd relocation type */
unsigned char r_type1; /* 1st relocation type */
} _Elf64_Mips_R_Info;
(R_MIPS_64 << 8) | R_MIPS_REL32 is (18 << 8) | 3 = 4611
Thanks,
Mahesh
On Fri, Jan 22, 2016 at 12:41 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> On 2015-10-27 02:30, Rich Felker wrote:
> > On Tue, Oct 20, 2015 at 12:40:21PM +0200, Szabolcs Nagy wrote:
> >> * Mahesh Bodapati <maheshbodapati90@gmail.com> [2015-10-20 15:14:04
> +0530]:
> >> > Error relocating libc.so: unsupported relocation type 4611
> >> > Error relocating libc.so: unsupported relocation type 4611
> >> > Error relocating libc.so: unsupported relocation type 4611
> >> ....
> >> > *#define REL_SYM_OR_REL R_MIPS_64 /*I didn't see
> R_MIPS_REL64 so
> >> > It is a composition of R_MIPS_64 and R_MIPS_REL relocations but i
> didn't
> >> > see R_MIPS_REL in elf.h. *
> >> > *
> >> > how can i define REL_SYM_OR_REL for mips n64 abi */*
> >>
> >> i don't know what the n64 abi docs says, but this might be a hint:
> >>
> >> glibc/sysdeps/mips/dl-machine.h has
> >>
> >> #if _MIPS_SIM == _ABI64
> >> case (R_MIPS_64 << 8) | R_MIPS_REL32:
> >> #else
> >> case R_MIPS_REL32:
> >> #endif
> >>
> >> where R_MIPS_64 << 8 | R_MIPS_REL32 is 4611.
> >
> > This seems right. Mahesh, did you get a chance to try this? Does it
> > help?
> Manesh, any update on this? I'm really interested in musl MIPS64 support
> for OpenWrt - I'd like to move away from glibc for that arch.
> I can also help with testing and bugfixing once this is getting
> somewhere...
>
> Thanks,
>
> - Felix
>
[-- Attachment #2: Type: text/html, Size: 3023 bytes --]
next prev parent reply other threads:[~2016-01-22 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 9:21 Mahesh Bodapati
2015-10-19 11:02 ` Szabolcs Nagy
2015-10-19 15:18 ` Rich Felker
2015-10-20 9:44 ` Mahesh Bodapati
2015-10-20 10:40 ` Szabolcs Nagy
2015-10-27 1:30 ` Rich Felker
2016-01-21 19:11 ` Felix Fietkau
2016-01-22 7:51 ` Mahesh Bodapati [this message]
2016-01-22 14:13 ` Szabolcs Nagy
2016-01-27 6:47 ` Mahesh Bodapati
2016-01-28 0:08 ` Rich Felker
2016-01-28 11:29 ` Mahesh Bodapati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKd0kD+cuBqn3T=292aUS9p9QSDbBbfs3RB8xHrEVotmQzG8ZQ@mail.gmail.com' \
--to=maheshbodapati90@gmail.com \
--cc=musl@lists.openwall.com \
--cc=nbd@openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).