[lkml]   [2000]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: string-486.h?
From said:


> 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.

Where, exactly? Note that memcpy per se is implemented again for the kernel
(When the compiler contains perfectly good inlined implementations of
several of the string and memory handling functions. Beats me why), so if
you do not include <linux/string.h>, it will end up missing.
Horst von Brand
Casilla 9G, Viña del Mar, Chile +56 32 672616

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.048 / U:3.260 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site