On Tue, Mar 20, 2018 at 05:17:35PM +0200, James wrote:
> 2018-03-20 17:08 GMT+02:00, Ken Moffat <zarniwh...@ntlworld.com>:
> > On Tue, Mar 20, 2018 at 04:13:16PM +0200, James wrote:
> >> 2018-03-20 0:58 GMT+02:00, Ken Moffat <zarniwh...@ntlworld.com>:
> >> > On Mon, Mar 19, 2018 at 11:06:08PM +0200, Кирилл wrote:
> >
> > I think you said you had made a symlink for lid-linux, but that it
> > did not help. That suggests the sanity check at the end of pass 2
> > gcc did not give the right answer.
> >
>
> No, sanity check was ok everywhere. Gcc stop working only when I enter
> chroot environment. If I'm using 'lfs' user, everything works fine.
That still sounds as if it is using *something* from the host which
is no-longer available when you enter chroot.
I've long-ago forgotten most of what I learned about how to debug
things like this, so all I can suggest is that you run ldd on gcc as
user lfs and compare it to what you see in chroot.
Also, just to confirm it is a problem with gcc itself, not something
triggered by the kernel build infrastructure, please try to run
gcc --version
in chroot (I assume it will report the same error).
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
