I have gone through the lfs 6.5 book 7 times. I have copied all of the
commands in the book into scripts so I would not make any typo
mistakes. I have been able to boot into the new system 4 times. The
problem is that 90% of the stuff that appeared to be getting compiled
and installed is no where t
On 11/27/2009 08:47 AM, stosss wrote:
> I have gone through the lfs 6.5 book 7 times. I have copied all of the
> commands in the book into scripts so I would not make any typo
> mistakes. I have been able to boot into the new system 4 times. The
> problem is that 90% of the stuff that appeared to b
On 11/27/2009 09:19 AM, Chris Staub wrote:
>
> Sorry, can't help you without more specifics. Name some of the programs,
> specifically, that you cannot find.
>
> I also note you mention make but not configure...
Also, specify exactly how you installed one of these packages you can't
find...config
On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
> On 11/27/2009 08:47 AM, stosss wrote:
>> I have gone through the lfs 6.5 book 7 times. I have copied all of the
>> commands in the book into scripts so I would not make any typo
>> mistakes. I have been able to boot into the new system 4 times.
On 11/27/2009 09:32 AM, stosss wrote:
> On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
> About the only things that are there is the Linux kernel, bash, grub
> and coreutils, beyond that there is nothing else. The /var /usr /sys
> directories are empty. there is no vi or vim cmd, no tar cmd,
On Fri, Nov 27, 2009 at 9:24 AM, Chris Staub wrote:
> On 11/27/2009 09:19 AM, Chris Staub wrote:
>>
>> Sorry, can't help you without more specifics. Name some of the programs,
>> specifically, that you cannot find.
>>
>> I also note you mention make but not configure...
>
> Also, specify exactly h
On Fri, Nov 27, 2009 at 9:35 AM, Chris Staub wrote:
> On 11/27/2009 09:32 AM, stosss wrote:
>> On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
>> About the only things that are there is the Linux kernel, bash, grub
>> and coreutils, beyond that there is nothing else. The /var /usr /sys
>> dir
On 11/27/2009 09:38 AM, stosss wrote:
>
> 1st half of one of my scripts
>
> #!/bin/bash
> tar -xvf vim-7.2.tar.bz2
> cd vim72
> patch -Np1 -i ../vim-7.2-fixes-5.patch
> echo '#define SYS_VIMRC_FILE "/etc/vimrc"'>> src/feature.h
> ./configure --prefix=/usr --enable-multibyte
> make
> make test
>
>
On Fri, Nov 27, 2009 at 9:39 AM, stosss wrote:
> On Fri, Nov 27, 2009 at 9:35 AM, Chris Staub wrote:
>> On 11/27/2009 09:32 AM, stosss wrote:
>>> On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
>>> About the only things that are there is the Linux kernel, bash, grub
>>> and coreutils, beyond
On 11/27/2009 09:39 AM, stosss wrote:
>>
> Yes I mean empty. no files no directories nothing.
That is simply not possible, as you set up several directories in /usr
right at the beginning of Chapter 6, so even if nothing is installed you
should at least have /usr/bin, /usr/lib, etc...
--
http:
On Fri, Nov 27, 2009 at 9:42 AM, stosss wrote:
> On Fri, Nov 27, 2009 at 9:39 AM, stosss wrote:
>> On Fri, Nov 27, 2009 at 9:35 AM, Chris Staub wrote:
>>> On 11/27/2009 09:32 AM, stosss wrote:
On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
About the only things that are there is
On Fri, Nov 27, 2009 at 9:35 AM, Chris Staub wrote:
> On 11/27/2009 09:32 AM, stosss wrote:
>> On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub wrote:
>> About the only things that are there is the Linux kernel, bash, grub
>> and coreutils, beyond that there is nothing else. The /var /usr /sys
>> dir
On Fri, Nov 27, 2009 at 9:41 AM, Chris Staub wrote:
> On 11/27/2009 09:38 AM, stosss wrote:
>>
>> 1st half of one of my scripts
>>
>> #!/bin/bash
>> tar -xvf vim-7.2.tar.bz2
>> cd vim72
>> patch -Np1 -i ../vim-7.2-fixes-5.patch
>> echo '#define SYS_VIMRC_FILE "/etc/vimrc"'>> src/feature.h
>> ./co
On Fri, Nov 27, 2009 at 9:43 AM, Chris Staub wrote:
> On 11/27/2009 09:39 AM, stosss wrote:
>
>>>
>> Yes I mean empty. no files no directories nothing.
>
> That is simply not possible, as you set up several directories in /usr
> right at the beginning of Chapter 6, so even if nothing is installed
On Fri, Nov 27, 2009 at 9:41 AM, Chris Staub wrote:
> On 11/27/2009 09:38 AM, stosss wrote:
>>
>> 1st half of one of my scripts
>>
>> #!/bin/bash
>> tar -xvf vim-7.2.tar.bz2
>> cd vim72
>> patch -Np1 -i ../vim-7.2-fixes-5.patch
>> echo '#define SYS_VIMRC_FILE "/etc/vimrc"'>> src/feature.h
>> ./co
On 11/27/2009 09:50 AM, stosss wrote:
>
> Yes I know, but there is nothing in them.
Um, then clearly you forgot to create them. Whether you have the
directory creation in your scripts, or manually, you skipped that part.
Of course that's far from the only problem, but if even basic
directories
On 11/27/2009 09:54 AM, stosss wrote:
>
> vim is just one of the apps missing. Like I said earlier the only
> things that appear to be there are Linux kernel, bash, coreutils and
> grub. 90% of the apps in the book are not there.
Um, and what about the make output that I *just* mentioned? I assume
On 11/27/2009 09:54 AM, stosss wrote:
>
> vim is just one of the apps missing. Like I said earlier the only
> things that appear to be there are Linux kernel, bash, coreutils and
> grub. 90% of the apps in the book are not there.
Provide the output of "ls -l /bin"
--
http://linuxfromscratch.org/m
On Fri, Nov 27, 2009 at 9:56 AM, Chris Staub wrote:
> On 11/27/2009 09:50 AM, stosss wrote:
>>
>> Yes I know, but there is nothing in them.
>
> Um, then clearly you forgot to create them. Whether you have the
> directory creation in your scripts, or manually, you skipped that part.
> Of course tha
On 11/27/2009 10:05 AM, stosss wrote:
>
> Find I will figure it out myself. I did not forget to do anything. I
> have gone over the book and the scripts more than a dozen times. I set
> the scripts up so that each one echos the next script to be run. i
> just got through running the entire book fro
Chris Staub wrote:
> On 11/27/2009 10:05 AM, stosss wrote:
>> Find I will figure it out myself. I did not forget to do anything. I
>> have gone over the book and the scripts more than a dozen times. I set
>> the scripts up so that each one echos the next script to be run. i
>> just got through runn
Le vendredi 27 novembre à 15:38, stosss a écrit :
> 1st half of one of my scripts
>
> #!/bin/bash
> tar -xvf vim-7.2.tar.bz2
> cd vim72
> patch -Np1 -i ../vim-7.2-fixes-5.patch
> echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h
> ./configure --prefix=/usr --enable-multibyte
> make
> mak
Something that happened quite a few times while automating with scripts, is
that chroot failed, then I got everything installed on the host over
original system.
As you mentioned vim, you can try:
$ vi
from the original host prompt to see if the version is matching the one from
LFS. If so, and you
2009/11/27 Philippe Delavalade :
> Le vendredi 27 novembre à 15:38, stosss a écrit :
>> 1st half of one of my scripts
>>
>> #!/bin/bash
>> tar -xvf vim-7.2.tar.bz2
>> cd vim72
>> patch -Np1 -i ../vim-7.2-fixes-5.patch
>> echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h
>> ./configure --p
I am using the lfs 6.3 last version LiveCD. The computer does not have
anything installed on it.
I started over. I deleted the partitions on the hard drive and created
new ones and started at the beginning of the book. I have been running
the commands manually by copy and paste at the cli. Everythi
> I am using the lfs 6.3 last version LiveCD. The computer does not have
> anything installed on it.
> I started over. I deleted the partitions on the hard drive and created
> new ones and started at the beginning of the book. I have been running
> the commands manually by copy and paste at the cli
On Sat, Nov 28, 2009 at 5:12 AM, Timothy Rice wrote:
>> I am using the lfs 6.3 last version LiveCD. The computer does not have
>> anything installed on it.
>> I started over. I deleted the partitions on the hard drive and created
>> new ones and started at the beginning of the book. I have been ru
On 11/28/09, stosss wrote:
> I am only using the lfs 6.3 LiveCD (this is the newest and last lfs
> LiveCD released) so I will have a working environment to build lfs
Unless I am mistaken, everything in ch6-8 is done within chroot.
Then it is imperative to be certain that
6.2. Preparing Virtual Ke
2009/11/28 stosss :
> I am using the lfs 6.3 last version LiveCD. The computer does not have
> anything installed on it.
> I started over. I deleted the partitions on the hard drive and created
> new ones and started at the beginning of the book. I have been running
> the commands manually by copy
stosss wrote:
> On Fri, Nov 27, 2009 at 9:24 AM, Chris Staub wrote:
>
>
[putolin]
> 1st half of one of my scripts
>
>
[putolin]
Here is my script that works
#!/tools/bin/bash -
CURRDIR=$(pwd)
SRC=/sources
tar xvf $SRC/vim-7.2.tar.bz2
cd vim72
patch -Np1 -i $SRC/vim-7.2-fixes-5.patch
On 11/28/09, Baho Utot wrote:
> make test | tee $CURRDIR/06.58.Check.log
> make install | tee $CURRDIR/06.58.Install.log
Logging helps so much when things go wrong.
As already mentioned
> Scripting an LFS build is *hard*
> 1. Use jhalfs. That is the most consistent way to do things
> and it k
I think it is time to try jhalfs
On Nov 28, 2009 4:43 PM, "linux fan" wrote:
On 11/28/09, Baho Utot wrote: > make test | tee $CURRDIR/06.58.Check.log >
make install | tee $CURR...
Logging helps so much when things go wrong.
As already mentioned
> Scripting an LFS build is *hard*
> 1. Use jhal
linux fan wrote:
> On 11/28/09, Baho Utot wrote:
>
>
>> make test | tee $CURRDIR/06.58.Check.log
>> make install | tee $CURRDIR/06.58.Install.log
>>
> Logging helps so much when things go wrong.
>
> As already mentioned
>
>
>> Scripting an LFS build is *hard*
>>
>
> [putolin]
> I on
On Friday 27 November 2009 22:50:12 stosss wrote:
> On Fri, Nov 27, 2009 at 9:43 AM, Chris Staub wrote:
> > On 11/27/2009 09:39 AM, stosss wrote:
> >> Yes I mean empty. no files no directories nothing.
> >
> > That is simply not possible, as you set up several directories in /usr
> > right at the
34 matches
Mail list logo
