For automation LFS, I've writtten the scriptaccordnig to instruction from chapter 5 that:http://www.dzti.edu.lv/isp-serv/a7/lfs-toolkit.txt For building I use LiveCD:http://ftp.osuosl.org/pub/lfs-livecd/lfslivecd-x86-6.2-pre3.isoI've mounted /dev/sda4, then setup network and sshd,copied needed src
Andrejs Spunitis wrote:
> /**/For automation LFS, I've writtten the script
> accordnig to instruction from chapter 5 that:
> http://www.dzti.edu.lv/isp-serv/a7/lfs-toolkit.txt
>
> For building I use LiveCD:
> http://ftp.osuosl.org/pub/lfs-livecd/lfslivecd-x86-6.2-pre3.iso
>
> I've mounted /dev/
Recently, Somebody Somewhere wrote these words
> Hi list,
>
> I'm new to this list (and hence cannot reply to an earlier mail), but I
> searched the archive and came across an earlier mailexchange dealing
> with the fact that SVN-20060220 appears unbootable.
>
> I have exactly the same problem: T
Jürg Billeter wrote:
> I know that it's far from ideal but the only ideal way I see would be to
> extensively add __KERNEL__ ifdefs to the linux headers upstream so that
> the script could recognize automatically which headers are
> kernel-internal. Unfortunately this probably won't happen in the
Jim Gifford wrote:
> On a few of the lists I have seen this done with success
> and found out that this is the recommended build method for GLIBC, still
> checking on the status GCC and this situation.
It has *always* been an option to compile Glibc against raw headers.
Nothing there has changed.
Joel Miller wrote:
Please send support requests to lfs-support.
And please trim your quotes! Nearly ~40 lines of quoted email to add a
6-word sentence is ridiculous.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above
Matthew Burgess wrote:
> And please trim your quotes! Nearly ~40 lines of quoted email to add a
> 6-word sentence is ridiculous.
My apologies to the list. I had just sent off a bunch of emails rapid
fire and the previous one in this thread being the last one, I guess I
wasn't paying too close at
In the Chapter 5 instructions of Gawk, it says this:
"This bug leads to, e.g., Gettext testsuite failures."
There really is no reason to put the ", e.g., " in that sentence.
It should be removed. If it leads to failures, then specify it, we
shouldn't be beating around the bush with "for example".
Bruce Dubbs wrote:
Jeremy, if you have time, would you take a look? If not, I can get back
to it this evening.
Did this get done? I've been away for the past few days and only just
now got back.
Greetings everyone. ;)
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http:
Jeremy Huntwork wrote:
Did this get done? I've been away for the past few days and only just
now got back.
Hi Jeremy,
I sent a patch and Bruce applied it which basically change all the
occurances of newlfscounter.cgi to lfscounter.cgi internally, since they
were causing problems. I think th
Randy McMurchy wrote:
In the Chapter 5 instructions of Gawk, it says this:
"This bug leads to, e.g., Gettext testsuite failures."
There really is no reason to put the ", e.g., " in that sentence.
It should be removed. If it leads to failures, then specify it, we
shouldn't be beating around the
11 matches
Mail list logo
