Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
Date: Tue, 24 Apr 2007 15:35:49 -0400
From: Earnie Boyd <[EMAIL PROTECTED]>
C:\>echo. > echo.
'echo.' is not recognized as an internal or external command,
operable program or batch file.
Can't reproduce this. Are you perhaps invoking `echo' from cm
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Date: Tue, 24 Apr 2007 22:05:25 +0100
>
> How long'd it take you to figure out that the redirected output file gets
> opened before the path search is done?
Actually, the redirection is parsed and acted upon as the first
thing. That's why redirection
> Date: Tue, 24 Apr 2007 15:35:49 -0400
> From: Earnie Boyd <[EMAIL PROTECTED]>
>
> C:\>echo. > echo.
> 'echo.' is not recognized as an internal or external command,
> operable program or batch file.
Can't reproduce this. Are you perhaps invoking `echo' from cmd that
was run from Bash?
___
On 24 April 2007 20:36, Earnie Boyd wrote:
> Quoting Aaron Shatters:
>
>> 2 - using "echo. 2>&1" which tricks make into thinking this should be
>> handled by the shell?
>
> I hate to be the bearer of bad news but ``echo.'' isn't a valid command.
[ Just to give a straight answer: It's documente
Quoting Aaron Shatters <[EMAIL PROTECTED]>:
2 - using "echo. 2>&1" which tricks make into thinking this should be
handled by the shell?
I hate to be the bearer of bad news but ``echo.'' isn't a valid command.
C:\>dir echo*
Volume in drive C is QWEST
Volume Serial Number is 6077-E76C
Directo
Quoting Aaron Shatters <[EMAIL PROTECTED]>:
Really, TAAHOALOP using a native windows GNU make.
Ok, ya gots me there. There Aint A . something something Lot Of Point?
TAAHOALOP
"There Are A Hell Of A Lot Of People"
Maybe?
Exactly.
Earnie
___
>> Really, TAAHOALOP using a native windows GNU make.
> Ok, ya gots me there. There Aint A . something something Lot Of Point?
TAAHOALOP
"There Are A Hell Of A Lot Of People"
Maybe?
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best s
On 24 April 2007 18:04, Earnie Boyd wrote:
> Quoting Dave Korn <[EMAIL PROTECTED]>:
>
>> On 24 April 2007 12:35, Earnie Boyd wrote:
>>
>>> Quoting Dave Korn:
>>>
On 24 April 2007 07:43, Benoit Sigoure wrote:
> and the whole community will benefit from this very slight impro
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Cc:
> Date: Tue, 24 Apr 2007 15:26:48 +0100
>
> > 2 - using "echo. 2>&1" which tricks make into thinking
> > this should be handled by the shell?
>
> Bingo. The problem is that make doesn't take the slow path when it should;
> using redirection guaran
Quoting Dave Korn <[EMAIL PROTECTED]>:
On 24 April 2007 12:35, Earnie Boyd wrote:
Quoting Dave Korn:
On 24 April 2007 07:43, Benoit Sigoure wrote:
and the whole community will benefit from this very slight improvement.
Nope, only the minority of win32/cmd.exe users. An awful lot of pe
On 24 April 2007 15:26, Christopher Faylor wrote:
> There's that plus the fact that the whole reason for this, AFAICT, is to
> somehow make your makefile output a blank line. Is that really a common
> enough task worth the cost of maintaining a kludge?
Well, it's often no mere cosmetic. I use
On 24 April 2007 15:23, Aaron Shatters wrote:
> With cmd.exe as my shell, what is the suggested method of echoing a blank
> line to the screen?
>
> 2 - using "echo. 2>&1" which tricks make into thinking
> this should be handled by the shell?
Bingo. The problem is that make doesn't take the
On Tue, Apr 24, 2007 at 10:18:13AM +0100, Dave Korn wrote:
>On 24 April 2007 10:11, Benoit Sigoure wrote:
>>Quoting Dave Korn <[EMAIL PROTECTED]>:
>>>On 24 April 2007 07:43, Benoit Sigoure wrote:
and the whole community will benefit from this very slight improvement.
>>>
>>>Nope, only the minor
Ok. I will start assuming that I am fighting a losing battle with getting make
to support his... so back to the problem...
With cmd.exe as my shell, what is the suggested method of echoing a blank line
to the screen?
1 - writing my own executable called "echo..exe" and distributing it with the
> Date: Tue, 24 Apr 2007 11:11:02 +0200
> From: Benoit Sigoure <[EMAIL PROTECTED]>
> Cc: 'Eli Zaretskii' <[EMAIL PROTECTED]>, make-w32@gnu.org
>
> Quoting Dave Korn <[EMAIL PROTECTED]>:
>
> > On 24 April 2007 07:43, Benoit Sigoure wrote:
> >
> >
> >> and the whole community will benefit from this
On 24 April 2007 12:35, Earnie Boyd wrote:
> Quoting Dave Korn:
>
>> On 24 April 2007 07:43, Benoit Sigoure wrote:
>>
>>
>>> and the whole community will benefit from this very slight improvement.
>>
>> Nope, only the minority of win32/cmd.exe users. An awful lot of people
>> never use make
Quoting Dave Korn <[EMAIL PROTECTED]>:
On 24 April 2007 07:43, Benoit Sigoure wrote:
and the whole community will benefit from this very slight improvement.
Nope, only the minority of win32/cmd.exe users. An awful lot of people
never use make with any other than a POSIX shell
With
On 24 April 2007 10:11, Benoit Sigoure wrote:
> Quoting Dave Korn <[EMAIL PROTECTED]>:
>
>> On 24 April 2007 07:43, Benoit Sigoure wrote:
>>
>>
>>> and the whole community will benefit from this very slight improvement.
>>
>> Nope, only the minority of win32/cmd.exe users. An awful lot of pe
Quoting Dave Korn <[EMAIL PROTECTED]>:
On 24 April 2007 07:43, Benoit Sigoure wrote:
and the whole community will benefit from this very slight improvement.
Nope, only the minority of win32/cmd.exe users. An awful lot of people
never use make with any other than a POSIX shell
Yes,
On 24 April 2007 07:43, Benoit Sigoure wrote:
> and the whole community will benefit from this very slight improvement.
Nope, only the minority of win32/cmd.exe users. An awful lot of people
never use make with any other than a POSIX shell
cheers,
DaveK
--
Can't think of a wit
Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
Date: Mon, 23 Apr 2007 15:17:52 -0700 (PDT)
From: Aaron Shatters <[EMAIL PROTECTED]>
Cc: make-w32@gnu.org
Documentation from microsoft:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/echo.mspx?mfr=true
This is not a bi
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>,
>
> Date: Tue, 24 Apr 2007 00:22:32 +0100
>
> On 23 April 2007 23:02, Eli Zaretskii wrote:
>
> >> From: "Dave Korn" <[EMAIL PROTECTED]>
> >> Cc: <[EMAIL PROTECTED]>,
> >>
> >> Date: Mon, 23 Apr 2007 15:22:40 +0100
> >>
> Date: Mon, 23 Apr 2007 15:17:52 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> >As for the "echo." case, it's just a bizarre consequence of cmd
> >command-line parsing (there are many more manifestations of that, and
> >others have pointed out some of them).
>
On 23 April 2007 23:02, Eli Zaretskii wrote:
>> From: "Dave Korn" <[EMAIL PROTECTED]>
>> Cc: <[EMAIL PROTECTED]>,
>>
>> Date: Mon, 23 Apr 2007 15:22:40 +0100
>>
>>> I don't think "echo." is a shell builtin. It is a peculiar feature of
>>> the cmd.exe command parser.
>>
>> This is a sema
>As for the "echo." case, it's just a bizarre consequence of cmd
>command-line parsing (there are many more manifestations of that, and
>others have pointed out some of them).
Documentation from microsoft:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/echo.mspx?mf
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>,
>
> Date: Mon, 23 Apr 2007 15:22:40 +0100
>
> > I don't think "echo." is a shell builtin. It is a peculiar feature of
> > the cmd.exe command parser.
>
> This is a semantic quibble.
You are, of course, entitled to think
> Date: Mon, 23 Apr 2007 07:20:53 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> >I remain unconvinced that we should ``fix'' this just because this
> >fundamental incompatibility between shells sometimes causes trouble in
> >Makefiles that assume Posix `echo' wh
On 2007-04-23 18:36Z, Keith Huntington wrote:
>
> If it were JUST the special case of "Echo.", I would
> absolutely be on the side of making the tweak to Make
> to support the one special case... but now that I know
> that CMD.EXE just has an obnoxious parser with some
> undocumented rules,
Here'
> >> > Since "echo." is clearly a shell builtin, and
> >>
> >> I don't think "echo." is a shell builtin. It is a
> >> peculiar feature of the cmd.exe command parser.
> >
> > This is a semantic quibble. The shell builtin
> > is "echo", "echo." is an alternative form, and
>
> I believe that t
On 23 April 2007 19:10, Christopher Faylor wrote:
> I believe that the real issue here is that, in some cases, cmd.exe
> throws away a '.' after a built-in command. So, it isn't, IMO, strictly
> correct to add an 'echo.'. If we really wanted to do this, it seems
> like it would be better to rec
On Mon, Apr 23, 2007 at 03:22:40PM +0100, Dave Korn wrote:
>On 21 April 2007 10:02, Eli Zaretskii wrote:
>
>[ got left sitting in my drafts folder over the weekend. ]
>
>>> From: "Dave Korn"
>>> Date: Fri, 20 Apr 2007 17:18:01 +0100
>>> On 20 April 2007 17:15, Aaron Shatters wrote:
>>>
As I
On 21 April 2007 10:02, Eli Zaretskii wrote:
[ got left sitting in my drafts folder over the weekend. ]
>> From: "Dave Korn"
>> Date: Fri, 20 Apr 2007 17:18:01 +0100
>> On 20 April 2007 17:15, Aaron Shatters wrote:
>>
>>> As I noted previously, there are many workarounds to this problem. I am
>> Date: Fri, 20 Apr 2007 09:14:31 -0700 (PDT)
>> From: Aaron Shatters <[EMAIL PROTECTED]>
>>
>> As I noted previously, there are many workarounds to this problem. I am
>> interested in fixing the root cause. After all of this investigation, do we
>> have consensus that this is a limitation of
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Date: Fri, 20 Apr 2007 17:18:01 +0100
> Cc:
>
> On 20 April 2007 17:15, Aaron Shatters wrote:
>
> > As I noted previously, there are many workarounds to this problem. I am
> > interested in fixing the root cause. After all of this investigation, do
> >
> Date: Fri, 20 Apr 2007 09:14:31 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
>
> As I noted previously, there are many workarounds to this problem. I am
> interested in fixing the root cause. After all of this investigation, do we
> have consensus that this is a limitation of make?
On 20 April 2007 17:15, Aaron Shatters wrote:
> As I noted previously, there are many workarounds to this problem. I am
> interested in fixing the root cause. After all of this investigation, do
> we have consensus that this is a limitation of make? More importantly, do
> we have consensus that
As I noted previously, there are many workarounds to this problem. I am
interested in fixing the root cause. After all of this investigation, do we
have consensus that this is a limitation of make? More importantly, do we have
consensus that it should be fixed? We seem to have run out of rea
On 2007-04-19 14:26Z, Aaron Shatters wrote:
>
> There is no reason why this should not work, which is why I'm requesting the
> gnu make change.
Here's an idea that might do what you want without changing 'make':
write your own 'echo..exe' that does whatever you like. My compiler's
on vacation to
>> For everyone who has 'echo""' working, I have an explaination...
>>
>> You probably have the echo.exe available in PATH somewhere. Let me show
>> you...
>>
>> #
>> Microsoft Windows 2000 [Version 5.00.2195]
>> (C) Copyright 1985-2000 Mi
On 19 April 2007 15:27, Aaron Shatters wrote:
> For everyone who has 'echo""' working, I have an explaination...
>
> You probably have the echo.exe available in PATH somewhere. Let me show
> you...
>
> #
> Microsoft Windows 2000 [Version
For everyone who has 'echo""' working, I have an explaination...
You probably have the echo.exe available in PATH somewhere. Let me show you...
#
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
P:\>set PAT
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Cc:
> Date: Thu, 19 Apr 2007 01:21:35 +0100
>
> >> (Notice the extra empty-line... weird)
> >
> > It's not weird, it's how `echo' in cmd.exe works.
>
> It doesn't normally print the word "echo", though.
Right, and it doesn't do that here. But the ex
> > From: Aaron Shatters <[EMAIL PROTECTED]>
> >
> > ##
> > Microsoft Windows XP [Version 5.1.2600]
> > (C) Copyright 1985-2001 Microsoft Corp.
> > P:\>echo""
> > 'echo""' is not recognized as an internal or external command,
> > operable program or batch fi
On 18 April 2007 23:39, Eli Zaretskii wrote:
>> Date: Thu, 19 Apr 2007 00:32:04 +0200
>> From: Benoit Sigoure <[EMAIL PROTECTED]>
>> Cc: Aaron Shatters <[EMAIL PROTECTED]>, make-w32@gnu.org
>>
>> C:\cygwin\home\build>echo""
>> echo""
>>
>>
>> C:\cygwin\home\build>echo ""
>> echo ""
>> ""
>>
>>
> > From: Aaron Shatters <[EMAIL PROTECTED]>
> >
> > ##
> > Microsoft Windows XP [Version 5.1.2600]
> > (C) Copyright 1985-2001 Microsoft Corp.
> > P:\>echo""
> > 'echo""' is not recognized as an internal or external command,
> > operable program or batch fi
> Date: Thu, 19 Apr 2007 00:32:04 +0200
> From: Benoit Sigoure <[EMAIL PROTECTED]>
> Cc: Aaron Shatters <[EMAIL PROTECTED]>, make-w32@gnu.org
>
> C:\cygwin\home\build>echo""
> echo""
>
>
> C:\cygwin\home\build>echo ""
> echo ""
> ""
>
> C:\cygwin\home\build>
> --
Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
Date: Wed, 18 Apr 2007 09:35:51 -0700 (PDT)
From: Aaron Shatters <[EMAIL PROTECTED]>
Cc: "make-w32 gnu.org"
##
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
P:\>echo""
'echo""' i
> Date: Tue, 17 Apr 2007 21:34:52 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> No, for the cmd.exe shell, echo"" doesn't seem to be working.
It does for me, see my other message, and it does for Dave. I'm at a
loss why it doesn't for you.
> As for why it is
> Date: Wed, 18 Apr 2007 09:35:51 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
> Cc: "make-w32 gnu.org"
>
> ##
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
> P:\>echo""
> 'echo""' is not recognized as an inte
>>> Btw, you can have an empty line with cmd's echo if you say `echo""'.
>>
>> No, for the cmd.exe shell, echo"" doesn't seem to be working.
> It WFM, but it's vital not to use a space:
>
>Microsoft Windows XP [Version 5.1.2600]
>(C) Copyright 1985-2001 Microsoft Corp.
>C:\Documents and Settings\
On 18 April 2007 05:35, Aaron Shatters wrote:
>> Btw, you can have an empty line with cmd's echo if you say `echo""'.
>
> No, for the cmd.exe shell, echo"" doesn't seem to be working.
It WFM, but it's vital not to use a space:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 M
>Btw, you can have an empty line with cmd's echo if you say `echo""'.
No, for the cmd.exe shell, echo"" doesn't seem to be working.
> shall-i-invoke-a-shell-command-because-of-redirection-or-other-tricky-stuff
> vs. shall-i-just-invoke-the-command-executable-itself-directly decision stuff?
Yes,
> From: "Dave Korn" <[EMAIL PROTECTED]>
> Cc:
> Date: Wed, 18 Apr 2007 00:00:49 +0100
>
> Maybe it's something to do with the
> shall-i-invoke-a-shell-command-because-of-redirection-or-other-tricky-stuff
> vs. shall-i-just-invoke-the-command-executable-itself-directly decision stuff?
>
> stati
On 17 April 2007 22:23, Eli Zaretskii wrote:
>> I suppose the "feature" that is missing is the ability to run shell
>> commands as they are defined by the shell that will be running the shell
>> commands. Furthermore, the ability to more easily port our numerous
>> makefiles to use gnu make witho
> Date: Tue, 17 Apr 2007 14:14:15 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
> Cc: make-w32@gnu.org
>
> I suppose the "feature" that is missing is the ability to run shell commands
> as they are defined by the shell that will be running the shell commands.
> Furthermore, the ability
>> Date: Tue, 17 Apr 2007 13:45:10 -0700 (PDT)
>> From: Aaron Shatters <[EMAIL PROTECTED]>
>>
>> "make" doesn't recognize this as a shell command because the "echo." command
>> is not in the shell >command list for dos, and furthermore, the arguments
>> are not separated from the command by a sp
> Date: Tue, 17 Apr 2007 13:45:10 -0700 (PDT)
> From: Aaron Shatters <[EMAIL PROTECTED]>
>
> "make" doesn't recognize this as a shell command because the "echo." command
> is not in the shell command list for dos, and furthermore, the arguments are
> not separated from the command by a space or
There is a usage of the echo command in the cmd.exe shell that doesn't seem to
be supported by gnu make. This is different that all other shell commands in
that it's arguments are not necessarily separated by whitespace from the
command. For example:
@echo.
will print a blank line
@echo. H
58 matches
Mail list logo
