From: Dieter Nützel <Dieter.Nuetzel@hamburg.de>
To: Nils Philippsen <nils@fht-esslingen.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Rik Faith <faith@valinux.com>,
Dri-devel <Dri-devel@lists.sourceforge.net>
Subject: Re: test13-preX: DRM (tdfx.o) unresolved symbols fixed?
Date: Thu, 28 Dec 2000 00:50:32 +0100 [thread overview]
Message-ID: <00122800503201.00902@SunWave1> (raw)
In-Reply-To: <Pine.LNX.4.30.0012270951360.21331-100000@rhlx01.fht-esslingen.de>
In-Reply-To: <Pine.LNX.4.30.0012270951360.21331-100000@rhlx01.fht-esslingen.de>
Am Mittwoch, 27. Dezember 2000 11:07 schrieb Nils Philippsen:
> Hi all,
>
> On Wed, 27 Dec 2000, Dieter [iso-8859-1] Nützel wrote:
> > I got this since test13-pre1 (pre4, now):
> >
> > SunWave1>depmod -e
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/tdfx.o
>
> [snipped]
>
> > Something missing in the 'new' drm/Makefile?
>
> From the test13-pre4 patch, the only difference I can see is that shared
> code is now in drmlib.a instead of the object files being linked
> individually for each drm module.
Yep, I saw this, too.
> If I do `nm tdfx.o|grep printk`, with test12 I get only this:
>
> U printk_R1b7d4074
dito
SunWave1>cd ../../../../../2.4.0-test12-pre7/kernel/drivers/char/drm/
SunWave1>nm tdfx.o | grep printk
U printk_R1b7d4074
> with test13-pre4 on my home machine, I get the mangled symbol name plus a
> non-mangled one, both unresolved, maybe that causes problems.
SunWave1>cd ../../../../../2.4.0-test13-pre4/kernel/drivers/char/drm/
SunWave1>nm tdfx.o | grep printk
U printk
U printk_R1b7d4074
But the strange thing is this:
SunWave1>depmod -e
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/tdfx.o
depmod: remap_page_range
depmod: _mmx_memcpy
depmod: __wake_up
depmod: mtrr_add
depmod: __generic_copy_from_user
depmod: schedule
[snip]
-Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany
email: nuetzel@kogs.informatik.uni-hamburg.de
@home: Dieter.Nuetzel@hamburg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-28 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 1:54 test13-preX: DRM (tdfx.o) unresolved symbols fixed? Dieter Nützel
2000-12-27 10:07 ` Nils Philippsen
2000-12-27 23:50 ` Dieter Nützel [this message]
2000-12-28 16:40 ` Tony Hoyle
2000-12-28 23:00 ` Dieter Nützel
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=00122800503201.00902@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=Dri-devel@lists.sourceforge.net \
--cc=faith@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nils@fht-esslingen.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