public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adrian von Bidder <avbidder@acter.ch>
To: gcc <gcc@gcc.gnu.org>
Subject: Not building libstdc++
Date: Wed, 05 Dec 2001 07:15:00 -0000	[thread overview]
Message-ID: <3C0E3A23.702031B9@acter.ch> (raw)

Heyho!

Still working with uclinux... (But this should not matter here)

I'm currently building the c++ compiler without libstdc++-v3 by
untarring gcc-core and gcc-g++ and removing the libstdc++-v3 subdir
before running configure. Is there a way not to build the library by
specifying a configure option? (like --without-libc, which I also use
currently).

rationale: 
 - I don't want libstdc++ because it won't build without a libc, and I
build uclibc externally, not from the gcc build process
 - removing the subdir by hand is ugly when I want to apply patches
(3.0.1 to 3.0.2 etc.) or making diffs between my build version an the
tars - manual fiddling is required every time.
 
greets from Zürich
-- vbi

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C0E3A23.702031B9@acter.ch \
    --to=avbidder@acter.ch \
    --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).