public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Broersma Jr <rabroersma@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GCC 4.1.1 missing g++/c++
Date: Sat, 12 Aug 2006 00:05:22 -0700 (PDT)	[thread overview]
Message-ID: <20060812070522.53855.qmail@web31805.mail.mud.yahoo.com> (raw)
In-Reply-To: <7573e9640608112338j7d85585k32af673867df047b@mail.gmail.com>

> Unless you are crazy enough to have USE=nocxx, you get a c++ compiler
> with gcc.  Others are controlled by USE flags.

I don't believe that I included the USE=nocxx variable.  I will give another try at re-building
GCC a little later just to see if I get the same effect. (Honestly, I did add a few additional Use
Flags before I emerge gcc. gdj and fortran were some of them.  I went through and pruned a few of
them when I first started having problems with some of packages failing to emerge.)

> 
> gcj - java compiler
> fortran - fortran compiler
> ...and so on.
> 
> > ncurces, groff, sys-libs/db, python
> >
> > All fail with the same error
> 
> What error?
These various errors sound very similar.  Here is an error I've transposed from the last package
in the emerge --resume --skipfirst.

../../build-aux/depcomp:line 512: execg++ not found
make[4]: *** [calc++-scanner.o] Error 127

Other packages will give up during the sanity check when they discovered there wasn't a g++
compiler for available.

Thanks for the reply.

Regards,

Richard Broersma Jr.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-08-12  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12  6:14 [gentoo-user] GCC 4.1.1 missing g++/c++ Richard Broersma Jr
2006-08-12  6:38 ` Richard Fish
2006-08-12  7:05   ` Richard Broersma Jr [this message]
2006-08-12  8:03     ` Richard Fish
2006-08-14  5:54     ` Dirk Heinrichs
2006-08-14 11:21       ` Richard Broersma Jr

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=20060812070522.53855.qmail@web31805.mail.mud.yahoo.com \
    --to=rabroersma@yahoo.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox