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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1f0fee9a90c6f8dd X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!h76g2000cwa.googlegroups.com!not-for-mail From: "Anh Vo" Newsgroups: comp.lang.ada Subject: Re: Problem with GNAT GPL 2006 win32ada bindings Date: 20 Jun 2006 10:06:27 -0700 Organization: http://groups.google.com Message-ID: <1150823186.967604.40390@h76g2000cwa.googlegroups.com> References: <449524dd$0$10456$afc38c87@news.optusnet.com.au> <1150665750.905137.327060@f6g2000cwb.googlegroups.com> <4496601a$0$22360$afc38c87@news.optusnet.com.au> <44967fb0$0$27620$afc38c87@news.optusnet.com.au> <1150729644.528499.141900@i40g2000cwc.googlegroups.com> NNTP-Posting-Host: 209.225.224.97 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1150823192 5204 127.0.0.1 (20 Jun 2006 17:06:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 20 Jun 2006 17:06:32 +0000 (UTC) In-Reply-To: <1150729644.528499.141900@i40g2000cwc.googlegroups.com> User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: h76g2000cwa.googlegroups.com; posting-host=209.225.224.97; posting-account=JVr7Xg0AAAAI3MbuARxMmvWLmA7qdJMx Xref: g2news2.google.com comp.lang.ada:4858 Date: 2006-06-20T10:06:27-07:00 List-Id: Anh Vo wrote: > Ross Higson wrote: > > Ross Higson wrote: > > > Anh Vo wrote: > > >> It happened to me, too. I plan to send a bug report tomorrow. > > > > > An update - I also contacted Adacore and just got a reply indicating > > that the problems I had with the GNAT GPL 2006 win32ada bindings is due > > to a packaging glitch which will be corrected soon . > > Thanks for your info. It saves me from sending a bug report. The fix is in. It works fine now.