linux-mips
[Top] [All Lists]

Re: Is this a toolchain bug?

To: Matthew Dharm <mdharm@momenco.com>
Subject: Re: Is this a toolchain bug?
From: Daniel Jacobowitz <dan@debian.org>
Date: Mon, 25 Feb 2002 20:13:27 -0500
Cc: Kevin Paul Herbert <kph@ayrnetworks.com>, Linux-MIPS <linux-mips@oss.sgi.com>
In-reply-to: <NEBBLJGMNKKEEMNLHGAIGEMACFAA.mdharm@momenco.com>
References: <a05100303b8a033ebf33b@[192.168.1.5]> <NEBBLJGMNKKEEMNLHGAIGEMACFAA.mdharm@momenco.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.3.23i
On Mon, Feb 25, 2002 at 12:30:38PM -0800, Matthew Dharm wrote:
> Well, that fixes it.  The driver works out-of-the-box with just some
> minor makefile modifications.
> 
> So, we've got a problem somewhere in the module handling.  Either the
> symbol wasn't being relocated properly, or it wasn't being allocated
> properly, or something.  I'm not an expert in this region of the
> kernel, but my guess is that we're going to see this more and more
> often, so someone with a clue should take a look at this.
> 
> I'm more than willing to help, as I seem to be the only person with a
> 100% reproducable situation.  But I really have no idea even where to
> begin looking... my expertise ends right about at objdump, and even
> then I'm not certain how some of that data should look for loadable
> modules.

Silly question... was the module built with the correct flags?  Look at
a command line; does it have all the same options as when you build a
module in the kernel source?

I bet something's missing.  Probably -G 0...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

<Prev in Thread] Current Thread [Next in Thread>