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: cm@mihalis.demon.co.uk (Chris Morgan) Subject: Re: GNAT 3.07 public release Date: 1996/11/28 Message-ID: #1/1 X-Deja-AN: 201184991 x-nntp-posting-host: mihalis.demon.co.uk references: <1996Nov19.112349.1@eisner> organization: Linux Hackers Unlimited newsgroups: comp.lang.ada Date: 1996-11-28T00:00:00+00:00 List-Id: In article Rolf Ebert writes: The usual place for gcc on any (intel) Linux is /usr/lib/gcc-lib/i486-linux/2.7.2 variable in the version number of gcc (the last part of the path). The leading part of the path is fixed by the Linux GCC maintainer H. Lu. *All* Linux distributions adhere to that standard. Whoever built linux binary version did not follow his own advice explained in the README.Linux. If you don't provide a target archtecture to "configure" it will guess where it is and guesses i586-unknown-linux. When running "configure" you explicitely have to say "i486-linux". This is good news. I thought the confusion over pathnames was just a feature of Linux's rapid development at the moment. Hopefully future GNAT releases will be configured to correctly install in vanilla Slackware. I may build compilers at work, but at home I'm too tired of breaking my entire system, I prefer safe upgrades so I can continue to rebuild my kernel. Have you pointed out this mistake to Sean McNeil? Chris -- Christopher Morgan