ncurses5.6 make error

Michael Spitler spitlermike at
Wed Jul 2 02:20:35 PDT 2008

> On Tue, Jul 1, 2008 at 12:28 AM, Michael Spitler <spitlermike at> wrote:
>> Hello, I am working with LFS Version SVN-20080604.
>> Only deviation is that I chose to use kernel instead.
>> I am using Ubuntu 8.04 as my host system.
>> Everything seems to have worked fine until I reached Ch. 5.13.
>> When I run make on ncurses, it gives this error:
>> make[1]: Entering directory `/mnt/lfs/source/ncurses-5.6/c++'
>> cd ../obj_s;   -I../c++ -I../include -I. -DHAVE_CONFIG_H -I.
>> -I../include  -D_GNU_SOURCE -DNDEBUG -I/tools/include
>> -fPIC -c ../c++/
>> /bin/sh: -I../c++: not found
>> make[1]: *** [../obj_s/cursesf.o] Error 127
>> make[1]: Leaving directory `/mnt/lfs/source/ncurses-5.6/c++'
>> make: *** [all] Error 2
> It seems like configure for ncurses failed to find a c++ compiler. Did
> you get any errors when you ran configure? It should be finding
> /tools/bin/g++. Maybe the GCC-pass2 build was borked.
> --
> Dan

Ok, I wound up starting over again, and noticed the following error when
running 'make check' after installing dejaGNU, right before
I am supposed to run the second pass of gcc:

../../depcomp: line 402: exec: g++: not found
make[4]: *** [unit.o] Error 127
make[4]: Leaving directory `/mnt/lfs/sources/dejagnu-1.4.4/testsuite/libdejagnu'
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory `/mnt/lfs/sources/dejagnu-1.4.4/testsuite'
make[2]: *** [check-DEJAGNU] Error 2
make[2]: Leaving directory `/mnt/lfs/sources/dejagnu-1.4.4'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/mnt/lfs/sources/dejagnu-1.4.4'
make: *** [check-recursive] Error 1

I ignored the error the last time I tried, because everything seemed fine till
then, and also because when I installed gcc(first pass) I specified
to only use c in the ./configure step as per the instructions. This led me
to believe that this would be fixed in the second pass when gcc is built with
the c and c++ options.

What baffles me most is that I was able to run the sanity check while adjusting
the toolchain just fine, so the compiler should be there...

More information about the lfs-support mailing list