From: Greg Satz <satz@ayrnetworks.com>
To: "H . J . Lu" <hjl@lucon.org>, Ralf Baechle <ralf@oss.sgi.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: SHN_MIPS_SCOMMON
Date: Sat, 21 Jul 2001 12:12:29 -0600 [thread overview]
Message-ID: <B77F222C.888C%satz@ayrnetworks.com> (raw)
In-Reply-To: <20010721104144.A17894@lucon.org>
The problem I ran into was making NFS as a kernel module. The resulting
sunrpc.o module crashed when insmod was run over it. Ralf's fix that all
compiles and links use -G 0 worked for me.
Thanks,
Greg
on 7/21/01 11:41 AM, H . J . Lu at hjl@lucon.org wrote:
> On Sat, Jul 21, 2001 at 02:11:20PM +0200, Ralf Baechle wrote:
>> Only if you don't compile / assemble / link with -G 0.
>>
>> .scommon shouldn't ever be in a kernel object. It seems that ld started
>> to move .common objects to .scommon from a certain version on, so 2.4.5
>
> Send me a testcase. I will fix the linker.
>
>
> H.J.
>
WARNING: multiple messages have this Message-ID (diff)
From: Greg Satz <satz@ayrnetworks.com>
To: "H . J . Lu" <hjl@lucon.org>, Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: SHN_MIPS_SCOMMON
Date: Sat, 21 Jul 2001 12:12:29 -0600 [thread overview]
Message-ID: <B77F222C.888C%satz@ayrnetworks.com> (raw)
Message-ID: <20010721181229.YQf2QxMkI40pVNetrAiKWPDCPyTIISLq-WeahQEWqm4@z> (raw)
In-Reply-To: <20010721104144.A17894@lucon.org>
The problem I ran into was making NFS as a kernel module. The resulting
sunrpc.o module crashed when insmod was run over it. Ralf's fix that all
compiles and links use -G 0 worked for me.
Thanks,
Greg
on 7/21/01 11:41 AM, H . J . Lu at hjl@lucon.org wrote:
> On Sat, Jul 21, 2001 at 02:11:20PM +0200, Ralf Baechle wrote:
>> Only if you don't compile / assemble / link with -G 0.
>>
>> .scommon shouldn't ever be in a kernel object. It seems that ld started
>> to move .common objects to .scommon from a certain version on, so 2.4.5
>
> Send me a testcase. I will fix the linker.
>
>
> H.J.
>
next prev parent reply other threads:[~2001-07-21 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 22:15 SHN_MIPS_SCOMMON Greg Satz
2001-07-20 22:15 ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 1:30 ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 9:22 ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 9:22 ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 12:11 ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 17:41 ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 18:12 ` Greg Satz [this message]
2001-07-21 18:12 ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 18:13 ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 18:56 ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 19:03 ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 23:20 ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 18:55 ` SHN_MIPS_SCOMMON 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=B77F222C.888C%satz@ayrnetworks.com \
--to=satz@ayrnetworks.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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 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.