From: "Brett Hunt" <huntbs@lycos.com>
To: "gcc" <gcc@gcc.gnu.org>, "Mark Butcher" <M_J_BUTCHER@compuserve.com>
Cc: "gcc-help" <gcc-help@gcc.gnu.org>
Subject: Re: Tutorial 4b
Date: Wed, 26 Jun 2002 13:42:00 -0000 [thread overview]
Message-ID: <OGLAKCCKBCJCKDAA@mailcity.com> (raw)
Mark,
This is just a guess from looking at your script. FYI, I have not reviewed the webpage you listed in a previous email to understand the build process but something stuck out as I read your script.
Your littlegcc is compiled with the option --with-languages=c.
I'm assuming that later you use this same compiler to build the full-blown gcc which contains c++ code. I'm out on a limb here since I don't know if by the time the error occurs you are using the c++ enabled full-blown gcc or not. But if you compile the littlegcc without c++ support, might that not result in an error later trying to compile c++ libraries?
Just my two cents
---
brett
On Wed, 26 Jun 2002 05:36:28
Mark Butcher wrote:
>Hi All
>
>During the night I let a modified version of the MCORE script (simply
>MCORE-ELF replaced by ARM-ELF) run.
>
>The result was the identical build error when trying to simpiler the first
>c++ library source. This seems proof that there is something wrong with the
>script.
>
>Does anyone see the error ????
>
>Regards
>
>Mark
>
____________________________________________________________
Win a first-class trip to New Orleans and vacation Elvis Style!.
Enter NOW!
http://r.lycos.com/r/sagel_mail/http://www.elvis.lycos.com/sweepstakes/
next reply other threads:[~2002-06-26 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 13:42 Brett Hunt [this message]
2002-06-26 13:49 ` Peter Barada
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 15:00 Mark Butcher
2002-06-26 2:37 Mark Butcher
2002-06-26 8:08 ` Peter Barada
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=OGLAKCCKBCJCKDAA@mailcity.com \
--to=huntbs@lycos.com \
--cc=M_J_BUTCHER@compuserve.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).