This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Porting GCC to RDOS and C++ issues
On Dec 29, 2005, at 1:01 PM, Leif Ekblad wrote:
OK, I found unwind-dw2.c in the GCC directory. I also found
the object files in the linux host directory, but not in the RDOS
cross
compilation directory. I cannot run the GCC configuration process
natively on RDOS (yet), so I must somehow build libgcc with the
cross-compiler. Any idea (FAQs) on how to do this?
make will build libgcc for the target, specifically, you should be
able to cd gcc && make libgcc.a to build it.
If your port doesn't use dwarf for EH, then it won't build that file,
but then again, there will be (should be) no unresolved references to
_Unwind_Resume if that were the case.
In you makefile, do you have something like:
# Additional sources to handle exceptions; overridden by targets as
needed.
LIB2ADDEH = $(srcdir)/unwind-dw2.c $(srcdir)/unwind-dw2-fde.c \
$(srcdir)/unwind-sjlj.c $(srcdir)/gthr-gnat.c $(srcdir)/unwind-c.c
LIB2ADDEHSTATIC = $(LIB2ADDEH)
LIB2ADDEHSHARED = $(LIB2ADDEH)
LIB2ADDEHDEP = $(UNWIND_H) unwind-pe.h unwind.inc unwind-dw2-fde.h
unwind-dw2.h
# Don't build libunwind by default.
LIBUNWIND =
LIBUNWINDDEP =
SHLIBUNWIND_LINK =
SHLIBUNWIND_INSTALL =
? Anyway, compare and contrast with linux. Build a linux cross, if
you want an easier to compare layout.