This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: C++ porting : No such file or directory
Sivaprasad.pv wrote:
Now I have configured gcc-3.3 as below:
gcc-3.3/configure --prefix=$RELDIR --target=$TARGET
--enable-languages=c++ --with-gnu-as --with-gnu-ld --with-newlib
--host=i686-pc-linux-gnu --with-dwarf2 --enable-sjlj-exceptions
I have copied the newlib headers into $target/sys-include now build is
proceed further.
But in the same scenario I got stuck up with below mentioned error,
so can u please help me in this regard.
gnu/gcc-3.3/libstdc++-v3/libsupc++/eh_personality.cc: In
function `_Unwind_Reason_Code __gxx_personality_sj0(int, int,
<anonymous>,
_Unwind_Exception*, _Unwind_Context*)':
/gnu/gcc-3.3/libstdc++-v3/libsupc++/eh_personality.cc:455: internal
compiler error: Segmentation
Some "stupid questions" resulting from your earlier messages :
- Is libstdc++-v3 REALLY ported for your "secret" CPU (You never told
what that is!) ? There is
that 'config/cpu' with its different 'atomicity.h's for different
CPUs etc. "target dependencies" in the
libstdc++-v3 sources. "Who else would raise the tail of the cat if
not the cat...", so be prepared to
the fact that not only the 'gcc' subdirectory will have
target/CPU-dependencies :( A common CPU
like MIPS means "already ported", a "totally local" CPU means "we
will port" ! The 'sankhyagcc' in
your messages hinted about some "own CPU"....
- Didn't you yet have any prebuilt/tested C library when you had a
"working" C compiler earlier, or
what was the reason to NOT use the obvious target headers? The
"copied the newlib headers"...