Re: string-486.h?

From: Daniel.Egger@suse.de
Date: Wed Feb 23 2000 - 12:55:57 EST

Next message: H. Peter Anvin: "Re: Shared library problem"
Previous message: Jamie Lokier: "Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode"
In reply to: Brian Gerst: "string-486.h?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 23 Feb, Brian Gerst wrote:

> The code in include/asm-i386/string-486.h has been disabled for quite
> long time now. Is it truly dead and can be removed? What is broken
> with it?

I'd like to append another question. The current gcc seems to have
problems with memcpy calls in the kernel source. When compiling a
kernel I get unresolved memcpy symbols for example in hisax.
Although memcpy is used all over the source I get these
unresolved symbols just in a few places.

Servus, Daniel

- 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: H. Peter Anvin: "Re: Shared library problem"
Previous message: Jamie Lokier: "Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode"
In reply to: Brian Gerst: "string-486.h?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:34 EST