public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sailer at sailer dot dynip.lugs.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66030] New: [5.1.0] std::codecvt_byname missing from libstdc++ DLL
Date: Tue, 05 May 2015 23:34:00 -0000 [thread overview]
Message-ID: <bug-66030-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66030
Bug ID: 66030
Summary: [5.1.0] std::codecvt_byname missing from libstdc++ DLL
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: sailer at sailer dot dynip.lugs.ch
Target Milestone: ---
Created attachment 35470
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35470&action=edit
testcase
Compiling the attached simple test case fails linking for mingw32, because
libstdc++ DLL misses codecvt_byname symbols. This test case works with mingw32
gcc 4.9.2.
$ i686-w64-mingw32-g++ -o x.exe x.c
/tmp/ccIXAXf0.o:x.c:(.text+0x74): undefined reference to
`std::codecvt_byname<wchar_t, char, int>::codecvt_byname(char const*, unsigned
int)'
collect2: error: ld returned 1 exit status
$ i686-w64-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=i686-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-w64-mingw32/5.1.0/lto-wrapper
Target: i686-w64-mingw32
Configured with: ../configure --prefix=/usr --bindir=/usr/bin
--includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info
--datadir=/usr/share --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --with-gnu-as --with-gnu-ld --verbose
--without-newlib --disable-multilib --disable-plugin --with-system-zlib
--disable-nls --without-included-gettext --disable-win32-registry
--enable-languages=c,c++,objc,obj-c++,fortran
--with-bugurl=http://bugzilla.redhat.com/bugzilla --with-cloog
--enable-threads=posix --enable-libgomp --target=i686-w64-mingw32
--with-sysroot=/usr/i686-w64-mingw32/sys-root
--with-gxx-include-dir=/usr/i686-w64-mingw32/sys-root/mingw/include/c++
Thread model: posix
gcc version 5.1.0 20150422 (Fedora MinGW 5.1.0-1.fc23) (GCC)
next reply other threads:[~2015-05-05 23:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 23:34 sailer at sailer dot dynip.lugs.ch [this message]
2015-05-05 23:35 ` [Bug libstdc++/66030] " sailer at sailer dot dynip.lugs.ch
2015-05-26 13:49 ` hamzaalloush at live dot com
2015-05-27 15:08 ` redi at gcc dot gnu.org
2015-06-01 16:02 ` jroivas at iki dot fi
2015-06-01 16:21 ` redi at gcc dot gnu.org
2015-06-01 16:30 ` redi at gcc dot gnu.org
2015-06-01 17:49 ` jroivas at iki dot fi
2015-06-01 18:22 ` jroivas at iki dot fi
2015-06-01 22:49 ` redi at gcc dot gnu.org
2015-06-05 16:56 ` jroivas at iki dot fi
2015-06-06 8:49 ` ktietz at gcc dot gnu.org
2015-06-06 12:10 ` redi at gcc dot gnu.org
2015-06-08 15:13 ` redi at gcc dot gnu.org
2015-06-09 4:42 ` jroivas at iki dot fi
2015-06-15 12:31 ` redi at gcc dot gnu.org
2015-06-15 12:32 ` redi at gcc dot gnu.org
2015-07-04 0:50 ` hamzaalloush at live dot com
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-66030-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).