This issue was posted onto lfs-support mailing list yesterday (see:
http://linuxfromscratch.org/pipermail/lfs-support/2010-June/038814.html ),
unluckly I disabled the mail delivery of LFS mailing list some days ago, so I
can't continue discuss it on the lfs-support mailing list. And, I consider
On Fri, Jun 4, 2010 at 1:40 AM, littlebat dashing.m...@gmail.com wrote:
This issue was posted onto lfs-support mailing list yesterday (see:
http://linuxfromscratch.org/pipermail/lfs-support/2010-June/038814.html ),
unluckly I disabled the mail delivery of LFS mailing list some days ago, so I
Then this evening I made a copy of the script without that line and
recompiled glibc with the Stage2 compiler as the next step. No
problem this time. So I think I have a fairly straightforward
workaround. I don't imagine there was any need for the nscd code to
get through the gcc
On 6/4/10, Paul Rogers paulgrog...@fastmail.fm wrote:
So the problem was the Chapter 5 gcc?
I'm not sure that follows.
Seems to.
Intending to attempt to duplicate __stack_chk_guard error in chapter 6
while building lfs-6.6 from lfs-6.1.1 ...
The theory being that the host gcc/glibc ideal
On 6/4/10, linux fan linuxscra...@gmail.com wrote:
So the problem was the Chapter 5 gcc?
I'm not sure that follows.
Seems to.
... I decide to break out of it, and try something
... This diff in commands
=
---
Paul Rogers wrote:
Then this evening I made a copy of the script without that line and
recompiled glibc with the Stage2 compiler as the next step. No
problem this time. So I think I have a fairly straightforward
workaround. I don't imagine there was any need for the nscd code to
get through
