Re: Results of test runs

[Leif Ekblad]

> Oh, yes, I guess you should incorporate your changes to config.guess and
> config.log into libtool's copy of those files.  Libtool imports those
> files just as GCC does.  (And no, I do not know how you named your
> toolchain; please fill in the correct values yourself).
> 
> For the next failure you are likely to encounter, please provide a bit
> more information: excerpts from config.log are usually helpful.

You are right. There are more failures, but they are in the make process.
libltdl/ltdl.c:1498: error: conflicting types for 'lt_argz_insertdir'.

However, I wonder why it would build libltdl at all, since I've
told GCC & libtool that RDOS doesn't support dynamic linking. I think
this is a good strategy right now, as I don't currently need dynamic
linking.
 
> You may be able to do better, though: we may be able to find out more
> about your system by running libtool's test suite on it, and thus
> improve libtool's RDOS support.

Yes, eventually, as I get more GNU tools ported. In it's current shape,
RDOS uses PE-executables and BC4.5 / TD32 as it's platform. That
means that RDOS isn't really unix-compatible. That's also why I use
newlib to start with instead of glibc. It uses FreeCom as a command
interpreter. All it can run right now from GNU is a hello-world
app compiled with the GCC/G++ toolchain.

My next goal is to incorporate GDB remote debugging features
and later port a native version of GDB. Being able to debug is
more important than porting utilities right now.
 
Leif Ekblad
www.rdos.net/rdos