From: Keith Owens <kaos@ocs.com.au>
To: Nick Warne <nick@linicks.net>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 make - path name breakage (perhaps)
Date: Thu, 17 Nov 2005 10:47:06 +1100 [thread overview]
Message-ID: <22029.1132184826@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 16 Nov 2005 15:09:04 -0000." <200511161509.04855.nick@linicks.net>
On Wed, 16 Nov 2005 15:09:04 +0000,
Nick Warne <nick@linicks.net> wrote:
>The reason is due to the untarred path name that includes () I found.
>
>I tested on virgin kernel 2.4.31 with GNU Make version 3.79.1.
>
>top level directory of kernel source as a test:
>
>linux-2.4.31(test)/
>
>And the errors (with a lot removed) - it does a little first then:
>
>> make mrproper
>/bin/sh: -c: line 1: syntax error near unexpected token
>`/home/nick/kernel/linux-2.4.31(t'
Rename the directory to linux-2.4.31-test. The kernel build code
assumes that there are no shell special characters in file names.
prev parent reply other threads:[~2005-11-16 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:09 2.4.31 make - path name breakage (perhaps) Nick Warne
2005-11-16 23:47 ` 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=22029.1132184826@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nick@linicks.net \
/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