From: Arnaud Launay <asl@launay.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.19 : 'make dep' error
Date: Wed, 29 May 2002 23:22:25 +0200 [thread overview]
Message-ID: <20020529212225.GA10412@launay.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0205291611040.8639-100000@localhost.localdomain> <Pine.LNX.4.44.0205291528160.9971-100000@chaos.physics.uiowa.edu>
Le Wed, May 29, 2002 at 03:37:15PM -0500, Kai Germaschewski a écrit:
> So fix your setup to not use symlinks, or, at least, put an older kernel
> back into /usr/src/linux and compile the new kernels elsewhere.
Or use the following:
--- linux-2.5.19-old/scripts/Makefile Wed May 29 20:42:56 2002
+++ linux/scripts/Makefile Wed May 29 21:46:58 2002
@@ -8,7 +8,7 @@
$(HOSTCC) $(HOSTCFLAGS) -o $@ $<
split-include: split-include.c
- $(HOSTCC) $(HOSTCFLAGS) -o $@ $<
+ $(HOSTCC) $(HOSTCFLAGS) -I $(HPATH) -o $@ $<
# xconfig
# ---------------------------------------------------------------------------
I find it perfectly idiotic to tell people to use older kernel
include. Better to tell them to use stable versions if they do
not know what they do.
I want applications to be build with the new kernel headers,
including new API, especially when some aren't backward
compatible, and I think I'm not alone. And the only way to find
these is to symlink those headers to the utilised kernel release.
Arnaud.
next prev parent reply other threads:[~2002-05-29 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 20:14 2.5.19 : 'make dep' error Frank Davis
2002-05-29 20:37 ` Kai Germaschewski
2002-05-29 21:22 ` Arnaud Launay [this message]
2002-05-29 21:53 ` Kai Germaschewski
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=20020529212225.GA10412@launay.org \
--to=asl@launay.org \
--cc=linux-kernel@vger.kernel.org \
/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