On Tue, 2021-01-12 at 20:37 +0100, coolnodje wrote:
> GCC compilation went well after fixing PATH from .bashrc
>
>
> But oddly the problem when using `su - lfs` comes from .bash_profile,
> containing
> exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash as defined
> in the book.
>
> Using `su lfs` then cd home and `source .bash_profile` or executing
> manually `exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash`
> both works.
>
> Bash version is
> GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
>
> The error goes like this:
>
> root@LFSDebian:~# su - lfs
>
> [3]+ Stopped su - lfs
At this point, you can type "fg" and the <enter> key. It's incredible
that debian have this bug in a stable version!
But I could reproduce it...
Then type env. On my machine, I get:
PWD=/home/lfs
HOME=/home/lfs
TERM=xterm-256color
SHLVL=1
PS1=${debian_chroot:+($debian_chroot)}\u@\h:\w\$
LFS_TGT=x86_64-lfs-linux-gnu
LC_ALL=POSIX
LFS=/mnt/lfs
CONFIG_SITE=/mnt/lfs/usr/share/config.site
PATH=/mnt/lfs/tools/bin:/usr/bin
_=/usr/bin/env
If everything is ok, I suggest you start over at binutils-pass1 (delete
everything in /mnt/lfs/tools)
Pierre
--
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
