[Dri-devel] Re: test13-preX: DRM (tdfx.o) unresolved symbols fixed?

[Dieter <Die...@ha...>]

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: nu...@ko...
@home: Die...@ha...