> -Original Message-
> From: help-make-bounces+mec=stowers@gnu.org [mailto:help-make-
> bounces+mec=stowers@gnu.org] On Behalf Of Afif Elghraoui
> Sent: Tuesday, May 26, 2015 2:36 PM
> To: help-make@gnu.org
> Subject: Re: Shell for evaluating .SHELLFLAGS
>
&
I should clarify something:
On 05/26/2015 12:35 PM, Afif Elghraoui wrote:
On 05/26/2015 10:16 AM, Cook, Malcolm wrote:
This will be a problem when using sqlite3 as your make .SHELL.
Why? Because the contents of a make recipe is always passed to the
.SHELL as a parameter. Never on stdin. B
Hi, Malcolm,
On 05/26/2015 10:16 AM, Cook, Malcolm wrote:
Afif,
Are you trying to get the output from different SQL recipes to go into
different files.
Yes
This will be a problem when using sqlite3 as your make .SHELL.
Why? Because the contents of a make recipe is always passed to the .
Erm, there is an errant "o" on the last line of `bash1in`. ~Malcolm
-Original Message-
From: Cook, Malcolm
Sent: Tuesday, May 26, 2015 12:17 PM
To: 'Afif Elghraoui'; help-make@gnu.org
Subject: RE: Shell for evaluating .SHELLFLAGS
Afif,
Are you trying to get the o
I know nothing, but to me it looks like the OP is mixing SHELL features:
'<(echo ".output $@")' doesn't look like a sqlite3 feature, it looks
like Unix shell redirection.
What works is something like
$ cat sqlite3.ini
.output all
$ cat Makefile
SHELL=/usr/bin/sqlite3
# .SHELLFLAGS= $(DB)
.SHEL
ed this approach for instance with the R language as the interpreter.
This should fix ya!
Malcolm Cook
-Original Message-
From: help-make-bounces+mec=stowers@gnu.org
[mailto:help-make-bounces+mec=stowers@gnu.org] On Behalf Of Afif Elghraoui
Sent: Monday, May 25, 2015 11:05 PM
To: help-
On 05/26/2015 09:15 AM, David Boyce wrote:
BTW /usr/bin/env creates a redundant process here. The reason people
use /usr/bin/env to translate an execv() (does not use PATH) to an
execvp() (does). But GNU make uses execvp() already; try "make
SHELL=sh” to see that.
-David Boyce
Thanks. That's
BTW /usr/bin/env creates a redundant process here. The reason people
use /usr/bin/env to translate an execv() (does not use PATH) to an
execvp() (does). But GNU make uses execvp() already; try "make
SHELL=sh” to see that.
-David Boyce
On Tue, May 26, 2015 at 5:14 AM, Paul Smith wrote:
> On Mon,
On Mon, 2015-05-25 at 21:05 -0700, Afif Elghraoui wrote:
> Hello,
> I am trying to use sqlite3 as my Makefile shell. In order to have the
> query outputs go to a file, I need to pass a file in to sqlite using its
> -i flag. I rely on the process substitution feature in bash for the
> .SHELLFLAGS to
Hello,
I am trying to use sqlite3 as my Makefile shell. In order to have the
query outputs go to a file, I rely on the process substitution feature
in bash for the .SHELLFLAGS:
SHELL=/usr/bin/env sqlite3
.SHELLFLAGS=-init <(echo ".output $@") $(DB)
I get this error:
/bin/sh: 1: Syntax error:
Hello,
I am trying to use sqlite3 as my Makefile shell. In order to have the
query outputs go to a file, I need to pass a file in to sqlite using its
-i flag. I rely on the process substitution feature in bash for the
.SHELLFLAGS to provide the file:
SHELL=/usr/bin/env sqlite3
.SHELLFLAGS=-init <(
11 matches
Mail list logo
