Xref: utzoo comp.unix.misc:1031 gnu.gcc.help:479
Path: utzoo!utgpu!watserv1!watmath!uunet!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!infopiz!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.unix.misc,gnu.gcc.help
Subject: Re: Porting GCC to a Callan Unistar 300... possible?
Message-ID: <4213@lupine.NCD.COM>
Date: 3 Mar 91 01:11:29 GMT
References: <1991Mar1.072541.6959@agate.berkeley.edu>
Followup-To: comp.unix.misc
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 65

In article <1991Mar1.072541.6959@agate.berkeley.edu> dburr@.berkeley.edu (Donald Burr) writes:
>
>I would like to get GCC running on my Callan Unistar 300 box.  This is a
>SysV R2 (I think) box that uses a MC68010 as the processor.  Is this
>possible, and if so, what/how much hacking would I need to do in the GCC
>code, and where?

If you already have a C compiler on your Callan, and if it is not too
brain dammaged, you should be able to get GCC up pretty easily.

You will probably want to make up your own xm-callan.h and tm-callan.h
files in order to do this.  Fortunately, you will not have to start
from scratch.  Look at the tm-sun2.h file.  It is correct for a 68010
processor so you should be able to make up a tm-callan.h file by just
doing:

	tm-callan.h:
	----------------------------------------------------------------
	#include "tm-sun2.h"

	/* ... overriding definitions go in here ... */

	----------------------------------------------------------------

You may have to override a few of the definitions that get included
from the tm-sun2.h file, but it should not be too many.

One thing that I *know* you will have to override is the following:

	#undef DBX_DEBUGGING_INFO
	#define SDB_DEBUGGING_INFO

That's because your target system (i.e. Callan) uses System V.

For your xm-callan.h file you probably want to start from one of the
xm-*.h files that are used for System V hosts.  Any one of the xm-*.h files
that define the symbol `USG' will probably be a good starting point for
your new xm-callan.h file.  If you just do:

	cd config
	grep USG xm-*.h

You will see which of the existing xm-*.h files are already used with
System V based systems.  (Fortuanately, they are all almost identical
and they are all pretty short, so if you look at the contents of a few
of these files it should be obvious what your xm-callan.h file should
look like.

Once you get these two configuration files set up properly, you will need
to complete the "configuration" step by doing:

	ln config/xm-callan.h config.h
	ln config/tm-callan.h tm.h
	ln config/m68k.md md
	ln config/out-m68k.c aux-output.c

Then just type `make' and keep your fingers crossed.

Summary:  You should have to `hack' very little (if at all).

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// New motto:  If it ain't broke, try using a bigger hammer.