Re: pre4-5 has a bunch of unresolved symbols

• Next message: Alok Mittal: "linux/apache configuration"
• Previous message: Ed Carp: "Re: Suggested dual human/binary interface for proc/devfs"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ari Pollak wrote:
>
> As the topic says, depmod -a -e shows one unresolved symbol in a ton of
> different modules, plus a couple extra ones. They are MMX-related; I am
> using an AMD K6-2 450 processor, and the processor type in the
> configuration is set to match that. I also have MTRRs enabled. Here is the
> entire 'depmod -a -e' output:
>
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/lockd.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/fat.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/vfat.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/isofs.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/nfs.o
> depmod: _mmx_memcpy
> depmod: xdr_two
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/smbfs.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/fs/autofs4.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/net/ppp_async.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/net/ppp_generic.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/net/slhc.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/net/3c59x.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/net/ppp_deflate.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/scsi/scsi_mod.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/block/floppy.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/cdrom/cdrom.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/bttv.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/joystick.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/parport.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/parport_pc.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/serial.o
> depmod: _mmx_memcpy
> depmod: mmx_clear_page
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/misc/sunrpc.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/usb/hid.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/usb/usb-ohci.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/usb/usbcore.o
> depmod: _mmx_memcpy
> depmod: *** Unresolved symbols in /lib/modules/2.3.99-pre4/ide/ide-cd.o
> depmod: _mmx_memcpy

I see this whenever I over-optimize while compiling. I have an Athlon,
and this occurs whenver I try to compile stupid things into the kernel
like PIII/MMX2 support (IE: My processor doesn't have it.) If you also
have an Athlon, Turn off the PIII optimizations, and compile for
K6/PII/PPro and you'll be allright.

Chris Kloiber

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Alok Mittal: "linux/apache configuration"
• Previous message: Ed Carp: "Re: Suggested dual human/binary interface for proc/devfs"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:11 EST