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 executables, the xgcc cross-compiler is named xgcc.exe, even though it is a Linux executable. This problem is fixed by copying this file to xgcc (no extension), and re-starting the make process. I don't know if this is a bug in some scripts, or it is some misconfiguration on my part. The system should know that Linux executables never have an .exe extension. After this build is complete, there is a gcclib.a file in the rdos-host directory. When I install it, however, the gcclib.a file isn't copied to /usr/local/rdos/lib, like the other libraries from the build without --host=rdos, but in another directory. I fixed this by copying the file to the correct location. I then linked a fairly large C++ executable that works in BC 4.52 format, and it works as an ELF-executable. However, I wonder why I had to explicitly include crt0.o, libc.a and some other files that ld finds automatically for C-executables. Maybe I shouldn't use g++ as a compiler but gcc? > 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. It works, but I haven't tested the exception-handling code yet. Leif Ekblad
