From: Robert Read <rread@datarithm.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use correct include dir for build tools
Date: Thu, 22 Feb 2001 14:40:55 -0800 [thread overview]
Message-ID: <20010222144055.B20752@tenchi.datarithm.net> (raw)
In-Reply-To: <20010222123940.A20319@tenchi.datarithm.net> <E14W4EP-00055G-00@the-village.bc.nu>
In-Reply-To: <E14W4EP-00055G-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Feb 22, 2001 at 10:28:58PM +0000
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:58PM +0000, Alan Cox wrote:
> > 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 find kernel includes for this kernel
> not the standard C includes
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-22 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 20:39 Robert Read
2001-02-22 22:23 ` Matthew Kirkwood
2001-02-22 22:28 ` Alan Cox
2001-02-22 22:40 ` Robert Read [this message]
2001-02-22 23:09 ` Mike Castle
2001-02-22 23:44 ` Thomas Dodd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010222144055.B20752@tenchi.datarithm.net \
--to=rread@datarithm.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®