| To: | Rajat Jain <rajat.noida.india@gmail.com> |
|---|---|
| Subject: | Re: 0 function size |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Mon, 5 Mar 2007 16:27:45 +0000 |
| Cc: | Alexander Sirotkin <demiourgos@gmail.com>, linux-mips@linux-mips.org |
| In-reply-to: | <b115cb5f0703050821v50667580oa8dfa26412c05b08@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <c4357ccd0703050619r6b5a7452j6b582687bf1794d3@mail.gmail.com> <b115cb5f0703050821v50667580oa8dfa26412c05b08@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.2i |
On Mon, Mar 05, 2007 at 09:51:25PM +0530, Rajat Jain wrote: > Are you using a native compiler or a cross compiler? > > If you are using a cross compiler, then you need to use the "cross > compiler" version of objdump / readelf utilities as well. For > instance if you are using mips-linux-gcc to compile, then you need > mips-linux-readelf / mips-linux-objdump etc. In general your're right but for this particular purpose for example an i386-linux-objdump will do the job for 32-bit big and little endian MIPS ELF. It will - depending on the exact binutils configuration - fail with an error message for 64-bit ELF. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 0 function size, Ralf Baechle |
|---|---|
| Next by Date: | Re: 0 function size, Alexander Sirotkin |
| Previous by Thread: | Re: 0 function size, Rajat Jain |
| Next by Thread: | Re: 0 function size, Alexander Sirotkin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |