public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67067] "Trouble closing elf file" and "-static-libstdc++ not implemented"
Date: Thu, 30 Jul 2015 17:07:00 -0000 [thread overview]
Message-ID: <bug-67067-4-ZHK4e8JpBx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67067-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67067
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Alex Lai from comment #1)
> the error apparently is due to the missing space between -static and
> -libstdc++.
There is no missing space, that's a valid gcc option.
next prev parent reply other threads:[~2015-07-30 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 15:25 [Bug c++/67067] New: #error -static-libstdc++ not implemented zclai at yahoo dot com
2015-07-30 15:33 ` [Bug c++/67067] "Trouble closing elf file" and "-static-libstdc++ not implemented" zclai at yahoo dot com
2015-07-30 17:07 ` redi at gcc dot gnu.org [this message]
2015-07-30 19:36 ` zclai at yahoo dot com
2015-08-01 3:28 ` zclai at yahoo dot com
2024-01-24 10:31 ` [Bug bootstrap/67067] " redi at gcc dot gnu.org
2024-01-24 13:15 ` ro 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-67067-4-ZHK4e8JpBx@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).