On Fri, 2010-07-16 at 23:44 -0500, Bruce Dubbs wrote:
That's a good reason. We each have our preferences. I like jhalfs for
lfs and scripts for blfs.
Scripts for BLFS is a good challenge too, since 1) there are a lot more
packages (and flavours of build) involved, and 2), it's not all a
On Wed, 2010-07-14 at 13:37 -0500, Mike McCarty wrote:
Simon Geard wrote:
[...]
That's experience talking, I might add. My LFS builds are almost always
scripted, and more than once, I've investigated a compile problem that's
Is there a reason you prefer a script to an automated
Simon Geard wrote:
On Wed, 2010-07-14 at 13:37 -0500, Mike McCarty wrote:
Simon Geard wrote:
[...]
That's experience talking, I might add. My LFS builds are almost always
scripted, and more than once, I've investigated a compile problem that's
Is there a reason you prefer a script to an
Simon Geard wrote:
[...]
That's experience talking, I might add. My LFS builds are almost always
scripted, and more than once, I've investigated a compile problem that's
Is there a reason you prefer a script to an automated package like
JHALFS?
Mike
--
On Sat, 2010-07-03 at 03:40 +0300, Face wrote:
it has been over 2 months since my first try i think. going through
the book manually over and over, I had many mistypes which force me to
start over. Therefore, I put them in a script so i can avoid mistypes.
To start with, copy-paste from the
after each command a Footer script will be call with a message saying
press any key to continue or q to Exit
so if i did not see any error i will press enter and if there is an
error i will exit.
I am not saying this is the best way but the script only print stderr
and i will know if the
what do you mean by I suggest trying to automate that process
On Sat, Jul 3, 2010 at 8:11 AM, Simon Geard delga...@ihug.co.nz wrote:
On Sat, 2010-07-03 at 03:40 +0300, Face wrote:
it has been over 2 months since my first try i think. going through
the book manually over and over, I had many
On 03/07/10 00:17, Baho Utot wrote:
Neal Murphy wrote:
Cleverly crafted, you should be able to catch most of the errors when they
happen while maintaining a readable script.
If using bash a simple:
#!/bin/bash -e
set +h
at the top of the script works, bails on any error
One nitpick
On 03/07/10 07:40, Face wrote:
what do you mean by I suggest trying to automate that process
He just meant that writing scripts is hard to get right. Though in my
experience, it's worth the effort in the long run. Partly for the
benefit of learning the programming language you've chosen and
On 7/3/10, Andrew Benton b3n...@gmail.com wrote:
If using bash a simple:
#!/bin/bash -e
set +h
at the top of the script works, bails on any error
Or
set -e
A few package maintainers manage to return 0 success from configure
even when the configure fails. These may be rare or nonexistent
On Thu, 2010-07-01 at 22:39 -0400, Neal Murphy wrote:
Sometimes, deleting everything and starting anew is all you *can* do.
More than that, it's often easier too. Less effort to start again paying
closer attention to the instructions, than to spend time trying to work
out how to fix the results
On 2 July 2010 01:57, Face falaz...@gmail.com wrote:
Ken,
Well, I am really sorry for all the trouble i caused. I start over b/c
i could not fix the earlier Problem, really sorry.
We're here to build systems. A large part of this is learning
from our mistakes [ aside: some people claim to
On Friday 02 July 2010 07:53:19 Ken Moffat wrote:
... but people can make the same error each time.
And that's really OK: it's a mere reflection of their computer skills and we
can help them with that. But expecting different results every time is a sure
sign of insanity, or so I'm told. :)
Neal Murphy wrote:
On Friday 02 July 2010 07:53:19 Ken Moffat wrote:
... but people can make the same error each time.
And that's really OK: it's a mere reflection of their computer skills and we
can help them with that. But expecting different results every time is a sure
sign of
well, thank you all, i will start over and see what will happen.
I am using a shell script to do the book if someone could take a look
at it, that would be nice .
Sincerely
Install-Ch5.sh
Description: Bourne shell script
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
On Friday 02 July 2010 15:11:31 Face wrote:
well, thank you all, i will start over and see what will happen.
I am using a shell script to do the book if someone could take a look
at it, that would be nice .
Sincerely
Ah, you don't seem to have error detection in your script.
After many of
Neal Murphy wrote:
On Friday 02 July 2010 15:11:31 Face wrote:
well, thank you all, i will start over and see what will happen.
I am using a shell script to do the book if someone could take a look
at it, that would be nice .
Sincerely
Ah, you don't seem to have error detection
Neal,
thanks alot for going through the script I appreciated.
well, I do have error detection i disable it on the script i attached.
its like this
Chapter5(){
GZ=tar -zxf
BZ=tar xjvf
exec 31 #Start- This to handel stderr
Chapter5_4 21 13 | sh $Error
Neal Murphy wrote:
On Friday 02 July 2010 15:11:31 Face wrote:
well, thank you all, i will start over and see what will happen.
I am using a shell script to do the book if someone could take a look
at it, that would be nice .
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
Face wrote:
well, thank you all, i will start over and see what will happen.
I am using a shell script to do the book if someone could take a look
at it, that would be nice .
Ignore the previous post I accidentally sent.
For any complex task like LFS, you should be able to successfully do the
it has been over 2 months since my first try i think. going through
the book manually over and over, I had many mistypes which force me to
start over. Therefore, I put them in a script so i can avoid mistypes.
Yes i do agree the script is way too long , however, alot of the lines
is about tell me
Face wrote:
it has been over 2 months since my first try i think. going through
the book manually over and over, I had many mistypes which force me to
start over. Therefore, I put them in a script so i can avoid mistypes.
Yes i do agree the script is way too long , however, alot of the lines
:) Hope you did not took my respond the wrong way, i do appreciated
every advice.
thx
On Sat, Jul 3, 2010 at 4:28 AM, Bruce Dubbs bruce.du...@gmail.com wrote:
Face wrote:
it has been over 2 months since my first try i think. going through
the book manually over and over, I had many mistypes
On Sat, 2010-07-03 at 02:19 +0300, Face wrote:
Neal,
thanks alot for going through the script I appreciated.
well, I do have error detection i disable it on the script i attached.
its like this
That's not error detection - that's just logging stderr. The biggest
problem with scripted
Hello All,
lfs:/mnt/lfs/sources/binutils-2.20.1$ CC=$LFS_TGT-gcc -B/tools/lib/ \
AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib \
../binutils-2.20.1/configure --prefix=/tools \
--disable-nls --with-lib-path=/tools/lib
checking build system type...
On 1 July 2010 23:12, Face falaz...@gmail.com wrote:
Hello All,
lfs:/mnt/lfs/sources/binutils-2.20.1$ CC=$LFS_TGT-gcc -B/tools/lib/ \
AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib \
../binutils-2.20.1/configure --prefix=/tools \
--disable-nls
Ken,
Well, I am really sorry for all the trouble i caused. I start over b/c
i could not fix the earlier Problem, really sorry.
section 5.8 went Ok (I think) here is the out
lfs:/mnt/lfs/sources$ echo 'main(){}' dummy.c
lfs:/mnt/lfs/sources$ $LFS_TGT-gcc -B/tools/lib dummy.c
27 matches
Mail list logo
