From: Keith Owens <kaos@ocs.com.au>
To: "Ph. Marek" <marek@mail.bmlv.gv.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.[01] and duron - unresolved symbol _mmx_memcpy
Date: Tue, 13 Feb 2001 18:23:13 +1100 [thread overview]
Message-ID: <1151.982048993@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 13 Feb 2001 07:47:33 BST." <3.0.6.32.20010213074733.00917210@pop3.bmlv.gv.at>
On Tue, 13 Feb 2001 07:47:33 +0100,
"Ph. Marek" <marek@mail.bmlv.gv.at> wrote:
>and the modules dependencies are not all set!
>make modules_install does not check for modules compilation - says
>"cp: file not found". I think that's because modules_install doesn't
>depend on the modules
Correct. The current recursive makefile design means it is difficult
to get a definitive list of modules without excessive overhead. So
modules_install assumes that you have compiled the modules already and
lets the 'cp' command fail. The 2.5 Makefile redesign will get this
right.
>grep _mmx_memcpy /proc/ksyms
> c01a4e20 _mmx_memcpy_R__ver__mmx_memcpy
Broken 2.4 makefile design. http://www.tux.org/lkml/#s8-8
The 2.5 makefile redesign will kill this problem once and for all.
next prev parent reply other threads:[~2001-02-13 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 7:04 2.4.[01] and duron - unresolved symbol _mmx_memcpy Ph. Marek
2001-02-12 8:49 ` Keith Owens
[not found] ` <Your message of "Mon, 12 Feb 2001 08:04:59 BST." <3.0.6.32.20010212080459.0090ce80@pop3.bmlv.gv.at>
2001-02-13 6:47 ` Ph. Marek
2001-02-13 7:23 ` Keith Owens [this message]
2001-02-12 9:54 ` Jan Niehusmann
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=1151.982048993@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marek@mail.bmlv.gv.at \
/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