[EMAIL PROTECTED] (Leif Ekblad) wrote on 30.12.05 in <[EMAIL PROTECTED]>:
> Mike Stump:
> > make will build libgcc for the target, specifically, you should be
> > able to cd gcc && make libgcc.a to build it.
>
> It did when I added --host=rdos to the configuration script and
> changed a couple of
Mike Stump:
> make will build libgcc for the target, specifically, you should be
> able to cd gcc && make libgcc.a to build it.
It did when I added --host=rdos to the configuration script and
changed a couple of other files. My only current problem is that
since RDOS uses the .exe suffix for exe
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
Where are these functions implemented
Mike Stump:
grep will show you the code that should be used to build it. unwind-
dw2.c is the usual place.
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 di
On Dec 29, 2005, at 11:45 AM, Leif Ekblad wrote:
However, now I still get unresolved externals related to C++
exception-handling (_Unwind_resume
and so on).
mrs $ nm libgcc_s.1.dylib | grep Unwind_Re
8c24 T __Unwind_Resume
mrs $ nm libgcc/unwind-dw2.o | grep Unwind_Res
24c0 T __Unwind
I've successfully ported GCC and Newlib to RDOS. It seems to work with a
"hello world" app.
However, my main focus is not C, but C++.
I found out that libstdc++ didn't compile without modifying it's
configuration files to support RDOS.
Where do I send patches for libstdc++? To this list?
Howe
