From: Glenn Morris <rgm@gnu.org>
To: Han Boetes <han@boetes.org>
Cc: 15769@debbugs.gnu.org
Subject: bug#15769: building on OpenBSD fails because of a shell pattern problem
Date: Thu, 31 Oct 2013 13:27:24 -0400 [thread overview]
Message-ID: <xq1u315p1f.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20131031134133.GF5834@boetes.org> (Han Boetes's message of "Thu, 31 Oct 2013 14:41:33 +0100")
This will become irrelevant if http://debbugs.gnu.org/15260 gets fixed,
but in the meantime, please give details of:
exactly what version of OpenBSD this is
what shell /bin/sh is
and send the config.log as attachment
Han Boetes wrote:
> - *[[^\ -~]]*) AC_MSG_ERROR([Emacs cannot be built or installed in a directory whose name contains non-ASCII characters: $var]) ;;
> + *[[^\ ~-]]*) AC_MSG_ERROR([Emacs cannot be built or installed in a directory whose name contains non-ASCII characters: $var]) ;;
These are not the same thing.
[^\ -~] is supposed to match any character not in the range " " to "~",
which, under LC_ALL=C, should be the range of ASCII characters, AFAIK.
Maybe someone knows a better, portable way to test for non-ASCII?
I'd rather not do: [^a-zA-Z0-9...] if at all possible.
Yours, [^\ ~-], should match any character that is not " " , "~", or "-".
I have no idea how this can work for you...
Maybe "^" does not work as negation in your shell?
The autoconf manual does say that [^...] is not portable (apparently we
should use [!...] instead), but [^...] is extensively used elsewhere in
the Emacs build rules, and [!...] not at all.
Does it work for you if you use:
*[[!\ ~-]]*) AC_MSG_ERROR ...
?
next prev parent reply other threads:[~2013-10-31 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 13:41 bug#15769: building on OpenBSD fails because of a shell pattern problem Han Boetes
2013-10-31 17:27 ` Glenn Morris [this message]
2013-10-31 17:30 ` Glenn Morris
2013-10-31 21:11 ` Han Boetes
2013-10-31 21:42 ` Glenn Morris
2013-10-31 21:51 ` Han Boetes
2013-10-31 18:06 ` Glenn Morris
2013-10-31 20:51 ` Han Boetes
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xq1u315p1f.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=15769@debbugs.gnu.org \
--cc=han@boetes.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).