From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: kkeil@suse.de, mac@melware.de
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: missing memset in divas and eicon in 2.2.20
Date: Tue, 22 Jan 2002 00:36:09 +0100 (MET) [thread overview]
Message-ID: <200201212336.g0LNa9b25643@oboe.it.uc3m.es> (raw)
betty:/usr/local/src/linux-2.2.20% sudo depmod -ae -F System.map 2.2.20-SMP
depmod: *** Unresolved symbols in
/lib/modules/2.2.20-SMP/misc/divas.o depmod: memset
depmod: *** Unresolved symbols in
/lib/modules/2.2.20-SMP/misc/eicon.o depmod: memset
Both compiled as modules, SMP kernel, i686 compile. No, I didn't make a
patch - I was too busy fighting with sct's patch for ext3, which is also
slightly toasted in the deendencies department when compiled as a
module.
I don't know why these are missing memset. Of course memset is in the
kernel and nobody else misses it one bit! Yes, they do include at least
some header that incorporates memset (from linux/strings.h? Or in
asm-i386?), because I tried copying an inline memset.h definition into
their header files, and it produced a typical compiler error ("error
before '?' .." sic) from a memset macro clash. One of the component
sources of divas.o and eicon.o must be missing an #include
<asm/strings.h>.
Your mission is to find and eliminate that missing include.
Good luck.
---------------------------------------------------------------------
Peter T. Breuer MA CASM PhD (Ing.), Prof. Asoc.
Area de Ingenieria Telematica E-mail: ptb@it.uc3m.es
Dpto. Ingenieria Tel: +34 (9)1 624 87 81
Universidad Carlos III de Madrid Fax: +34 (9)1 624 8749/9430
Butarque 15, Leganes/Madrid URL: http://www.it.uc3m.es/~ptb
E-28911 Spain Mob: +34 69 666 7835
next reply other threads:[~2002-01-21 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 23:36 Peter T. Breuer [this message]
2002-01-22 9:19 ` Armin Schindler
2002-01-22 10:43 ` Keith Owens
2002-01-22 12:00 ` Peter T. Breuer
2002-01-22 12:07 ` Peter T. Breuer
2002-01-22 13:28 ` Armin Schindler
2002-01-22 11:29 ` Karsten Keil
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=200201212336.g0LNa9b25643@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
/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®