[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gcc-2.6.3
- To: mint@terminator.rs.itd.umich.edu
- Subject: Re: gcc-2.6.3
- From: "troy (t.) carpenter" <troyc@bnr.ca>
- Date: Tue, 2 May 1995 14:54:00 -0400
- Sender: "troy (t.) carpenter" <troyc@bnr.ca>
- X400-content-type: P2-1984 (2)
- X400-mts-identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.418:02.04.95.18.57.01]
- X400-originator: /dd.id=1745965/g=troy/i=t/s=carpenter/@bnr.ca
In message "gcc-2.6.3", waldi@moacs.indiv.nl.net writes:
> Frank Bartels wrote:
>
> > And as gcc is our default compiler, I vote for the
> > following (4.4BSD style) pathnames:
> >
> > /usr/bin/cc
> > /usr/bin/gcc [symbolic link to /usr/bin/cc]
> > /usr/bin/cpp [a shellscript executing the real cpp]
> > /usr/libexec/cpp
> > /usr/libexec/cc1
> > /usr/libexec/cc1plus
>
> Looks fine for a distribution that ignores the standards set
> by Atari. ,-)
I know I don't use Lattice C. And I don't care if it avoids Atari's standard
set, if Atari even has a "standard set" for MiNT configurations, as long as it
simplifies configuration and things compile.
I agree with Christian Lynbech's suggestion about putting things in /usr/gnu.
I have already done this with my binaries, but still had to put the includes
and libs in /usr/include & /usr/lib, respectively. It might even simplify
upgrades to newer versions, instead of having different install paths which
vary from release to release.
Bell-Northern Research Troy Carpenter Atlanta, Georgia
troyc@bnr.ca I speak for myself, not BNR
"You're so open minded that your brain leaked out" - Steve Taylor
*>>>>>>>>>>>>>>>>>> The best thing in life costs exactly that <<<<<<<<<<<<<<<*