From: Jonathan Larmour <jlarmour@redhat.com>
To: Greg Shubin <gshubin@sonic.net>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] "too many input files" error from cpp
Date: Tue, 05 Sep 2000 11:38:00 -0000 [thread overview]
Message-ID: <39B53D87.6D931896@redhat.com> (raw)
In-Reply-To: <39B53699.DD8E6C15@sonic.net>
Greg Shubin wrote:
>
> I've read the FAQ and the archives of this list. The standard answer
> seems to be "you've moved the tools from where you built them. Either
> put symlinks to the build directories or build them again". Well, I
> haven't moved them from the build directory and I still get this. I am
> bullding on Mandrake 7.1, which I believe is basically Redhat 6.2. I've
> rebuilt the tools several times on two machine and I still get this
> error. I also tried the latest snapshot (8/28 I think it was), and that
> didn't even run (it wanted cpp0, which was nowhere to be found).
Out of interest, do you have the tools at the head of your path? If you do
`which cpp` what does it give you? Have you got GCC_EXEC_PREFIX set (the
answer should be no)?
I'm interested about what the cause is if not moved tools.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-09-05 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-05 10:59 Greg Shubin
2000-09-05 11:38 ` Jonathan Larmour [this message]
2000-09-05 13:54 ` Greg Shubin
2000-09-05 14:51 ` Greg Shubin
[not found] ` <39B5BACF.95AAE4F5@wco.com>
2000-09-11 15:25 ` [ECOS] "too many input files" error from cpp (still more) Jonathan Larmour
2000-09-11 16:30 ` Greg Shubin
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=39B53D87.6D931896@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gshubin@sonic.net \
/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).