Le 03/04/2013 08:03, Bruce Dubbs a écrit : > I'm pretty sure I tracked down this problem. In pmap.exp there is: > > spawn $pmap -X 1 > expect_pass $test "$pmap_initname\$" > > and spawn is doing some things with stty and the pmap program's newline > characters are being converted to \r\n. The expect command is doing a > regular expression match looking for a newline and \r\n does not match > that. To make that pass, we need to do: > > sed -i -r 's/(pmap_initname)\\\$/\1/' ./testsuite/pmap.test/pmap.exp > > Use -r here instead of -e to avoid some extra baskslashes. > > Another note is that the checks for procps-ng need almost all the > virtual file systems: /dev, /dev/pts, /proc, and /sys. The only one > that isn't needed here is /run/shm. > > I am running a build with this sed. I'll let you know.
BTW, I have also the "stty-pairs.sh" error in coreutils, when running in a virtual console. See gmane.linux.lfs.devel/13742 <http://article.gmane.org/gmane.linux.lfs.devel/13742> One way to fix is: sed -i '/stty-pairs/d' Makefile.in sed -i '/stty-pairs/d' tests/local.mk A more complicated way would be to adapt the code from stty.sh to stty-pairs.sh. I do not think we would gain much... Pierre -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
