From: Keith Owens <kaos@ocs.com.au>
To: jbglaw@lug-owl.de
Cc: linux-mips@oss.sgi.com
Subject: Re: elf2ecoff problem
Date: Sun, 25 Mar 2001 09:21:56 +1000 [thread overview]
Message-ID: <32583.985476116@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 24 Mar 2001 22:17:58 +0100." <20010324221757.B9810@lug-owl.de>
On Sat, 24 Mar 2001 22:17:58 +0100,
Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>./elf2ecoff /home/jbglaw/kernel_src/work/mips_linux/linux/vmlinux vmlinux.ecoff -a
>Non-contiguous data can't be converted.
> 17 .modinfo 00000018 ffffffff802730a0 ffffffff802730a0 001700a0 2**2
> CONTENTS, ALLOC, LOAD, READONLY, DATA
This may not be relevant but vmlinux should not have a .modinfo
section. .modinfo is only created when code is compiled with -DMODULE
so why is it in vmlinux?
There was a recent change to the attributes of .modinfo, from CONTENTS,
READONLY to CONTENTS, ALLOC, LOAD, READONLY, DATA, this change was to
remove gcc warning messages. insmod treats sections .modinfo and
.modstring as special cases and turns off the SHF_ALLOC flag, elf2ecoff
might need special processing for these sections.
next prev parent reply other threads:[~2001-03-24 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-24 21:17 elf2ecoff problem Jan-Benedict Glaw
2001-03-24 23:21 ` Keith Owens [this message]
2001-03-25 3:35 ` Ralf Baechle
2001-03-26 3:38 ` Keith Owens
2001-03-26 17:19 ` Ralf Baechle
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=32583.985476116@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=jbglaw@lug-owl.de \
--cc=linux-mips@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox