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.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:ac8:1198:: with SMTP id
 d24-v6mr6096651qtj.14.1530209980721;
        Thu, 28 Jun 2018 11:19:40 -0700 (PDT)
X-Received: by 2002:a37:21a4:: with SMTP id f36-v6mr685935qki.7.1530209980617;
 Thu, 28 Jun 2018 11:19:40 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!h2-v6no1500213qtp.0!news-out.google.com!u13-v6ni532qtg.0!nntp.google.com!h2-v6no1500206qtp.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 28 Jun 2018 11:19:40 -0700 (PDT)
In-Reply-To: <ph2fs9$70q$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=47.185.195.62;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 47.185.195.62
References: <64c649e6-fe13-4a1b-8584-cd9e727151a2@googlegroups.com>
 <ph2fs9$70q$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <db00e2a5-814d-4ace-8611-889b6cd03945@googlegroups.com>
Subject: Re: Rebuilding GNAT for mingw (32bit)
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Thu, 28 Jun 2018 18:19:40 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:53410
Date: 2018-06-28T11:19:40-07:00
List-Id: <comp.lang.ada>

On Thursday, June 28, 2018 at 6:13:14 AM UTC-5, Brian Drummond wrote:
> On Thu, 28 Jun 2018 04:01:18 -0700, Jere wrote:
>=20
> > So I recently ran into an issue using the FSF GNAT on 32bit mingw.
> > It ended up having a bug in GNAT.Serial_Communications, which was fixed
> > in later versions of GNAT found in 64 bit mingw.  Unfortunately I can't
> > upgrade to the 64bit version and get a later version of GNAT.
> > The bug fix was only a few lines, so I figured I could make the change
> > to g-sercom.adb in the adainclude directory and hopefully recompile
> > GNAT.  When I looked up instructions for this I found:
> >=20
> > https://gcc.gnu.org/onlinedocs/gnat_ugn/Rebuilding-the-GNAT-Run-Time-
> Library.html
> > Any help would be appreciated.
>=20
> In the event you can't find the correct answer, you can probably move=20
> forward by replacing g-sercom.ad[sb] with your own package derived from=
=20
> it, in your project and under your control.
>=20
> I'm sure someone will jump in with comments if there are license=20
> implications to this approach.

If g-sercom.ad[sb] were copied from FSF GNAT (64-bit mingw) to FSF GNAT (32=
-bit mingw), then same license.  No harm, no foul.

If g-sercom.ad[sb] were copied from GNAT GPL Community Edition to FSF GNAT =
(by anyone other than an official FSF maintainer as normative representativ=
e of FSF itself), then the GPLv3's Runtime Exception would disappear hencef=
orth in all of everything downstream from that now-full-fledged-GPLv3ed cop=
y of FSF GNAT.

[I am not a lawyer who has passed the bar in any jurisdiction.  These obser=
vations are merely for my novelty purposes only, not to be relied upon by y=
ou.]