public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
	linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2] compat-wireless: build: Throw error if space in path
Date: Wed, 18 Jan 2012 16:18:43 +0100	[thread overview]
Message-ID: <20120118151843.GA23506@nautica> (raw)
In-Reply-To: <1326786261.3342.0.camel@jlt3.sipsolutions.net>

Hi,

(I added linux-kbuild@ in Cc because it also concerns them. The idea is
to fail cleanly if there is a space in the path to the directory from
which we want to build some modules. We can't detect some from kbuild
itself given how params are given, so it started as a patch for the
modules' Makefile instead)


Johannes Berg wrote on Tue, Jan 17, 2012 :
> I think it also fails if there's a colon in the path -- does anyone know
> what the "forbidden" characters would be?

I can confirm that it fails with a colon in path, although it's not
documented anywhere in Documentation/kbuild/.. (I guess I've just
volunteered to fix that, too :))

I didn't find a proper list, but what I've seen fail is:
 - space " "
 - colon ":"
 - semicolon ";"
 - antislash "\"
 - dollar "$"
 - sharp "#" (although it fails later than the others)
 - ampersand "&"
 - parenthesis "(" and ")" - these fail somewhere else as well (even
 after fixing compat-wireless' Makefile with minor quoting)
 - backtick "`"
 - double quotes """ 
 - single quotes "'"

what does work that's not necessarily obvious:
 - comma, brakets [], brakets {}


... There might be many more I didn't come up with, but that does look
like a fair start!
Does anyone know of a more complete list?

Regards,
-- 
Dominique Martinet | Asmadeus

           reply	other threads:[~2012-01-18 15:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1326786261.3342.0.camel@jlt3.sipsolutions.net>]

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=20120118151843.GA23506@nautica \
    --to=asmadeus@codewreck.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@frijolero.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