Can't see symbolic Links in chrooted environment

Gerard Beekmans gerard at
Mon Nov 20 07:22:23 PST 2000

On November 19, 2000 03:31 pm, you 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?

What does "ls -l /usr/include/linux" give you?

Gerard Beekmans

-*- If Linux doesn't have the solution, you have the wrong problem -*-

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

More information about the blfs-support mailing list