public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stew@tenbox.com Subject: Re: libstdc++/9776: -static-libgcc does not produce a static link to libstdc++, instead always dynamic Date: Thu, 20 Feb 2003 18:23:00 -0000 [thread overview] Message-ID: <20030220182319.22057.qmail@sources.redhat.com> (raw) Synopsis: -static-libgcc does not produce a static link to libstdc++, instead always dynamic State-Changed-From-To: open->closed State-Changed-By: bkoz State-Changed-When: Thu Feb 20 18:23:19 2003 State-Changed-Why: Err, -static-libgcc is just for libgcc, not for libstdc++. If you are trying to statically link libstdc++, try: g++ -static You might find the on-line documentation for gcc helpful: please consult it. best -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9776
next reply other threads:[~2003-02-20 18:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 18:23 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-20 16:46 Phil Edwards 2003-02-20 16:36 stew
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=20030220182319.22057.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=stew@tenbox.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: linkBe 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).