Can't see symbolic Links in chrooted environment

Thinus Pollard thinusp at olienhout.org.za
Sun Nov 19 14:22:22 PST 2000


speaking of kernel symlinks, has anyone noticed there is no
../linux/include/asm?

you should make the symlink point to:
    ../src/linux/asm-i386
on an x86 machine at least

T

----- Original Message -----
From: "Jesse Tie Ten Quee" <highos at highos.com>
To: <lfs-apps at linuxfromscratch.org>
Sent: Sunday, November 19, 2000 10:20 PM
Subject: Re: Can't see symbolic Links in chrooted environment


> Yo,
>
> On Sun, Nov 19, 2000 at 01:31:19PM -0700, Roger deBry wrote:
> > This is a follow on to my earlier note regarding not being able to
compile
> > ed or patch in the chrooted environment. When doing a make on either of
> > these, I get compiler messages that it cannot find header files in
/linux
> > and /asm, yet the directories and files are there (linux and asm are
> > symbolic links)! While playing around with these files, I found that I
could
> > cd to $LFS/usr/include/linux or to $LFS/usr/include/asm when in the
> > development environment. However, when I chroot to the $LFS system, I
cannot
> > cd to these directories -- even though they show up in a directory
listing.
> > I get the message directory or file does not exist. This has got me
> > completely baffled. Why don't the symbolic links work in the chrooted
> > environment?
>
> Make sure they are not absolute links.
>
> -
> Jesse Tie Ten Quee - highos at highos dot com
>
> --
> Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message


-- 
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the blfs-support mailing list