Re: Handling of shell builtins in make(1)
From: Peter Jeremy (PeterJeremy_at_optushome.com.au)
Date: 05/24/05
- Previous message: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- In reply to: Scott Long: "Re: Handling of shell builtins in make(1)"
- Next in thread: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- Reply: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 24 May 2005 19:32:38 +1000 To: Harti Brandt <harti@freebsd.org>
On Mon, 2005-May-23 20:50:40 -0600, Scott Long wrote:
>Harti Brandt wrote:
>>The result of this is that for one and the same command you can get
>>different behaviour whether you execute it via make(1) or via sh -c '...'.
Not to mention the effect of IFS. Does POSIX provide any helpful
suggestions on how to efficiently implement the behaviour they specify?
>4. Separate /bin/sh into a front end and back end (libsh) and include
>libsh into make.
And this still won't help people who use .SHELL (or similar) to pick
a different shell.
5) Add a "POSIX_ME_HARDER" option that just invokes the shell on every
command. In the absence of this option, make(1) is free to directly
exec the command if it's simple enough.
6) Add two new magic line markers (to supplement '@', '+' and '-') to
require the line be executed using the shell or exec'd directly,
superceding the buildin rules.
-- Peter Jeremy _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- In reply to: Scott Long: "Re: Handling of shell builtins in make(1)"
- Next in thread: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- Reply: Harti Brandt: "Re: Handling of shell builtins in make(1)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|