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,4ca5b381d519c442,start X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!q17g2000vby.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: GNAT 2011 - some mixed feelings Date: Fri, 17 Jun 2011 04:18:03 -0700 (PDT) Organization: http://groups.google.com Message-ID: <2d872d5e-8d9d-4a34-a106-e192bfa93595@q17g2000vby.googlegroups.com> NNTP-Posting-Host: 83.3.40.82 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1308310368 15395 127.0.0.1 (17 Jun 2011 11:32:48 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 17 Jun 2011 11:32:48 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: q17g2000vby.googlegroups.com; posting-host=83.3.40.82; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Xref: g2news2.google.com comp.lang.ada:20890 Date: 2011-06-17T04:18:03-07:00 List-Id: So, after two days of trying, I was finally able to download the packages. :-) I'm pleased to note that the package for Mac OS X finally got the g++ compiler as part of the whole suite (as was always the case for other platforms). I regret to report, however, that this combination is probably broken. I have a project that works perfectly fine on Linux (GNAT GPL & FSF), FreeBSD (GNAT-AUX), and Windows (GPL), but on Mac the program hangs at the beginning without even reaching the first line of its main procedure. I'm a bit lost with how to diagnose it, but will surely report more when I find out what is wrong. (any help is highly welcome, I will provide the necessary details on demand) I have also noticed that gnatmake changed its behavior with regard to the following in library project files: for Library_Dir use "."; I use such lines to link with standard libraries written in "other languages". In previous versions, this allowed the linker to find such library on one of its standard search paths - now it tries to read the library file in the current directory, which fails and requires manual modification of such project file. I will agree that the current behavior is actually correct (after all, that's what dot means...), but then - how can I instruct the linker to really search on its standard paths? -- Maciej Sobczak * http://www.msobczak.com * http://www.inspirel.com