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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,430e73ffe1dca4e9 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder.news-service.com!188.40.43.213.MISMATCH!feeder.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: How to exit a loop with keyboard input Date: Thu, 15 Apr 2010 20:22:58 +0100 Organization: A noiseless patient Spider Message-ID: References: <176f2831-ce2a-4bb1-9e04-47f662fc7176@q23g2000yqd.googlegroups.com> <20100412181434.dd154269.tero.koskinen@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Thu, 15 Apr 2010 19:23:00 +0000 (UTC) Injection-Info: feeder.eternal-september.org; posting-host="KCXegvZb5vh43D+f3BR6Ew"; logging-data="28930"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19xQVRvlQ4aasnrvienF/nkExTsLrPn6yk=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (darwin) Cancel-Lock: sha1:Actibte3lCC+REvIGhjunBMJqNQ= sha1:xDulzwOE+/iis+lOZVlF98GjZv8= Xref: g2news2.google.com comp.lang.ada:10970 Date: 2010-04-15T20:22:58+01:00 List-Id: Jerry writes: > Unfortunately, with the new set-up, building PLplot (to which I wrote > Ada bindings) now results in the linker complaining of some dylibs, > "file is not of required architecture." The SourceForge Leopard GNAT GPL 2009 compiler is 32-bit, while AdaCore's is 64-bit. I had a Leopard issue, where libtk was a thin library supporting only 32-bit, so I got the sort of problem you report when using AdaCore's compiler. Are you getting the problem with both compilers? if so, I'd expect each compiler to report the problem with different libraries. And your only recourse will be to rebuild the offending libraries with the appropriate compiler. What I've done is to use the matching GNAT compiler; eg for 64-bit, $ PATH=/opt/gnat-gpl-2009-x86_64/bin:$PATH $ ./configure .... $ make Given that most people don't build GNAT with c++, this is only going to work if the library concerned is C-based. You can find what architectures a library supports using lipo (-info or -detailed_info): in my /opt/gnu/lib I have some of the libraries used for compiler builds, so I get $ lipo -info *.a Architectures in the fat file: libgmp.a are: i386 x86_64 input file libhistory.a is not a fat file input file libltdl.a is not a fat file Architectures in the fat file: libmpc.a are: i386 x86_64 Architectures in the fat file: libmpfr.a are: i386 x86_64 input file libreadline.a is not a fat file Non-fat file: libhistory.a is architecture: i386 Non-fat file: libltdl.a is architecture: i386 Non-fat file: libreadline.a is architecture: i386