public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Adrian von Bidder <avbidder@acter.ch>
Cc: Adam Megacz <gcc@lists.megacz.com>, gcc@gcc.gnu.org
Subject: Re: configure option to disable building of libstdc++-v3 but not disable g++?
Date: Wed, 12 Dec 2001 17:16:00 -0000	[thread overview]
Message-ID: <orellzhqg7.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Adrian von Bidder's message of "12 Dec 2001 11:43:24 +0100"

On Dec 12, 2001, Adrian von Bidder <avbidder@acter.ch> wrote:

> On Wed, 2001-12-12 at 04:50, Alexandre Oliva wrote:
>> On Dec 11, 2001, Adam Megacz <gcc@lists.megacz.com> wrote:
>> 
>> > What option would I pass to configure to cause it to not build
>> > libstdc++-v3 (without simply leaving c++ out of the --with-languages=
>> > option, since I still need g++)?
>> 
>> > I can't seem to find such an option in the manual...
>> 
>> I'm afraid there's no such option.

> But simply deleting the libstdc++-v3 subdirectory does probably get you
> where you want.

Good idea.  Just to be clear: deleting it from (or renaming it in) the
source tree should indeed get you there.  Removing it from the build
tree will just get it re-created.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

      reply	other threads:[~2001-12-13  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 16:34 Adam Megacz
2001-12-11 20:05 ` Alexandre Oliva
2001-12-12  3:13   ` Adrian von Bidder
2001-12-12 17:16     ` Alexandre Oliva [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=orellzhqg7.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=avbidder@acter.ch \
    --cc=gcc@gcc.gnu.org \
    --cc=gcc@lists.megacz.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).