delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Mon, 10 Apr 2000 10:04:22 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: Porting problems with Sh-utils (beta) |
Message-ID: | <38F1A726.23834.332F7B@localhost> |
References: | <200004091317 DOT SAA00692 AT midpec DOT com> |
In-reply-to: | <Pine.SUN.3.91.1000410083609.19649B-100000@is> |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
Reply-To: | djgpp-workers AT delorie DOT com |
>> > Script: > > ----- > > #!/bin/sh > > > > echo $source Add: echo "${1+$@}" run 'make' and you'll see what's going on. The line continutation shown below tricks Bash into treating 'echo `echo` script executed' as an argument belonging to the previous command instead of treating it like a new command. I'd recommend changing the makefile from: > > all: > source='There is no bug in BASH!' \ > $(SHELL) ./script \ > echo `echo`script executed to > > all: > source='There is no bug in BASH!' \ > $(SHELL) ./script > echo `echo`script executed
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |