From: Tom Rini <trini@kernel.crashing.org>
To: Martin MOKREJ? <mmokrejs@natur.cuni.cz>
Cc: Thunder from the hill <thunder@ngforever.de>,
Kelledin <kelledin+LKML@skarpsey.dyndns.org>,
linux-kernel@vger.kernel.org
Subject: Re: Missing files in 2.4.19-rc1
Date: Fri, 12 Jul 2002 12:03:27 -0700 [thread overview]
Message-ID: <20020712190327.GM695@opus.bloom.county> (raw)
In-Reply-To: <Pine.OSF.4.44.0207122052150.281934-100000@tao.natur.cuni.cz>
On Fri, Jul 12, 2002 at 08:54:46PM +0200, Martin MOKREJ? wrote:
> On Fri, 12 Jul 2002, Tom Rini wrote:
>
> > On Fri, Jul 12, 2002 at 08:39:18PM +0200, Martin MOKREJ? wrote:
> >
> > > `make dep` gave again:
> > [snip]
> > > au1000_gpio.c:41: asm/au1000.h: No such file or directory
> > > au1000_gpio.c:42: asm/au1000_gpio.h: No such file or directory
> >
> > These aren't an issue, since you're not compiling for MIPS, and that's
> > for the MIPS-specific au1000 GPIO driver. And those files aren't
> > missing on MIPS.
>
> Hmm, I just tried with plain 2.4.18 extracted and have the same problem.
> Should I just ignore `make dep` errors and just compile? Probably yes,
> as I'm running 2.4.10-pre2 for some months now with no real troubles
> anyway.
Yes, since they aren't errors, they're warnings really.
> But the source tree is broken, right? ;-)
No. 'make dep' goes and does dependancies on every single file in the
tree (except inside of arch/ where we only go into arch/$(ARCH)) so for
drivers which are specific to certain arches, you might get warnings for
files which don't exit on your $ARCH, but aren't selectible anyhow.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2002-07-12 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 9:47 Missing files in 2.4.19-rc1 Martin MOKREJŠ
2002-07-12 10:13 ` Kelledin
2002-07-12 10:21 ` Martin MOKREJŠ
2002-07-12 12:44 ` Thunder from the hill
2002-07-12 18:39 ` Martin MOKREJŠ
2002-07-12 18:50 ` Tom Rini
2002-07-12 18:54 ` Martin MOKREJŠ
2002-07-12 19:03 ` Tom Rini [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=20020712190327.GM695@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=kelledin+LKML@skarpsey.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@natur.cuni.cz \
--cc=thunder@ngforever.de \
/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