All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schiele <rschiele@uni-mannheim.de>
To: deedsmis@aculink.net, linux-gcc@vger.kernel.org
Subject: Re: Mistake With CPP File
Date: Fri, 2 Aug 2002 23:40:40 +0200	[thread overview]
Message-ID: <20020802214040.GA12473@schiele.local> (raw)
In-Reply-To: <3D4ACD09.A626D16@cdm01.deedsmiscentral.net>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

On Fri, Aug 02, 2002 at 12:18:49PM -0600, SoloCDM wrote:
> Robert Schiele stated the following:
> > 
> > On Fri, Aug 02, 2002 at 06:47:41AM -0600, SoloCDM wrote:
> > 
> > > It starts the linking (ln command) with /usr/bin/g++ -->
> > > /etc/alternatives/g++ --> /usr/bin/colorg++ --> /usr/bin/colorgcc.
> > > G++ is acting as a link.  If executed in the same manner as g++ to
> > > create an a.out file, without options, colorgcc doesn't execute like
> > > g++.
> > 
> > What do you have in ~/.colorgccrc?
> 
> No such file exists.  Everything for g++ and gcc is exactly as it was
> installed.

Then your installation of colorgcc is braindead, as you have an
infinite loop, because colorgcc runs /usr/bin/g++ by default, which is
itself in your case.  You need to specify the path to your real g++ in
the config file.

Robert

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de

[-- Attachment #2: Type: application/pgp-signature, Size: 524 bytes --]

      reply	other threads:[~2002-08-02 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 11:04 Mistake With CPP File SoloCDM
2002-08-01  7:09 ` Robert Schiele
2002-08-01  8:38   ` SoloCDM
2002-08-01 13:33     ` Robert Schiele
2002-08-02 12:47       ` SoloCDM
2002-08-02 13:08         ` Robert Schiele
2002-08-02 18:18           ` SoloCDM
2002-08-02 21:40             ` Robert Schiele [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020802214040.GA12473@schiele.local \
    --to=rschiele@uni-mannheim.de \
    --cc=deedsmis@aculink.net \
    --cc=linux-gcc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.