Date: Wed, 5 Jan 2000 18:38:07 +0100 (CET) From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de> To: freebsd-questions@FreeBSD.ORG Subject: Re: Poss bug in /bin/sh? Message-ID: <200001051738.SAA36801@dorifer.heim3.tu-clausthal.de> In-Reply-To: <84vu3o$1hpk$1@atlantis.rz.tu-clausthal.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric J. Schwertfeger <ejs@bfd.com> wrote in list.freebsd-questions:
> cat >> confdefs.h <<EOF
> #define PTY_BSD_SCHEME_FIRST_CHARS "`ls /dev/pty* | cut -c 9-9 | uniq | tr -d '\n'`"
> EOF
> [...]
> running the same under bash produces the desired output. What's wrong
> here? Yes, this is part of the configure script, if it looks strange,
> though with my limited shell knowledge, I'd still expect it to work.
From the sh(1) manpage:
If the delimiter as specified on the initial line is quoted,
then the here-doc-text is treated literally, otherwise the
text is subjected to parameter expansion, command
substitution, and arithmetic expansion (as described in the
section on `Expansions'').
So /bin/sh works perfectly correct. Bash probably doesn't.
Regards
Oliver
--
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)
"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001051738.SAA36801>