Oron Peled <[EMAIL PROTECTED]> writes:
> The correctness of you assertion greatly depends on which "those" you mean.
> Sunos (which was the dominant Unix throughout the 80's and the beginning
> of the 90's) had /bin/csh as default. BTW, this explains how some parts
> in the academic world got the
On Friday, 23 בNovember 2007, Oleg Goldshmidt wrote:
> "Amos Shapira" <[EMAIL PROTECTED]> writes:
> > - properly-written shell scripts shouldn't depend on their
> > environment
Hmmm... I hope you don't advocate massive overriding of environment
variables in shell scripts: PATH, HOME, TERM and zill
"Amos Shapira" <[EMAIL PROTECTED]> writes:
> On 22/11/2007, Oleg Goldshmidt <[EMAIL PROTECTED]> wrote:
>
>> what not that expect echo options, regular expressions, and other
>> stuff ash/dash does not provide. Yes, I realize that it is technically
>> careless. That's no excuse for keeping the defa
On 22/11/2007, Oleg Goldshmidt <[EMAIL PROTECTED]> wrote:
> If you don't want to change your installation, put
>
> SHELL=/bin/bash
>
> at the top of your Makefile. This is probably a good idea for
> portability if you don't trust the user's $SHELL to have all the
> needed features.
1. As far as I
On Nov 22, 2007 6:23 PM, Oleg Goldshmidt <[EMAIL PROTECTED]> wrote:
> "Kfir Lavi" <[EMAIL PROTECTED]> writes:
>
> > Yep,
> > The thing is that make uses /bin/sh and /bin/sh -> dash.
> > Changing the link /bin/sh to point to bash solved the problem.
>
> If you don't want to change your installation
"Kfir Lavi" <[EMAIL PROTECTED]> writes:
> Yep,
> The thing is that make uses /bin/sh and /bin/sh -> dash.
> Changing the link /bin/sh to point to bash solved the problem.
If you don't want to change your installation, put
SHELL=/bin/bash
at the top of your Makefile. This is probably a good idea
Do note that this symlink is a result of a divert made by dash's
installation. The *right* solution is to either uninstall the 'dash' package
or at least to remove the divert (using the dpkg-divert utility).
On Nov 22, 2007 9:53 AM, Kfir Lavi <[EMAIL PROTECTED]> wrote:
> Yep,
> The thing is that
t; Thanks,
> > Kfir
> >
> > On Nov 21, 2007 8:26 PM, Valery Reznic <[EMAIL PROTECTED]> wrote:
> > > --- Dotan Shavit <[EMAIL PROTECTED]> wrote:
> > > > On Tuesday 20 November 2007, you wrote:
> > > > > Hi,
> > > > >
> Kfir
>
> On Nov 21, 2007 8:26 PM, Valery Reznic <[EMAIL PROTECTED]> wrote:
> > --- Dotan Shavit <[EMAIL PROTECTED]> wrote:
> > > On Tuesday 20 November 2007, you wrote:
> > > > Hi,
> > > > I have a problem running echo in
OTECTED]> wrote:
>
> > On Tuesday 20 November 2007, you wrote:
> > > Hi,
> > > I have a problem running echo inside Makefile.
> > > Here is the Makefile:
> > > all:
> > > @echo "string"
> > > @echo -e -n "s
On Tuesday 20 November 2007, you wrote:
> Hi,
> I have a problem running echo inside Makefile.
> Here is the Makefile:
> all:
> @echo "string"
> @echo -e -n "string"
>
> The output is:
> string
> -e -n string
>
> The problem i
On Nov 21, 2007 1:33 AM, Amos Shapira <[EMAIL PROTECTED]> wrote:
> On 20/11/2007, Kfir Lavi <[EMAIL PROTECTED]> wrote:
> > Ok,
> > make -d don't show much.
> > I have attached the two files: Makefile and make.log
>
> That's weird - your make.log says:
>
> Must remake target `all'.
> -e -n aaa
>
>
AIL PROTECTED]> writes:
>
> > Hi,
> > I have a problem running echo inside Makefile.
> > Here is the Makefile:
> > all:
> > @echo "string"
> > @echo -e -n "string"
> > The output is:
> > string
> > -e -n string
> > The
On 20/11/2007, Kfir Lavi <[EMAIL PROTECTED]> wrote:
> Ok,
> make -d don't show much.
> I have attached the two files: Makefile and make.log
That's weird - your make.log says:
Must remake target `all'.
-e -n aaa
(i.e. "echo" is missing").
But running "make -d -n" on my machine (Debian Etch, make
Ok,
make -d don't show much.
I have attached the two files: Makefile and make.log
On Nov 20, 2007 2:28 PM, Ilya Konstantinov <[EMAIL PROTECTED]>
wrote:
> You can run 'make -d' to get more insight into what Make does.
> There aren't supposed to be any internal Make commands. There are internal
> f
"Kfir Lavi" <[EMAIL PROTECTED]> writes:
> Hi,
> I have a problem running echo inside Makefile.
> Here is the Makefile:
> all:
> @echo "string"
> @echo -e -n "string"
> The output is:
> string
> -e -n string
> The
You can run 'make -d' to get more insight into what Make does.
There aren't supposed to be any internal Make commands. There are internal
functions, but the syntax for calling them is $(function ...), e.g. $(info
foobar)
On Nov 20, 2007 2:16 PM, Kfir Lavi <[EMAIL PROTECTED]> wrote:
> Does make us
7.10
> > May be your bash for some reason running not it's
> > embedded echo, but external one .
> >
> > Anyway, what about printf, is it work for you ?
> >
> > Valery.
> >
> > >
> > > Kfir
> > >
> > > On Nov 20, 2
mbedded echo, but external one .
>
> Anyway, what about printf, is it work for you ?
>
> Valery.
>
> >
> > Kfir
> >
> > On Nov 20, 2007 1:22 PM, Valery Reznic
> > <[EMAIL PROTECTED]> wrote:
> >
> > >
> > >
> > >
>
ay, what about printf, is it work for you ?
Valery.
>
> Kfir
>
> On Nov 20, 2007 1:22 PM, Valery Reznic
> <[EMAIL PROTECTED]> wrote:
>
> >
> >
> >
> >
> > --- Amos Shapira <[EMAIL PROTECTED]> wrote:
> >
> > > On
PROTECTED]>
> > wrote:
> > > Hi,
> > > I have a problem running echo inside Makefile.
> > > Here is the Makefile:
> > > all:
> > > @echo "string"
> > > @echo -e -n "string"
> You could try to use pri
--- Amos Shapira <[EMAIL PROTECTED]> wrote:
> On 20/11/2007, Kfir Lavi <[EMAIL PROTECTED]>
> wrote:
> > Hi,
> > I have a problem running echo inside Makefile.
> > Here is the Makefile:
> > all:
> > @echo "string"
> >
On 20/11/2007, Kfir Lavi <[EMAIL PROTECTED]> wrote:
> Hi,
> I have a problem running echo inside Makefile.
> Here is the Makefile:
> all:
> @echo "string"
> @echo -e -n "string"
>
> The output is:
> string
> -e -n string
>
Hi,
I have a problem running echo inside Makefile.
Here is the Makefile:
all:
@echo "string"
@echo -e -n "string"
The output is:
string
-e -n string
The problem is the second @echo command. It prints '-e -n' instead of
interpreting those options.
I
24 matches
Mail list logo
