Re: [lfs-support] PS1 for user lfs
On Fri, 20 Apr 2012 21:38:37 +0100
Philippe Delavalade philippe.delaval...@orange.fr wrote:
Hi.
I'm building svn-9812 ; my host is debian/wheezy ; I encounter for the
first time a little problem in 4.4.
When becoming user lfs and after having passed the command
source .bash_profile
I don't obtain the right prompt ; all variables are correct except PS1
which is
PS1=${debian_chroot:+($debian_chroot)}\u@\h:\w\$
Maybe it's not important (and I think so) but nevertheless, I fear that
this uncorrect value can hide other problems...
I've noticed the same issue when using Ubunut as a host, when I su to
the user lfs I didn't get the bare bash prompt. Like you I worried that
it might hide other environment variables that were being preserved
from the host. Unlike you I've never taken the time to investigate it,
I just cracked on and it all turned out fine so I didn't look back. I
suspect that they compile a default PS1 into bash but it's just a
suspicion.
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] PS1 for user lfs
Andrew Benton wrote:
On Fri, 20 Apr 2012 21:38:37 +0100
Philippe Delavalade philippe.delaval...@orange.fr wrote:
Hi.
I'm building svn-9812 ; my host is debian/wheezy ; I encounter for the
first time a little problem in 4.4.
When becoming user lfs and after having passed the command
source .bash_profile
I don't obtain the right prompt ; all variables are correct except PS1
which is
PS1=${debian_chroot:+($debian_chroot)}\u@\h:\w\$
Maybe it's not important (and I think so) but nevertheless, I fear that
this uncorrect value can hide other problems...
I've noticed the same issue when using Ubunut as a host, when I su to
the user lfs I didn't get the bare bash prompt. Like you I worried that
it might hide other environment variables that were being preserved
from the host. Unlike you I've never taken the time to investigate it,
I just cracked on and it all turned out fine so I didn't look back. I
suspect that they compile a default PS1 into bash but it's just a
suspicion.
On Debian based systems, PS1 is set to use debian_chroot in /etc/bash.bashrc.
When we run
exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
bash is rerun as an interactive shell and executes both /etc/bash.bashrc and
~/.bashrc.
I'm not sure we need to worry about this, but I can't quite figure out how to
only run ~/.bashrc.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] error in udev in chapter 6.60
while issuing the make command in udev chpater 6.60 for lfs 7.1 the following error results.please provide help root:/sources/udev-181# make GEN test/sys/kernel/uevent_seqnum make --no-print-directory all-recursive Making all in . CC src/libudev.lo CC src/libudev-list.lo CC src/libudev-util.lo CC src/libudev-device.lo CC src/libudev-enumerate.lo CC src/libudev-monitor.lo src/libudev-monitor.c: In function 'udev_monitor_receive_device': src/libudev-monitor.c:654:44: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] CC src/libudev-queue.lo CCLD src/libudev.la CC src/libudev-util-private.lo CC src/libudev-device-private.lo CC src/libudev-queue-private.lo CCLD src/libudev-private.la CC src/src_udevadm-udev-event.o CC src/src_udevadm-udev-watch.o CC src/src_udevadm-udev-node.o CC src/src_udevadm-udev-rules.o CC src/src_udevadm-udev-ctrl.o CC src/src_udevadm-udev-builtin.o CC src/src_udevadm-udev-builtin-blkid.o CC src/src_udevadm-udev-builtin-firmware.o CC src/src_udevadm-udev-builtin-hwdb.o CC src/src_udevadm-udev-builtin-input_id.o CC src/src_udevadm-udev-builtin-kmod.o src/udev-builtin-kmod.c:30:21: fatal error: libkmod.h: No such file or directory compilation terminated. make[2]: *** [src/src_udevadm-udev-builtin-kmod.o] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Thank you -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error in udev in chapter 6.60
ankit vishwakarma wrote: while issuing the make command in udev chpater 6.60 for lfs 7.1 the following error results.please provide help CC src/src_udevadm-udev-builtin-kmod.o src/udev-builtin-kmod.c:30:21: fatal error: libkmod.h: No such file or directory compilation terminated. Did you install kmod? Do you have /lib/libkmod.so? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error in udev in chapter 6.60
ankit vishwakarma wrote: i have installed kmod but there is no file named /lib/libkmod.so so do i have to install kmod again Please don't top post. If /lib/libkmod.so does not exist then kmod wasn't installed. You may have built it, but overlooked the make install line. Yes, install kmod again. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error in vim inn chapter 6.61
ankit vishwakarma wrote: cp test51.ok test.ok ../vim -u unix.vim -U NONE --noplugin -s dotest.in test51.in 3,6c3 NewGroup xxx term=bold cterm=italic ctermfg=2 ctermbg=3 --- NewGroup xxx term=bold cterm=italic ctermfg=2 ctermbg=3 10,11c7 Group3 xxx term=underline cterm=bold --- Group3 xxx term=underline cterm=bold test51 FAILED TEST FAILURE Those lines look like they only differ in newlines. Do you have LANG or one of the LC_ environment variables set? Also, what terminal type are you using? (echo $TERM) I haven't seen that type of error before, but I wouldn't worry about it. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error in vim inn chapter 6.61
On Sun, Apr 22, 2012 at 06:27:48AM +0530, ankit vishwakarma wrote: the following error occur while executing make test. please provide help. Press ENTER or type command to continue No idea if that is odd - I route the output from the tests to a file. Seems unusual, maybe someone else who actually runs the tests without dumping the results to a file would like to comment ? But either way, not something to worry about. # Sleep a moment to avoid that the xterm title is messed up ../vim -u unix.vim -U NONE --noplugin -s dotest.in test51.in 3,6c3 NewGroup xxx term=bold cterm=italic ctermfg=2 ctermbg=3 --- NewGroup xxx term=bold cterm=italic ctermfg=2 ctermbg=3 10,11c7 Group3 xxx term=underline cterm=bold --- Group3 xxx term=underline cterm=bold This is probably the failure - the results have different formatting from the expected results. [...] Test results: test51 FAILED TEST FAILURE For years, I saw one or more failures in the vim tests, when I could be bothered to run them, but oddly enough for LFS-7.0 and LFS-7.1 it has always managed to pass the tests on those builds where I run them (x86_64, using the previous release of LFS). But does it matter ? Perhaps (in an infinite universe, *anything* *might* make a difference), but unlikely. The book got very worked up about running tests in LFS-6.0 or whenever 'pure LFS' was introduced (understandably, after the different / unrepeatable results some people saw in earlier versions), but the reality is that test suites are rarely decisive and mostly concerned with testing 'corner cases'. My own experience is that from time to time I see more failures in toolchain tests, then at other times the failures no longer happen. The only real way to make sense of that is to build LFS-svn frequently, run the tests each time, and then try to work out what changed (e.g. the host kernel). Mostly, that is NOT worth the effort [ those who differ are welcome to spend their time doing this, I prefer to find out if the resulting LFS system can build a system which I find useful ] If you get one failure in a non-toolchain package, it's very unlikely to make a difference. If you get more than 10 failures in a *toolchain* package, it *might* indicate a problem. If you get 100 or more failures in the same package, you have a problem. For intermediate numbers of failures, your guess is as good as mine ;-) So, asking about failures is fine, but expecting 100% lack of test failures is unrealistic. Yes, I know Bruce's posted results often show perfection - I just wish I had his machines or his environment. I often see a few test failures - some are obviously because of what I do differently (no static libs), others seem to occur for no obvious reason. Summary: don't panic, and don't expect perfection (this is software, no software is bug-free and that includes the testsuites) - particularly if you are running in a virtual machine, or using an older kernel, or a kernel with a lot of distro patches. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] error in vim inn chapter 6.61
the terminal type is xterm. root:/sources/vim73# echo $TERM xterm and the information concerning LANG and LC_environment variables is as follows root:/sources/vim73# locale LANG= LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= root:/sources/vim73# so do i need not worry and continue with the build or what should i do please provide help. Thank You -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
