From: Alexandre Oliva <aoliva@redhat.com>
To: s.kwiatkowski@t-online.de (Sebastian Kwiatkowski)
Cc: gcc-help@gcc.gnu.org
Subject: Re: cannot exec cpp0
Date: Mon, 30 Jul 2001 14:20:00 -0000 [thread overview]
Message-ID: <or8zh6gln8.fsf@feijoada.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3B62FE0F.5060306@t-online.de>
On Jul 28, 2001, s.kwiatkowski@t-online.de (Sebastian Kwiatkowski) wrote:
> After installing it, I get (building anything):
> gcc: installation problem, cannot exec `cpp0': No such file or directory
> But actually cpp0 exists in /usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3
Did you configure GCC with --prefix=/usr ? If not, you'll have to
rebuild.
> Could this problem have something to do with the conten of the
> following extract of the build log?
Nope, these errors at the end of a stage are normal: in general, only
the C compiler is build in stage 1, but the staging process tries to
move everything into the stage1 sub-directory in case one had run
`make all' before realizing s/he should have run `make bootstrap'.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-07-30 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 9:02 Sebastian Kwiatkowski
2001-07-30 14:20 ` Alexandre Oliva [this message]
2007-02-28 5:12 Rangaswamy, Parthasarathy (Parthasarathy)
2007-02-28 5:59 ` Zhang, Fan (Fan)
2007-02-28 6:09 Rangaswamy, Parthasarathy (Parthasarathy)
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=or8zh6gln8.fsf@feijoada.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=s.kwiatkowski@t-online.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).