From: Rob Landley <landley@trommello.org>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br
Subject: No rule to make autoconf.h in 2.4.19-rc1?
Date: Fri, 12 Jul 2002 11:26:44 -0400 [thread overview]
Message-ID: <20020712210434.271CA8B5@merlin.webofficenow.com> (raw)
Retry with a hopefully correct address for Marcelo. (There's only one n in
conectiva. Right.)
------------------
I'm trying to put together a linux from scratch system (3.3 with extensive
tweaks) using a build script that happily built 2.4.18 but is dying at the
start of make bzImage in 19-rc1, complaining there's no rule to make
include/linux/autoconf.h (needed by include/config/MARKER).
I've confirmed I got the right patch and that it applied correctly (or at
least reproducibly without rejects and changed the version numbers in the top
level makefile)... I untarred the 2.4.18 tarball into a fresh directory,
applied the patch, did "make dep" followed by "make clean" (I tried omitting
make clean and it didn't help) followed by make bzImage, at which point the
build process went off into the corner to sulk.
Maybe I'm doing something small and simple wrong (although 2.4.18 built), but
I can't spot it. I grepped the last couple weeks of my linux-kernel folder
and the only mention of autoconf.h was in patches, no descriptive text.
I also tried "touch include/linux/autoconf.h", which just makes
scripts/split-include die in find...
What does the kernel use autoconf for? (When did this get added? I wrote a
kernel output parser and didn't see autoconf, and I'd expect it to run in ake
dep anyway...)
Er... Help?
Rob
next reply other threads:[~2002-07-12 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 15:26 Rob Landley [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 15:13 Rob Landley
2002-07-12 17:29 ` Rob Landley
2002-07-12 21:27 ` Thunder from the hill
2002-07-12 17:33 ` Rob Landley
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=20020712210434.271CA8B5@merlin.webofficenow.com \
--to=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®