From: Ian Lance Taylor <iant@google.com>
To: "Mailaripillai\@google.com, Kannan Jeganathan" <kannanmj@hp.com>
Cc: "gcc-help\@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: building libstdc++ standalone
Date: Tue, 19 Jun 2012 21:10:00 -0000 [thread overview]
Message-ID: <mcr4nq72eld.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <AA6ADB5A789EDD4DA355F183E8ECDFA6607F6839@G4W3300.americas.hpqcorp.net> (Kannan Jeganathan Mailaripillai's message of "Mon, 18 Jun 2012 19:33:48 +0000")
"Mailaripillai, Kannan Jeganathan" <kannanmj@hp.com> writes:
> I want to build libstdc++ separately (i.e without building toplevel gccsrcdir).
> Please let me know whether it is possible to do so? In the configure page of
> libstc++ there is a mention that I need to do start with the configure of the
> entire gccsrcdir and issue make. But this will start making the entire tool
> chain. I just want to fire the build of libstdc++. Any suggestions?
There is no reliable or supported way to build libstdc++ separately.
Sorry.
Ian
next prev parent reply other threads:[~2012-06-19 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 19:33 Mailaripillai, Kannan Jeganathan
2012-06-19 21:10 ` Ian Lance Taylor [this message]
2012-06-19 3:48 Mailaripillai, Kannan Jeganathan
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=mcr4nq72eld.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kannanmj@hp.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).