Topic: Checking 'working-g++'... failed.

[root@na trunk]# make menuconfig
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'working-gcc'... ok.
Checking 'working-g++'... failed.
Checking 'ncurses'... ok.
Checking 'zlib'... ok.
Checking 'gawk'... ok.
Checking 'bison'... ok.
Checking 'flex'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'patch'... ok.
Checking 'perl'... ok.
Checking 'wget'... ok.
Checking 'gnutar'... ok.
Checking 'autoconf'... ok.
Checking 'non-root'... ok.

Build dependency: Please install the GNU C++ Compiler (g++).
Prerequisite check failed. Use FORCE=1 to override.
make: *** [tmp/.prereq-build] Error 1
[root@na trunk]#

However my g++ is just fine from what you can see:

[root@na trunk]# g++ --version
g++ (GCC) 4.2.1
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[root@na trunk]#

Re: Checking 'working-g++'... failed.

Note that it is not testing to see if g++ exists, it checks to see if it works properly.  Here is the excerpt from kamikaze_7.07/include/prereq-build.mk

define Require/working-g++
    echo 'int main(int argc, char **argv) { return 0; }' | \
        g++ -x c++ -o $(TMP_DIR)/a.out -lstdc++ -
endef

$(eval $(call Require,working-g++, \
    Please install the GNU C++ Compiler (g++). \
))

If that code fragment does not run successfully then there is something wrong with your toolchain.  In case you have trouble making sense of it, here's a cleaner version:

echo 'int main(int argc, char **argv) { return 0; }' | \g++ -x c++ -o a.out -lstdc++ - && echo === Success === || echo === Failed ===

It will print "=== Success ===" if it worked, "=== Failed ===" (and probably some error output) if it did not.
If it fails then you will have to figure out why your host toolchain is not working properly.

Also, it looks like you are attempting to build as root, the build system tries to prevent this unless you have disabled it.  There is no reason to build as root.

Re: Checking 'working-g++'... failed.

Thanks for the info. I was using svn for /trunk

When I got svn for /kamikadze it all works. Go figure? I guess /trunk has something in the rules file that prevents it from executing the little a.out file while Kamikadze compiles and runs that file fine.

Oh well. Thank you. If I may repeat another question from previous post - how can one write simple c++ programs and compile them for the Broadcom platform? Are there any samples for "Hello World" programs and the Makefile to use?

Thanks
~B