From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.21: kbuild changes broke filenames with commas
Date: Tue, 11 Jun 2002 09:02:45 +1000 [thread overview]
Message-ID: <5896.1023750165@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 09 Jun 2002 17:58:04 +0100." <20020609175804.B8761@flint.arm.linux.org.uk>
On Sun, 9 Jun 2002 17:58:04 +0100,
Russell King <rmk@arm.linux.org.uk> wrote:
>With the latest kbuild version in 2.5.21, we are unable to build the
>following files:
>
>linux/drivers/block/smart1,2.h
>linux/drivers/scsi/53c7,8xx.c
>linux/drivers/scsi/53c7,8xx.h
>linux/drivers/scsi/53c7,8xx.scr
>linux/arch/arm/mm/proc-arm6,7.S
>linux/arch/arm/mm/proc-arm2,3.S
kbuild 2.5 can handle filenames with ',' in the name. I do not believe
in restricting what users can do unless there is absolutely no
alternative. In this case a smarter build system can handle special
filenames.
next prev parent reply other threads:[~2002-06-10 23:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 16:58 2.5.21: kbuild changes broke filenames with commas Russell King
2002-06-09 17:11 ` Upper limits to number of processes / threads in Linux / ia32?? M. Edward (Ed) Borasky
2002-06-09 18:02 ` 2.5.21: kbuild changes broke filenames with commas Kai Germaschewski
2002-06-09 18:34 ` Tom Rini
2002-06-10 23:02 ` Keith Owens [this message]
2002-06-11 7:39 ` Russell King
2002-06-11 11:11 ` Thunder from the hill
2002-06-11 11:21 ` Russell King
2002-06-11 12:16 ` Thunder from the hill
2002-06-11 13:01 ` Russell King
2002-06-12 14:36 ` Ingo Oeser
2002-06-12 18:10 ` Thunder from the hill
2002-06-13 20:12 ` Thunder from the hill
2002-06-11 16:08 ` Daniel Phillips
2002-06-11 16:14 ` Alexander Viro
2002-06-11 16:22 ` Daniel Phillips
2002-06-11 16:31 ` Russell King
2002-06-11 16:36 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 23:55 Keith Owens
2002-06-12 0:27 ` Kai Germaschewski
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=5896.1023750165@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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