From: Sam Ravnborg <sam@ravnborg.org>
To: Miles Bader <miles@gnu.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Embed __this_module in module itself.
Date: Wed, 8 Jan 2003 21:56:45 +0100 [thread overview]
Message-ID: <20030108205645.GA4037@mars.ravnborg.org> (raw)
In-Reply-To: <buoadid1pxl.fsf@mcspd15.ucom.lsi.nec.co.jp>
On Tue, Jan 07, 2003 at 02:36:54PM +0900, Miles Bader wrote:
> Miles Bader <miles@lsi.nec.co.jp> writes:
> > When I try to build modules using 2.5.54, the resulting .ko files lack
> > the .gnu.linkonce.* sections, which causes the kernel module loader to
> > fail on them -- those sections _are_ present in the .o files, but the
> > linker apparently removes them!
>
> Ok, I found out why this is happening -- the v850 default linker
> scripts, for whatever reason, merge any section called `.gnu.linker.t*'
> with .text.
ld per default uses a default linker-scripts as you note.
Could another solution be to provide a fixed linker script, used for all
invocations of ld?
LDFLAGS += -T arch/v850/v850.lds
Not knowing much about v850, I wonder why you do not need to set the -m
option. Most other architectures do this.
Sam
next prev parent reply other threads:[~2003-01-08 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 10:25 [PATCH] Embed __this_module in module itself Rusty Russell
2003-01-06 11:03 ` Miles Bader
2003-01-07 5:36 ` Miles Bader
2003-01-08 11:51 ` Rusty Russell
2003-01-08 20:56 ` Sam Ravnborg [this message]
2003-01-09 1:18 ` Miles Bader
2003-01-09 18:49 ` Sam Ravnborg
2003-01-09 19:16 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 8:38 Rusty Russell
2002-12-23 9:21 ` David S. Miller
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=20030108205645.GA4037@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=rusty@rustcorp.com.au \
/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