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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,92e58113fdb96ff0 X-Google-Attributes: gid103376,public From: Rolf Ebert Subject: Re: GNAT 3.07 public release Date: 1996/12/03 Message-ID: #1/1 X-Deja-AN: 202292593 references: <1996Nov19.112349.1@eisner> organization: R. Ebert at home newsgroups: comp.lang.ada Date: 1996-12-03T00:00:00+00:00 List-Id: cm@mihalis.demon.co.uk (Chris Morgan) writes: CM> In article Rolf Ebert CM> writes: RE> The usual place for gcc on any (intel) Linux is RE> /usr/lib/gcc-lib/i486-linux/2.7.2 RE> variable in the version number of gcc (the last part of the path). The RE> leading part of the path is fixed by the Linux GCC maintainer H. Lu. RE> *All* Linux distributions adhere to that standard. RE> Whoever built linux binary version did not follow his own advice RE> explained in the README.Linux. CM> This is good news. I thought the confusion over pathnames was just a CM> feature of Linux's rapid development at the moment. Hopefully future CM> GNAT releases will be configured to correctly install in vanilla CM> Slackware. I may build compilers at work, but at home I'm too tired of CM> breaking my entire system, I prefer safe upgrades so I can continue to CM> rebuild my kernel. Have you pointed out this mistake to Sean McNeil? I sent a copy of the above article to report@gnat.com, but had no answer so far (I'm not a paying customer). I don't think that Sean built the last release as he is aware of such issues. I suppose someone else did it for him this time. That one built gcc/gnat in the usual gcc way (without specifying the architecture) which is not the usual Linux way (providing i486-linux to configure) CM> Chris CM> -- CM> Christopher Morgan Rolf