mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Abbey <jonabbey@arlut.utexas.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21-pre6: mmx_memcpy not properly exposed to modules with Athlon
Date: Sun, 30 Mar 2003 04:47:21 -0600	[thread overview]
Message-ID: <20030330104720.GA27518@arlut.utexas.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

I've had a good deal of trouble this evening trying to compile
2.4.21-pre6 for the Athlon processor.  It appears that when the
kernel's bzImage is built all is well, but building modules (for USB)
results in unresolved references to _mmx_memcpy in the modules.

From looking at the System.map file and nm vmlinux, it appears that
the _mmx_memcpy symbol is present and presumably thereby linkable.
I'm not certain why that symbol is not being resolved when I try to
depmod or insmod the USB modules.

I was able to work around the problem by building the bzImage for
Athlon, then doing a make config to switch the processor type to
PIII/Coppermine before building the modules, so that memcpy is not
#define'd to refer to _mmx_memcpy, but this is not a terribly
satisfying workaround.
 
-- 
-------------------------------------------------------------------------------
Jonathan Abbey 				              jonabbey@arlut.utexas.edu
Applied Research Laboratories                 The University of Texas at Austin
Ganymede, a GPL'ed metadirectory for UNIX     http://www.arlut.utexas.edu/gash2

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

             reply	other threads:[~2003-03-30 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30 10:47 Jonathan Abbey [this message]
2003-03-30 14:30 ` Keith Owens

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=20030330104720.GA27518@arlut.utexas.edu \
    --to=jonabbey@arlut.utexas.edu \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®