From: Keith Owens <kaos@melbourne.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: insmod hates RELA?
Date: Fri, 06 Oct 2000 21:57:02 +1100 [thread overview]
Message-ID: <22488.970829822@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 06 Oct 2000 12:26:28 +0200." <Pine.GSO.3.96.1001006121819.26752C-100000@delta.ds2.pg.gda.pl>
On Fri, 6 Oct 2000 12:26:28 +0200 (MET DST),
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl> wrote:
> The linker tends to create empty .rela sections even if there is no input
>for them. This actually is a minor error and until (unless) we modify the
>linker just use the quick fix for modutils that is available from my FTP
>site (not that these modutils actually work ;-) ).
Against modutils 2.3.17. Does 2.3.17+this patch work on mips?
Index: 18.2/obj/obj_load.c
--- 18.2/obj/obj_load.c Fri, 08 Sep 2000 16:46:27 +1100 kaos (modutils-2.3/21_obj_load.c 1.7 644)
+++ 18.2(w)/obj/obj_load.c Fri, 06 Oct 2000 21:45:44 +1100 kaos (modutils-2.3/21_obj_load.c 1.7 644)
@@ -151,11 +151,13 @@ obj_load (int fp, Elf32_Half e_type, con
#if SHT_RELM == SHT_REL
case SHT_RELA:
- error("RELA relocations not supported on this architecture");
+ if (sec->header.sh_size)
+ error("RELA relocations not supported on this architecture");
return NULL;
#else
case SHT_REL:
- error("REL relocations not supported on this architecture");
+ if (sec->header.sh_size)
+ error("REL relocations not supported on this architecture");
return NULL;
#endif
next prev parent reply other threads:[~2000-10-06 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39DCDBA0.8EED1CBD@ridgerun.com>
2000-10-06 2:51 ` insmod hates RELA? Ralf Baechle
2000-10-06 10:26 ` Maciej W. Rozycki
2000-10-06 10:57 ` Keith Owens [this message]
2000-10-06 12:05 ` Maciej W. Rozycki
2000-10-06 13:22 ` Gordon McNutt
2000-10-06 13:22 ` Gordon McNutt
2000-10-06 13:51 ` Keith Owens
2000-10-06 14:52 ` Gordon McNutt
2000-10-06 14:52 ` Gordon McNutt
2000-10-06 15:14 ` 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=22488.970829822@ocs3.ocs-net \
--to=kaos@melbourne.sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox