> 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 email@example.com 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 firstname.lastname@example.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:09 EST