public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: huntbs@lycos.com
Cc: gcc@gcc.gnu.org, M_J_BUTCHER@compuserve.com, gcc-help@gcc.gnu.org
Subject: Re: Tutorial 4b
Date: Wed, 26 Jun 2002 13:49:00 -0000	[thread overview]
Message-ID: <200206262049.g5QKnM025848@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <OGLAKCCKBCJCKDAA@mailcity.com> (huntbs@lycos.com)


>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? 

littlegcc is just a c compiler used to build newlib which is required
to build libstdc++v3 in the fourth step.  In the fourth step when
building 'gcc', '--enable-languages=c,c++' forces a c++ compiler to be
built which is used to build libstc++v3(also in the fourth step).

I hope that makes it just the faintest bit clearer :-)

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

  reply	other threads:[~2002-06-26 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 13:42 Brett Hunt
2002-06-26 13:49 ` Peter Barada [this message]
  -- 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=200206262049.g5QKnM025848@hyper.wm.sps.mot.com \
    --to=pbarada@mail.wm.sps.mot.com \
    --cc=M_J_BUTCHER@compuserve.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=huntbs@lycos.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).