All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Art Haas" <ahaas@airmail.net>
To: sparclinux@vger.kernel.org
Subject: Compiling modules question
Date: Mon, 29 Mar 2004 20:19:01 +0000	[thread overview]
Message-ID: <20040329201901.GD30251@artsapartment.org> (raw)

Hi.

Here's another question for the list that I've not been able to
answer. When I compile a kernel with modules, the modules all have
problems with undefined symbols like 'udiv', 'urem', etc. As
my machine is a 'v8' machine, my solution to resolving this
problem was to edit the makefile and add '-mcpu=v8' in a couple
of places, and things work fine. But, if I had to run my kernel
on a 'v7' machine, things would fail.

In 'arch/sparc/lib' there are routines that provide the missing
functions, so am I missing some step where this library gets linked
into the building of the module? If not, then these missing
functions must get picked up in libc, correct? My ignorance of how
things work in SparcLinux is showing ...

Thanks in advance for any info you can send my way.

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

             reply	other threads:[~2004-03-29 20:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 20:19 Art Haas [this message]
2004-03-29 20:30 ` Compiling modules question David S. Miller
2004-03-29 21:19 ` Keith M Wesolowski
2004-03-29 21:29 ` Jason Wever
2004-03-29 22:42 ` Keith M Wesolowski
2004-03-30  0:21 ` Rusty Russell
2004-03-30  1:35 ` Art Haas
2004-03-30  7:43 ` Keith M Wesolowski
2004-03-30  8:03 ` David S. Miller
2004-03-31  0:18 ` Rusty Russell

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=20040329201901.GD30251@artsapartment.org \
    --to=ahaas@airmail.net \
    --cc=sparclinux@vger.kernel.org \
    /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.