Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!zephyr!tektronix!sequent!mntgfx!dclemans
From: dclemans@mntgfx.mentor.com (Dave Clemans @ APD x1292)
Newsgroups: comp.sys.apollo
Subject: Re: Please mail and post specific changes for GCC on Apollo
Summary: supplying requested information
Message-ID: <1989Jun2.094539.2408@mntgfx.mentor.com>
Date: 2 Jun 89 16:45:38 GMT
References: <1318@novavax.UUCP>
Organization: Mentor Graphics Corporation, Beaverton Oregon
Lines: 61

In article <1318@novavax.UUCP>, weiner@novavax.UUCP (Bob Weiner) writes:
> Request to Dave Clemans who recently posted modifications to GCC and G++
> to enable them to work on Apollo 680x0 systems.
> 
> Dear Dave,
> 
> Recently you posted your change files for getting GCC and G++ on Apollo
> SR10.1 BSD systems.  I'm sure everyone thanks you very much for the
> contribution.  I was trying to build the system and ran into some problems
> that you point out in the README file.
> 
>     Compile gcc/gas using the Apollo C compiler (setting the appropriate
>     flags in the makefile; see existing comments in the GCC makefile).  You
>     may also have to play around with includes of <sys/file.h>, and some
>     strange function pointer references in gcc/stmt.c; but all changes should
>     be relatively obvious.  None of the changes (except for the <sys/file.h>
>     ones) has to be permanent once you have a gcc/gas binary.
> 
> Since we are under the same environment, I thought you could send out a diff
> file or at least make explicit what changes are necessary since they don't
> seem obvious to me.  stmt.c is too large for anything to be obvious to
> someone who is not looking to spend a day or two in the code.
> 
> What needs to be done with includes of <sys/file.h>?
> 
> Exactly, which pointer references should be changed and how in stmt.c?
> 
> 	       Thanks very much,
> 
> 	       Bob
> 

I don't have that information explicitly saved (it's been quite a while
since I have had to use Apollo's compilers on gnu stuff), but in general

    for #include <sys/file.h>

        first try ifdef'ing it out; i.e.
        #ifndef apollo
        #include <sys/file.h>
        #endif

        if that doesn't work, include <unistd.h> instead; i.e.
        #ifndef apollo
        #include <sys/file.h>
        #else
        #include <unistd.h>
        #endif

    for stmt.c, first try to compile it as is (the problem areas may have
    been changed in current versions).  If everything works you can ignore
    this; else you will get errors messages something like
    "trying to call a non-function" (or something similar).  If you look
    at the referenced lines, and how the names on those lines are declared,
    you will that the names causing the errors are functions pointers
    that haven't been de-referenced.  Add de-references to all attempts to
    call through those function pointers (i.e. change "name" to "(*name)")
    and stmt.c should compile.

Sorry,
dgc