For me the result is for awk --version | head -n1 is: GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.2-p11, GNU MP 6.0.0) So it looks like I did replace mawk with gawk on the Kubuntu host. However I did notice mawk is still present on the system,
So I did some more digging I came to conclusion it was mawk after all. It seems that ncurses prefers to use mawk even when awk points to gawk and even when there is an awk or gawk earlier in $PATH. The only way to get ncurses to build without the patch was to ensure there is no mawk in $PATH what so ever. However on my fresh LFS build, I did try an ncurses build with mawk in $PATH. That was no problem was so ever without the patch. Heck it even compiled with only mawk present an no gawk. That leaves me puzzling why ncurses is giving issues on a Kubuntu host when mawk is present next to gawk. Might be there is some 'feature' in the mawk Kubuntu. On my fresh LFS dev build with gawk next to mawk or pure mawk seems to make ncurses build regardless. I even retried this with the temp toolchain within the chroot. The mawk used is the latest from the mawk website. After all this I came to the conlusion that is is a host system problem. It seems to be having mawk present in $PATH on a *ubuntu 15.04 host is giving issues. If mawk is not present in $PATH on *ubuntu 15.04 ncurses will compile happily.
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
