From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Mitchell Blank Jr <mitch@sfgoth.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [2.5 patch] fix kbuild breakage in drivers/atm
Date: Tue, 8 Oct 2002 19:49:46 +0200 [thread overview]
Message-ID: <20021008194946.A2212@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.NEB.4.44.0210081752240.8340-100000@mimas.fachschaften.tu-muenchen.de>; from bunk@fs.tum.de on Tue, Oct 08, 2002 at 06:02:41PM +0200
On Tue, Oct 08, 2002 at 06:02:41PM +0200, Adrian Bunk wrote:
> BTW:
> There might be places in the kernel that are now broken without a compile
> error, consider the second part of this line would output a compiler flag
> instead of a file name.
find -name Makefile | cut -d: -f 1 | grep -v arch | xargs grep '\.\./'
./drivers/atm/Makefile: CONFIG_ATM_FORE200E_PCA_FW := $(shell if test -n "`$(CC) -E -dM ../../include/asm/byteorder.h | grep ' __LITTLE_ENDIAN '`"; then echo pca200e.bin; else echo pca200e_ecd.bin2; fi)
./drivers/net/Makefile:obj-$(CONFIG_ARCH_ACORN) += ../acorn/net/
./drivers/scsi/Makefile:obj-$(CONFIG_ARCH_ACORN) += ../acorn/scsi/
./fs/devfs/Makefile:TOPDIR = ../..
./fs/devfs/Makefile: gcc -o /tmp/base.o -D__KERNEL__ -I../../include -Wall \
Dunno about the acorn part, but devfs looks broken.
Checking, devfs makefile has some documentation support in the makefile.
I'm tempted to delete it, surely it's not part of the kernel build system,
but I guess someone would yell at me.
If we include the architecture Makefiles:
find -name Makefile | xargs grep '\.\./' | wc -l
148
But I'm sure we hit a lot of false positves here.
Sam
next prev parent reply other threads:[~2002-10-08 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 16:02 Adrian Bunk
2002-10-08 17:49 ` Sam Ravnborg [this message]
2002-10-08 22:01 ` Russell King
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=20021008194946.A2212@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch@sfgoth.com \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®