[Daniel.Egger@suse.de: Re: string-486.h?]

[David Schleef <ds@stm.lbl.gov>]

This just appeared on the Linux kernel mailing list.  It
seems to be an interesting coincidence, or none at all.



dave...


----- Forwarded message from Daniel.Egger@suse.de -----

Date:   Wed, 23 Feb 2000 18:55:57 +0100 (CET)
From: Daniel.Egger@suse.de
Reply-To: Daniel.Egger@suse.de
Subject: Re: string-486.h?
To: bgerst@quark.vpplus.com
Cc: linux-kernel@vger.rutgers.edu
In-Reply-To: <38B40BAC.39AC36B0@quark.vpplus.com>
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-kernel-outgoing-dig

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/

----- End forwarded message -----