Re: Problems Building GCC 2.95.2 on Concurrent Maxion (mips)

["Cal Webster" <cwebster at ec dot rr dot com>]

Thank you for the tips Jim. I'm preparing for a trip next week to CA where
there is yet another flight simulator using old Concurrent systems. I'll put
some more work into it in the next few weeks. "When" I get something working
I'll post it in case there's some other hapless fool in my circumstances.

----- Original Message -----
From: "Jim Wilson" <wilson@cygnus.com>
To: "Cal Webster" <cwebster@ec.rr.com>
Cc: <gcc@gcc.gnu.org>
Sent: Thursday, August 24, 2000 3:02 PM
Subject: Re: Problems Building GCC 2.95.2 on Concurrent Maxion (mips)


> I am not familiar with Concurrent Maxion systems.  Since gcc is very
system
> dependent, it is unlikely to work if it doesn't already support your
system.
>
> Using "mips" as the target will certainly not work.  There are many
different
> kinds of mips based systems available, and they are not interchangeable.
> "mips" by itself will default to something inappropriate for your target.
> Figuring out which target, if any, is the right one will be hard.  Try
looking
> at the list of mips-*-* targets gcc/configure.in.  mips-sni-sysv4 would be
my
> first suggestion, but you might also try mips-tandem-sysv4.  If neither of
> these work, then there is probably no choice that will work.
>
> Most old systems require ranlib to process archive files.  Some new
systems
> don't.  If you system doesn't have ranlib, then it isn't required.  Gcc
should
> figure this out on its own, but if it doesn't you can just alias ranlib to
> "touch" or "true" or some other harmless command that always succeeds.
>
> Binutils is just as system dependent as gcc.  If binutils doesn't already
> know about your system (and it doesn't), then it is unlikely to work.
>
> As with gcc, telling binutils that your target is "mips" won't work.
There
> are too many different incompatible mips systems out there for this to
work.
> Try one of the two targets I mentioned above for gcc, but again, it is
> possible that there is no choice that will work.
>
> Binutils is apparently defaulting to a 64-bit target when you specify
"mips".
> If you are on a 32-bit system, then this can work only if the host
compiler
> supports a 64-bit type like gcc's long long.  In practice, this probably
means
> that you can't build it unless you have gcc.  However, since it is
configured
> wrong, it doesn't really matter that you can't build it.
>
> In general, the GNU tools do not support mips SVR4 systems very well.
> GNU tools mostly support the machines that GNU developers have access to,
> and, historically, we haven't had access to these kinds of systems.
> You should be able to get the things other than gcc/gdb/binutils working
> though, as the rest of the stuff is not so system dependent.  Your GNU
make
> is probably OK.
>
> -lmld is a library on some older mips systems.  Gcc is trying to link
> against it because you configured gcc wrong.
>
> Jim