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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,27e56580ae0c3b7d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-24 23:39:38 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!newsfeed.mathworks.com!nycmny1-snh1.gtei.net!washdc3-snh1.gtei.net!news.gtei.net!ngpeer.news.aol.com!newsfeed1!bredband!uio.no!ntnu.no!not-for-mail From: Preben Randhol Newsgroups: comp.lang.ada Subject: Re: GNAT for Debian Date: Fri, 25 Jul 2003 06:39:38 +0000 (UTC) Organization: Norwegian university of science and technology Message-ID: References: <404ee0af.0307211056.15324da@posting.google.com> <20030722021229.15da08ae.david@realityrift.com> <20030722135518.32888aaa.david@realityrift.com> <20030722165245.15f880a2.david@realityrift.com> <20030723125549.1336a07f.david@realityrift.com> <20030723134949.7badd43c.david@realityrift.com> <3f1f9c07.90089321@news.greenlnk.net> <3f1fc2d7.100025238@news.greenlnk.net> <3f1ffea7.115337085@news.greenlnk.net> NNTP-Posting-Host: kiuk0152.chembio.ntnu.no X-Trace: tyfon.itea.ntnu.no 1059115178 12516 129.241.83.78 (25 Jul 2003 06:39:38 GMT) X-Complaints-To: usenet@itea.ntnu.no NNTP-Posting-Date: Fri, 25 Jul 2003 06:39:38 +0000 (UTC) User-Agent: slrn/0.9.7.4 (Linux) Xref: archiver1.google.com comp.lang.ada:40793 Date: 2003-07-25T06:39:38+00:00 List-Id: Simon Wright wrote: > But you must be very careful where the gcc-lib/i686-whatever-linux > stuff goes -- not on top of your working standard compiler. That is no problem: /usr/lib/gcc-lib/i486-linux/2.8.1/ ^^^^^ gcc version > So you need a clean way of putting the GNAT builds (especially if you > have more than one) in places where they can't be mistaken and will > never end up on your path. You cannot have two gnat compilers at the same time. At least not as the standard compiler. > I choose /opt because if didn't seem like a bad idea; if it was, I am > very sorry. /usr/lib/gnat-3.15p (for example) would be a perfectly > good place, or /usr/local/gnat-3.15p. > > You could easily then install gnatgcc and friends by symlinks in > /usr/local/bin (say). > > The point of my gnatfe is to do effectively just that but in a way > that you can alter the compiler actually used by changing an > environment variable, which is effectively the prefix you built the > compiler with. Sure, but it makes it harder to maintain as a package I would say. Normal practice if you need more than one gcc is that is is named: gcc-2.95 gcc-3.2 gcc-3.3 etc... and gcc symlinks to the standard. Of course one could do that too, but then one might get problems with gnatmake calling wrong gnatgcc because of bad symlinks. > I quite realize that if you're building a package for people to > install & use on the other side of the world without handholding, > things may look different! Exactly -- Ada95 is good for you. http://www.crystalcode.com/codemage/MainMenu/Coding/Ada/IntroducingAda.php