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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a02:5696:: with SMTP id u22-v6mr3419730jad.5.1530222200346; Thu, 28 Jun 2018 14:43:20 -0700 (PDT) X-Received: by 2002:a9d:62d7:: with SMTP id z23-v6mr524206otk.6.1530222200211; Thu, 28 Jun 2018 14:43:20 -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!d7-v6no3097552itj.0!news-out.google.com!p13-v6ni3983itf.0!nntp.google.com!u78-v6no3065401itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 28 Jun 2018 14:43:19 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=96.247.198.106; posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf NNTP-Posting-Host: 96.247.198.106 References: <64c649e6-fe13-4a1b-8584-cd9e727151a2@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <2fa5cb92-7351-43a4-8329-2a33b48ac235@googlegroups.com> Subject: Re: Rebuilding GNAT for mingw (32bit) From: Jere Injection-Date: Thu, 28 Jun 2018 21:43:20 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:53414 Date: 2018-06-28T14:43:19-07:00 List-Id: On Thursday, June 28, 2018 at 2:19:41 PM UTC-4, Dan'l Miller wrote: > 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 fix= ed > > > 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 chang= e > > > 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. >=20 > 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. >=20 > If g-sercom.ad[sb] were copied from GNAT GPL Community Edition to FSF GNA= T (by anyone other than an official FSF maintainer as normative representat= ive of FSF itself), then the GPLv3's Runtime Exception would disappear henc= eforth in all of everything downstream from that now-full-fledged-GPLv3ed c= opy of FSF GNAT. >=20 > [I am not a lawyer who has passed the bar in any jurisdiction. These obs= ervations are merely for my novelty purposes only, not to be relied upon by= you.] All work was done using FSF versions utilizing the special exception.