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++/102341] [modules] "error: conflicting exporting declaration" for anything previously declared
Date: Wed, 15 Sep 2021 11:28:50 +0000 [thread overview]
Message-ID: <bug-102341-4-c8NX2ZhDth@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102341-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102341
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-09-15
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> This seems to make it impractical to create a module interface unit for any
> library that is currently defined in header files, such as libstdc++.
I can work around this by adding 'export' into the headers themselves (as a
macro that expands to nothing unless included from the module interface unit).
next prev parent reply other threads:[~2021-09-15 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 9:46 [Bug c++/102341] New: [modules] alias-declaration and typedef-declaration conflict in module interface unit redi at gcc dot gnu.org
2021-09-15 9:52 ` [Bug c++/102341] " redi at gcc dot gnu.org
2021-09-15 10:34 ` redi at gcc dot gnu.org
2021-09-15 11:28 ` redi at gcc dot gnu.org [this message]
2021-09-15 11:37 ` [Bug c++/102341] [modules] "error: conflicting exporting declaration" for anything previously declared pilarlatiesa at gmail dot com
2021-09-15 11:50 ` redi at gcc dot gnu.org
2023-11-25 1:45 ` cvs-commit 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-102341-4-c8NX2ZhDth@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).