From owner-freebsd-ports  Sun Sep 28 16:03:48 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA28952
          for ports-outgoing; Sun, 28 Sep 1997 16:03:48 -0700 (PDT)
Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA28918;
          Sun, 28 Sep 1997 16:03:24 -0700 (PDT)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id RAA19154; Sun, 28 Sep 1997 17:29:39 -0500 (CDT)
Message-Id: <199709282229.RAA19154@iworks.InterWorks.org>
Date: Sun, 28 Sep 1997 17:29:39 -0500 (CDT)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: asami@cs.berkeley.edu, owner-freebsd-ports@FreeBSD.ORG
Subject: Re: gnat port
Cc: ada@bsd.org, helbig@Informatik.BA-Stuttgart.DE, ports@FreeBSD.ORG
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > Actually there has been a port submission (PR 3687).  I have exchanged
>
> Ooops, I guess I should have queried the PRs *before* starting
> this Don Quichoteese fight with gcc and friends--devoting every
> spare second to it. :-( Didn't even take the time to read the mail
> last couple of days, so it's only today that I learned about this
> PR and gnat-3.09.
>
> > commit now.  It uses a separate tarball (gcc-2.7.2.1.tar.gz), so go
> > ahead and fix it to use /usr/src/contrib/gcc.
>
> I'll try, but it's not trivial. Anyway I think it's worth it.

If this is in regard to fixing the gnat port to use FreeBSDs
gcc, please do not do that.  I changed the gnat port so that
it *doesn't* depend on /usr/src/contrib/gcc (which can be a
moving target, and changes to it will make the gnat port fail).

I diff'd the FreeBSD gcc source tree with the stock 2.7.2.1
source tree, and used that as a patch file to apply to the
stock gcc-2.7.2.1.  Now the gnat port should work regardless
of what happens to /usr/src/contrib/gcc.

Another reason for basing the gnat port on the stock gcc
distribution is that FreeBSDs gcc will always lag behind
the latest and greatest GNU gcc.  When ACT (Ada Core Technologies) 
starts using newer gccs, we can easily stay current with
GNAT by using the stock gcc distributions.  The GNAT port
has, in the past, been left behind because it was based on the
stock gcc distribution - GNAT-2.0.3 was based on gcc-2.6.3
and was never maintained when GNAT went to gcc-2.7.2.

Dan Eischen
deischen@iworks.InterWorks.org