From: Keith Owens <kaos@ocs.com.au>
To: Markus.Hennig@astaro.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0test5 make dep errors
Date: Sat, 28 Oct 2000 21:57:02 +1100 [thread overview]
Message-ID: <7788.972730622@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 27 Oct 2000 13:01:32 +0200." <39F9608C.A329F945@astaro.de>
On Fri, 27 Oct 2000 13:01:32 +0200,
Markus hennig <hennig@astaro.de> wrote:
>config.c:311: #error "HiSax: No cards configured"
>su.c:75: asm/oplib.h: No such file or directory
>su.c:77: asm/ebus.h: No such file or directory
>newport.c:11: asm/gfx.h: No such file or directory
>newport.c:12: asm/ng1.h: No such file or directory
>tcsyms.c:7: asm/dec/tc.h: No such file or directory
>zorro.c:20: asm/amigahw.h: No such file or directory
All (unfortunately) normal because make dep scans all source before any
generated .h files are created. Ignore, will be fixed in 2.5.
>/usr/src/linux/Rules.make:145: target `_subdir_sched' given more than
>once in the same rule.
Annoying but AFAIK it is harmless. Also to be fixed in 2.5.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-28 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 11:01 2.4.0test5 make dep errors Markus hennig
2000-10-28 10:57 ` Keith Owens [this message]
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=7788.972730622@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=Markus.Hennig@astaro.de \
--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