From: Han Boetes <han@boetes.org>
To: 15769@debbugs.gnu.org
Subject: bug#15769: building on OpenBSD fails because of a shell pattern problem
Date: Thu, 31 Oct 2013 22:11:18 +0100 [thread overview]
Message-ID: <20131031211118.GJ5834@boetes.org> (raw)
In-Reply-To: <vpwqkt4acg.fsf@fencepost.gnu.org>
Glenn Morris wrote:
> Argh, I meant to say
>
> *[[!\ -~]]*) AC_MSG_ERROR ...
>
> Ie, just swap "^" for "!".
I just got a portability hint from Thorsten Glaser:
"mirabilos| in shell moet je ! ipv ^ gebruiken voor inverted match"
So yes indeed, we have to use ! and not ^ in the shell. :-)
# Han
next prev parent reply other threads:[~2013-10-31 21:11 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
2013-10-31 17:30 ` Glenn Morris
2013-10-31 21:11 ` Han Boetes [this message]
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=20131031211118.GJ5834@boetes.org \
--to=han@boetes.org \
--cc=15769@debbugs.gnu.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).