From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>,
Richard Sandiford <rsandifo@redhat.com>,
linux-mips@linux-mips.org
Subject: Re: Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5
Date: Tue, 24 May 2005 16:00:08 +0100 [thread overview]
Message-ID: <20050524150008.GC13850@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0505241548330.13738@blysk.ds.pg.gda.pl>
On Tue, May 24, 2005 at 03:50:16PM +0100, Maciej W. Rozycki wrote:
> > The kernel ELF binary is too complicated for objcopy to cope with. Fixing
> > objcopy to handle this case correctly turned out to be hopeless but with
> > a little linker script magic it's possible to keep the kernel vmlinux file
> > within what elf2ecoff can deal with.
>
> Well, it used to work for me the few times I tried, except from that MIPS
> III magic number problem. But that's not a binutils' fault.
That's because you haven't booted 2.6 on DECstations yet ;-) I'm sure
you'll have some elf2ecoff fun ...
Ralf
next prev parent reply other threads:[~2005-05-24 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 7:10 Unmatched R_MIPS_HI16/R_MIPS_LO16 on gcc 3.5 Stanislaw Skowronek
2005-05-23 11:17 ` Richard Sandiford
2005-05-23 16:19 ` Stanislaw Skowronek
2005-05-23 17:23 ` Richard Sandiford
2005-05-23 17:32 ` Stanislaw Skowronek
2005-05-24 6:35 ` Richard Sandiford
2005-05-24 6:39 ` Stanislaw Skowronek
2005-05-24 6:56 ` Richard Sandiford
2005-05-24 6:58 ` Stanislaw Skowronek
2005-05-24 10:40 ` Maciej W. Rozycki
2005-05-24 10:47 ` Stanislaw Skowronek
2005-05-24 11:40 ` Maciej W. Rozycki
2005-05-24 10:50 ` Richard Sandiford
2005-05-24 14:22 ` Ralf Baechle
2005-05-24 14:50 ` Maciej W. Rozycki
2005-05-24 15:00 ` Ralf Baechle [this message]
2005-05-24 15:04 ` Maciej W. Rozycki
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=20050524150008.GC13850@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=rsandifo@redhat.com \
--cc=sskowron@ET.PUT.Poznan.PL \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.