From: Andreas Schwab <schwab@suse.de>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
Leif Sawyer <lsawyer@gci.com>,
linux-kernel@vger.kernel.org
Subject: Re: Sparc-64 kernel build fails on version.h during 'make oldconfig'
Date: 26 Jul 2001 10:58:01 +0200 [thread overview]
Message-ID: <je1yn4kqxy.fsf@sykes.suse.de> (raw)
In-Reply-To: <BF9651D8732ED311A61D00105A9CA315053E1265@berkeley.gci.com> <15199.18841.458617.411246@pizda.ninka.net> <20010726064237.A26837@suse.de>
In-Reply-To: <20010726064237.A26837@suse.de> (Thorsten Kukuk's message of "Thu, 26 Jul 2001 06:42:37 +0200")
Thorsten Kukuk <kukuk@suse.de> writes:
|> No, I send you and on the sparclinux list already a patch for
|> this 2 weeks ago. The problem is, that make dep will build at first
|> sparc specific programs (archdep) which needs linux/version.h, but
|> make dep does create linux/version.h only after building this tools. The
|> following patch solved the problem for me:
|>
|> --- linux/Makefile
|> +++ linux/Makefile 2001/05/21 12:57:07
|> @@ -440,7 +440,7 @@
|> sums:
|> find . -type f -print | sort | xargs sum > .SUMS
|>
|> -dep-files: scripts/mkdep archdep include/linux/version.h
|> +dep-files: include/linux/version.h scripts/mkdep archdep
This will still fail with parallel builds. Better make the dependency of
archdep on version.h explicit.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-07-26 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 17:39 Sparc-64 kernel build fails on version.h during 'make oldconfig' Leif Sawyer
2001-07-25 22:35 ` David S. Miller
2001-07-26 4:42 ` Thorsten Kukuk
2001-07-26 8:58 ` Andreas Schwab [this message]
2001-07-26 1:45 ` Keith Owens
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=je1yn4kqxy.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=davem@redhat.com \
--cc=kukuk@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lsawyer@gci.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