Mike Castle wrote:
> (libc does usually take care to be able to build against a later kernel
> version than you're running on, and determine at run time what features may
> or may not be there, so one could have a 2.4.2 kernel handy to build libc
> against while still running a 2.2.18 kernel. The
On Thu, Feb 22, 2001 at 02:40:55PM -0800, Robert Read wrote:
> Ok, my bad, I forgot about cross-compiles. The problem was
> scripts/split-include.c includes errno.h, which requires linux/errno.h
> to exist, and I thought it would be better to use the current kernel's
> version, rather than the sys
Ok, my bad, I forgot about cross-compiles. The problem was
scripts/split-include.c includes errno.h, which requires linux/errno.h
to exist, and I thought it would be better to use the current kernel's
version, rather than the system version. I guess not.
robert
On Thu, Feb 22, 2001 at 10:28:58P
> FINDHPATH = $(HPATH)/asm $(HPATH)/linux $(HPATH)/scsi $(HPATH)/net
>
> HOSTCC = gcc
> -HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
> +HOSTCFLAGS = -I$(HPATH) -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
That seems odd. Which build tools need to
On Thu, 22 Feb 2001, Robert Read wrote:
> Please apply one line patch to the top level Makefile. This points
> the build tools at the correct linux include dir.
Or please don't, it's incorrect.
It breaks cross-compiling, and just generally wrong. If your
system won't build without this, it's
5 matches
Mail list logo
