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
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Brian Drummond <brian@shapes.demon.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: Rebuilding GNAT for mingw (32bit)
Date: Thu, 28 Jun 2018 11:13:13 -0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <ph2fs9$70q$1@dont-email.me>
References: <64c649e6-fe13-4a1b-8584-cd9e727151a2@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 28 Jun 2018 11:13:13 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="67163b3116af35df3177be5120107c56";
	logging-data="7194"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18jo8znjR39x8wNImkMRphv/SOfUxZsUhU="
User-Agent: Pan/0.141 (Tarzan's Death; 168b179 git.gnome.org/pan2)
Cancel-Lock: sha1:veIwy8SBsK/ZK27z8YAyVOoCJuU=
Xref: reader02.eternal-september.org comp.lang.ada:53400
Date: 2018-06-28T11:13:13+00:00
List-Id: <comp.lang.ada>

On Thu, 28 Jun 2018 04:01:18 -0700, Jere wrote:

> 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:
> 
> https://gcc.gnu.org/onlinedocs/gnat_ugn/Rebuilding-the-GNAT-Run-Time-
Library.html
> Any help would be appreciated.

In the event you can't find the correct answer, you can probably move 
forward by replacing g-sercom.ad[sb] with your own package derived from 
it, in your project and under your control.

I'm sure someone will jump in with comments if there are license 
implications to this approach.

-- Brian