[Octave-bug-tracker] [bug #60413] build: sed expression problems when prefix is empty or slash

[John W. Eaton]

Follow-up Comment #22, bug #60413 (project octave):

Rik: The .mk files are different, they are Makefile fragments where the parens
are required, otherwise $PERL is equivalent to ${P}ERL.  In a shell script,
normal parens $(PERL) will be evaluated as a shell command substitution and
execute PERL, stuffing any output back into the shell script expression where
$(PERL) is used.  Maybe you are thinking of ${PERL} instead of just $PERL in
shell scripts?  I don't see that we've been consistent with that either.

Where it might matter is when the command is a full file name that contains
spaces.  Does ${} protect that, or is "${}" quoting needed?  Either way I
don't think we've ever done the work so that the build system can work
properly in a directory tree that has spaces in the name.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60413>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/