Can LFS 6.4 be built on a x86_64 system or will it build only on x86?
If I have a 64 bit distro installed (arch) should it not build.. as 64
bit instead of 32 bit?
If not what is the difference between CLFS-1.1.0-x86_64-64 and the
CLFS-1.1.0-x86_64?
Thanks
--
http://linuxfromscratch.org/mail
tarballs went to .used for reuse in case needed... unpacked source folder
deleted as the book says...
On Thu, Jul 23, 2009 at 1:25 AM, Chris Staub wrote:
> RaptorX wrote:
> >
> > hahaha
> >
> > thats exactly what i meant, but the source package not the extracted ones
> >
> Huh? I have no idea
RaptorX wrote:
>
> hahaha
>
> thats exactly what i meant, but the source package not the extracted ones
>
Huh? I have no idea what you mean here. Are you referring to the source
tarball, or the unpacked source directory? If you mean that you only
moved the tarballs elsewhere, then what did you
hahaha
thats exactly what i meant, but the source package not the extracted ones
On Thu, Jul 23, 2009 at 1:16 AM, Chris Staub wrote:
> RaptorX wrote:
> >
> > the thing is that according to the book: "After installing each package,
> > delete its source and build directories, unless specifically
RaptorX wrote:
>
> the thing is that according to the book: "After installing each package,
> delete its source and build directories, unless specifically instructed
> otherwise. Deleting the sources prevents mis-configuration when the same
> package is reinstalled later."
>
> what i did is th
you are right... the thing is that when i did this:
tar -jxf ../mpfr-2.3.2.tar.bz2
mv mpfr-2.3.2 mpfr
tar -jxf ../gmp-4.2.4.tar.bz2
mv gmp-4.2.4 gmp
I assumed that it was extracted in ../
but actually was extracted in the current directory...
the thing is that according to the book: "After insta
RaptorX wrote:
> Im in the second pass of the GCC compilation... book LFS 6.4 chapter 5.12...
>
> and im getting
>
>
> */checking for correct version of gmp.h... no
> configure: error: Building GCC requires GMP 4.1+ and MPFR 2.3.0+.
> Try the --with-gmp and/or --with-mpfr options to specify thei
Im in the second pass of the GCC compilation... book LFS 6.4 chapter 5.12...
im issuing this command
*../gcc-4.3.2/configure --prefix=/tools \
--with-local-prefix=/tools --enable-clocale=gnu \
--enable-shared --enable-threads=posix \
--enable-__cxa_atexit --enable-languages=c,c++ \
Bruce Dubbs wrote:
> Justin P. Mattock wrote:
>
>> Any ideas on why ctl+alt+del doesn't shutdown my machine?
>> the inittab I copied was from 6.54.3
>> which has the entry there, but when exiting
>> the xserver and issuing those commands, I have
>> no movement.(also my user name is in shutdown.
Bruce Dubbs wrote:
> Justin P. Mattock wrote:
>
>> Any ideas on why ctl+alt+del doesn't shutdown my machine?
>> the inittab I copied was from 6.54.3
>> which has the entry there, but when exiting
>> the xserver and issuing those commands, I have
>> no movement.(also my user name is in shutdown.
Justin P. Mattock wrote:
> Any ideas on why ctl+alt+del doesn't shutdown my machine?
> the inittab I copied was from 6.54.3
> which has the entry there, but when exiting
> the xserver and issuing those commands, I have
> no movement.(also my user name is in shutdown.allow)
Do you have
ca:12345:
Any ideas on why ctl+alt+del doesn't shutdown my machine?
the inittab I copied was from 6.54.3
which has the entry there, but when exiting
the xserver and issuing those commands, I have
no movement.(also my user name is in shutdown.allow)
Justin P. Mattock
--
http://linuxfromscratch.org/mailman/l
: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
it is perfectly fine... for me thats the point of going along with LFS right
now.
:D
On Wed, Jul 22, 2009 at 1:02 PM, William Immendorf wrote:
> On Wed, Jul 22, 2009 at 4:58 AM, wrote:
> > Can someone use LFS to create a new distribution brand and art instead of
> using the host brand??? Let's
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
Hi RaptorX
Your command has double quotes between double quotes (nested double quotes). In
such cases the shell doesn't know where the quoted statement finishes. You need
to use escaped double quotes for this case. Or you can use single quotes for
outer quotes and double for inner.
Use of sing
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
On Wed, Jul 22, 2009 at 4:58 AM, wrote:
> Can someone use LFS to create a new distribution brand and art instead of
> using the host brand??? Let's say if he wants to create an LFS system using
> Ubuntu and rebrand it to XYZ Linux...
He could, if he knew Gimp/Inkscape and knows Linux good enough
Can someone use LFS to create a new distribution brand and art instead of using
the host brand??? Let's say if he wants to create an LFS system using Ubuntu
and rebrand it to XYZ Linux...
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/
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=
Craig Jackson wrote:
>> Anyone else have ideas on how we can come together and get the project
>> moving ahead at a faster pace?
>>
>
> I just thought of the blood bank analogy. When someone offers to
> donate, the blood bank tells the donor what type of blood is most
> needed. If there is
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
44 matches
Mail list logo
