public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "earnie at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/57797] New: configure --enable-languages=c builds libstdc++-v3
Date: Wed, 03 Jul 2013 12:32:00 -0000	[thread overview]
Message-ID: <bug-57797-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57797

            Bug ID: 57797
           Summary: configure --enable-languages=c builds libstdc++-v3
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: earnie at users dot sourceforge.net

When specifying --enable-languages=c the libstdc++-v3 directory is being
configured and built.  I had to remove the directory from the source to prevent
the build.  Here is the full set of configure options:

--prefix=/mingw --enable-languages=c --disable-sjlj-exceptions --with-dwarf2
--enable-shared --disable-win32-registry --disable-build-poststage1-with-cxx
--enable-version-specific-runtime-libs --host=i686-pc-mingw32
--target=i686-pc-mingw32 --build=i686-pc-mingw32 --disable-multilib
--without-pic --with-gnu-ld --with-gnu-as --without-readline
--disable-libstdcxx --enable-lto --enable-multilib --enable-multiarch
--disable-tls --enable-threads --disable-cxx --enable-assembly --enable-fft
--disable-nls --disable-rpath


             reply	other threads:[~2013-07-03 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 12:32 earnie at users dot sourceforge.net [this message]
2013-07-03 12:57 ` [Bug bootstrap/57797] " redi at gcc dot gnu.org
2013-07-03 20:02 ` earnie at users dot sourceforge.net
2013-09-11  9:45 ` ktietz at gcc dot gnu.org
2013-09-11 11:43 ` earnie at users dot sourceforge.net
2013-09-11 11:48 ` mikpe at it dot uu.se
2013-09-11 11:54 ` ktietz at gcc dot gnu.org
2013-09-11 12:03 ` earnie at users dot sourceforge.net
2013-09-11 12:25 ` ktietz at gcc dot gnu.org

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=bug-57797-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).