:D
yesh... the problem was that i was typing "{ ls; }" and when using the time
command you should not quote the brackets since bash will try to read them
litterally...
time "{ ls; }" does not work
time { ls; } works fine
On Wed, Jul 22, 2009 at 7:53 PM, Mike McCarty wrote:
> RaptorX wrote:
> >
RaptorX wrote:
> while re-reading Bruce's comment i just tried:
>
> time { ls; }
>
> and it worked fine... I feel dumb now... I did try it before and it didnt
> work!!
It should work. The syntax of the builtin is
time
Now may be any command, including a compound one.
However, when I encount
while re-reading Bruce's comment i just tried:
time { ls; }
and it worked fine... I feel dumb now... I did try it before and it didnt
work!!
any way... it is totally correct what Bruce explained maybe i misspelled and
didnt notice??
Thanks for all the help guys!!!
On Wed, Jul 22, 2009 at 7:18
>
> This stuff all gets confusing, I know, especially since bash
> has incorporated even the kitchen sink into it. IMO, bash
> has gotten out of hand, similar to emacs. However, that's
> getting into a whole 'nother discussion, which is OT for
> this echo. I do think it would be less confusing if b
actually for me it *is* necessary to pass the -c option after bash...:
This is BASH 3.1 - DISPLAY on :0.0
[~]$ *time bash "{ ls; }"*
> bash: { ls; }: No such file or directory
real0m0.002s
user0m0.000s
sys 0m0.001s
[~]$ *time bash -c "{ ls; }"*
> Azureus Downloads
Trent Shea wrote:
> On Wednesday 22 July 2009 10:32:34 Trent Shea wrote:
>>> CC="gcc -B/usr/bin/" time { ls; }
>> Actually, this doesn't work for me either, :) now I'm a little curious...
>
> I just assumed this set a variable and went on to the next command, but
> obviously not.
It changes the
RaptorX wrote:
>
> so basically i had to invoke* bash* AND add the* -c* option before adding
> the wraps...
That's not necessary as I already explained.
> which in the book is not explained...
This is bash functionality. It is out of scope to explain how to use tools.
However the book does poi
>
> No, what you are doing with the quotes is telling bash to that everything
> within
> the quotes is a single parameter. There is no executable
> {-space-ls-space-}.
>
> Note that the 'time' builtin must be first, so
>
> CC="gcc -B/usr/bin/" time { ls; }
>
> is invalid. It must be:
>
> time { C
On Wednesday 22 July 2009 10:32:34 Trent Shea wrote:
> > CC="gcc -B/usr/bin/" time { ls; }
>
> Actually, this doesn't work for me either, :) now I'm a little curious...
I just assumed this set a variable and went on to the next command, but
obviously not.
Trent.
--
http://linuxfromscratch.org
i did try the space + semicolon later on and didnt work either...
but just did
time bash -c " { ls; } "
and went perfectly
so basically i had to invoke* bash* AND add the* -c* option before adding
the wraps...
which in the book is not explained...
Thanks to Mike for the answer and to Bruce for
On Wednesday 22 July 2009 10:26:29 Mike McCarty wrote:
> CC="gcc -B/usr/bin/" time { ls; }
Actually, this doesn't work for me either, :) now I'm a little curious...
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the
RaptorX wrote:
> actually in this system:
> Slackware 12.2
>
> that returns with an error...
>
> *[~]$ time bash "{ ls }"
> bash: { ls }: No such file or directory
>
> real0m0.002s
> user0m0.000s
> sys 0m0.002s
> [~]$*
>
> it really seems to be with the version of bash that Slackwar
On Wednesday 22 July 2009 10:26:29 Mike McCarty wrote:
> The original question related to a command like this:
>
> $ CC="gcc -B/usr/bin/" time { ls; }
The command in the original post was still not properly formatted. It should
work with the space and semi colon inserted.
Trent.
--
http://linu
Trent Shea wrote:
> On Wednesday 22 July 2009 07:46:58 RaptorX wrote:
>> the following commands work fine:
>>
>> time ls
>>
>> time "ls"
>>
>> time 'ls'
>>
>> this one doesnt:
>>
>> time {ls}
>>
>> time { ls }
>>
>>
>> so do we really have to enclose in brackets?
>
> http://tldp.org/LDP/abs/html/f
RaptorX wrote:
> Hi guys,
>
> This is my first time building LFS 6.4, im in chapter 5.4.1 at the moment
> and I wanted to run the benchmark with the time command...
You have to understand how bash parses the command line. It separates reserved
words by whitespace and separates commands by semi-
RaptorX wrote:
> actually in this system:
> Slackware 12.2
>
> that returns with an error...
>
> *[~]$ time bash "{ ls }"
> bash: { ls }: No such file or directory
>
> real0m0.002s
> user0m0.000s
> sys 0m0.002s
> [~]$*
>
> it really seems to be with the version of bash that Slackwar
On Wednesday 22 July 2009 07:46:58 RaptorX wrote:
> the following commands work fine:
>
> time ls
>
> time "ls"
>
> time 'ls'
>
> this one doesnt:
>
> time {ls}
>
> time { ls }
>
>
> so do we really have to enclose in brackets?
http://tldp.org/LDP/abs/html/functions.html
time { ls; }
The first s
actually in this system:
Slackware 12.2
that returns with an error...
*[~]$ time bash "{ ls }"
bash: { ls }: No such file or directory
real0m0.002s
user0m0.000s
sys 0m0.002s
[~]$*
it really seems to be with the version of bash that Slackware uses.
> The reason for this is that tim
RaptorX wrote:
> the following commands work fine:
>
> time ls
>
> time "ls"
>
> time 'ls'
>
> this one doesnt:
>
> time {ls}
The reason for this is that time simply passes its argument to
one of the exec() calls. So, "{ls}" is not the name of any
command, and it can't be executed. However
t
well, it has to do with the host then, cause im using Slackware 12.2 as
host.
maybe the binutils there work little bit different...
no problem then I will continue without the time measuring since is not
really that important.
thanks for the help guys
On Wed, Jul 22, 2009 at 4:37 PM, Jaiyson w
I don't know if time bash "{ CC=gcc...}" will work for you...its been
a couple months since I did my build so I'm already starting to
forget the terminology...but I built my system using the 6.4 book and
used the host 6.3 live cd. The only difference is that I used all the
packages recommended
the following commands work fine:
time ls
time "ls"
time 'ls'
this one doesnt:
time {ls}
time { ls }
so do we really have to enclose in brackets?
--
==
"The shortest way to do many things is to do only one thing at a time
I was just right now poking with that... it doesnt take it either...
Now I just realized that if I make
time CC="gcc -B
without any quotation it does take the time of the first command but i never
realized because the screen is constantly moving... here is what i got:
checking whether to en
se of single quotes in outer quotes means everything (character, number or
special character) is passed on to the command.
Thanks,
Aditya
From: RaptorX
To: LFS Support List
Sent: Wednesday, 22 July, 2009 12:55:22 PM
Subject: Re: time command help
If I understoo
thanks for the info... I am sure i am using 6.4... the problem was that i
was using livecd... it seems to be outdated but now i downloaded from the
book all the packages.
so I should try:
time bash "{ CC=gcc..}" ??
On Wed, Jul 22, 2009 at 1:05 PM, William Immendorf wrote:
> On Wed, Jul 22
On Wed, Jul 22, 2009 at 2:25 AM, RaptorX wrote:
> If I understood you correctly i should try:
>
> time bash "{/foo/bar}"
>
> the output is the same...
Try putting a space after the first bracket. It works for me.
Also, it looks like you're using 6.3. (because you're using gcc
4.1.2.) I don't recom
If I understood you correctly i should try:
time bash "{/foo/bar}"
the output is the same...
time bash "{CC="gcc -B/usr/bin" ../gcc-4.1.2/configure --prefix=/tools
--with-local-prefix=/tools --disable-nls --disable-shared --disable-libssp
--enable-languages=c && make && make install}"
bash: {CC=
RaptorX wrote:
> Hi guys,
>
> This is my first time building LFS 6.4, im in chapter 5.4.1 at the moment
> and I wanted to run the benchmark with the time command...
>
> as far as I understood I should make something like:
>
> *CC="gcc -B/usr/bin/" time {../binutils-2.18/configure --prefix=/tools
Hi guys,
This is my first time building LFS 6.4, im in chapter 5.4.1 at the moment
and I wanted to run the benchmark with the time command...
as far as I understood I should make something like:
*CC="gcc -B/usr/bin/" time {../binutils-2.18/configure --prefix=/tools
--disable-nls --disable-werror
29 matches
Mail list logo
