From: Dan Brown <dbrown@bruxton.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Problem with 'cc1plus'
Date: Wed, 31 Jan 2001 16:10:00 -0000 [thread overview]
Message-ID: <3A77AF9F.EB577C1D@bruxton.com> (raw)
In-Reply-To: <3A76C6EB.D430BE45@redhat.com>
Jonathan,
Thank you very much for the help. The problem turned out to lie in a
direction you pointed me in - it was an operator malfunction. When I
built the compiler, I wrote LANGUAGES="c c", not LANGUAGES="c c++". This
means that I failed to build the C++ support. Now everything works.
-- Dan
[The following is edited]
Jonathan Larmour wrote:
>
> Dan Brown wrote:
> >
> > During the build, an error occurs that arm-elf-gcc cannot find
> > 'cc1plus'. The executable in fact does not exist. The error occurs when
> > building startup.cxx, which has a line of C++ code in it. The compiles
> > of C code appear to work fine.
>
> Type "arm-elf-gcc -v". Is there a cc1plus file in the same directory as the
> specs file it lists there? If not, perhaps your compiler build didn't work
> for some reason, like not putting quotes in the make argument: LANGUAGES="c
> c++"
>
--
Dan Brown
Bruxton Corporation
http://www.bruxton.com
206 782-8862
prev parent reply other threads:[~2001-01-31 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 19:49 Dan Brown
2001-01-30 5:51 ` Jonathan Larmour
2001-01-31 16:10 ` Dan Brown [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=3A77AF9F.EB577C1D@bruxton.com \
--to=dbrown@bruxton.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).