From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cb8bead09b00bb4b
X-Google-Attributes: gid103376,public
From: "David Taylor" <dtaylor@advicom.net>
Subject: Re: Help: gnat messing with gcc?
Date: 1997/07/27
Message-ID: <dtaylor-2707970959430001@dyn-d99.advicom.net>#1/1
X-Deja-AN: 259427532
Distribution: world
References: <5r70h2$14ks$1@cdserv.rzg.mpg.de>
Organization: at home
Newsgroups: comp.lang.ada
Date: 1997-07-27T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <5r70h2$14ks$1@cdserv.rzg.mpg.de>, witt@mppmu.mpg.de (Myriam Witt)
wrote:

>Hello.....
>
>please help me with the following question:
>
>I had gcc compiled and installed into a non-standard directory.
>After that I installed the gnat-309 binary distribution (for
>Solaris), choosing option 3 in a different (non-standard)

Sounds like a similar problem I had with SGI. Apparently, the gcc you got with
GNAT has some hardcoded pathnames in it and at some point things get derailed
onto the other gcc stuff. I've already told you more than I understand. 

Read carefully a README that in the directory created from unzipping and
untarring. We decided that we couldn't use GNAT installed with option 3 if there
is already a GNAT (hence a gcc) installed in "the usual place".

dave taylor