Ken,
Thanks for the feed back.
I am running from the command line, but I'm not working on my Kernel right now. I'm trying to get this application built to run on linux over Nios.
What I meant by "-S" was my compiler flag.
nios2-elf-gcc -S foo.c, instead of nios2-elf-gcc -c foo.c
The compiler was passing the assembly file to the HOST assembler. By using "-S," I was able to generate the assembly file "foo.s," then call nios2-elf-as direclty and generate the object file.
I'm now over this hurdle. I updated GCC_EXEC_PREFIX with the correct path to cc1, and cc1plus. I was also calling nios2-elf-gcc, when I needed to be calling nios2-elf-g++. A cut, copy, and paste error!!!
The assembler is happy now that I'm calling the correct one. And for about 2 minutes, so was I. The flavor of the afternoon is with basic_string.h being called out of the ....../c++/3.4.1/bits/ directory.
I'm getting errors like '_Atomic_word' does not name a type, and
'__exchange_and_add' is not a member of '__gnu_cxx'
Doug