public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "James dot W dot Mckelvey at jpl dot nasa dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/16140] New: Errors in libstdc++ testsuite; recent CVS Date: Tue, 22 Jun 2004 15:20:00 -0000 [thread overview] Message-ID: <20040622152031.16140.James.W.Mckelvey@jpl.nasa.gov> (raw) Most of the suite passes, but I get errors like these: /tmp/ccJOH1iG.o: In function `test01()': /tmp/ccJOH1iG.o(.text._Z6test01v+0x6c): undefined reference to `typeinfo for wchar_t' /tmp/ccJOH1iG.o: In function `test01()': /mnt/home3/utilities/gcc/libstdc++-v3/testsuite/27_io/fpos/14320-1.cc:43: undefined reference to `typeinfo for short' /mnt/home3/utilities/gcc/libstdc++-v3/testsuite/27_io/fpos/14320-1.cc:45: undefined reference to `typeinfo for signed char' /mnt/home3/utilities/gcc/libstdc++-v3/testsuite/27_io/fpos/14320-1.cc:45: undefined reference to `typeinfo for signed char' /mnt/home3/utilities/gcc/libstdc++-v3/testsuite/27_io/fpos/14320-1.cc:47: undefined reference to `typeinfo for char' collect2: ld returned 1 exit status mushroom~...gcc-obj>uname -a SunOS mushroom 5.7 Generic_106541-19 sun4u sparc SUNW,Ultra-2 mushroom~...gcc-obj>alias CONFIGURECVS setenv CC gcc ; /mnt/home3/utilities/gcc/configure --prefix=/mnt/home3/utilities --verbose --with-as=/mnt/home3/utilities/bin/as --with-ld=/mnt/home3/utilities/bin/ld --with-gnu-as --with-gnu-ld --disable-multilib --enable-languages=c++ |& tee clog mushroom~...gcc-obj>alias BUILD nice gmake CFLAGS='-O' BOOT_CFLAGS='-O' LIBCFLAGS='-g -O' CXXFLAGS='-O' LIBCXXFLAGS='-g -O -fno-implicit-templates' bootstrap |& tee log mushroom~...gcc-obj>g++ -v Reading specs from /mnt/home3/utilities/lib/gcc/sparc-sun-solaris2.7/3.5.0/specs Configured with: /mnt/home3/utilities/gcc/configure --prefix=/mnt/home3/utilities --verbose --with-as=/mnt/home3/utilities/bin/as --with-ld=/mnt/home3/utilities/bin/ld --with-gnu-as --with-gnu-ld --disable-multilib --enable-languages=c++ Thread model: posix gcc version 3.5.0 20040621 (experimental) -- Summary: Errors in libstdc++ testsuite; recent CVS Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: James dot W dot Mckelvey at jpl dot nasa dot gov CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: sparc-sun-solaris2.7 GCC host triplet: sparc-sun-solaris2.7 GCC target triplet: sparc-sun-solaris2.7 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16140
next reply other threads:[~2004-06-22 15:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-22 15:20 James dot W dot Mckelvey at jpl dot nasa dot gov [this message] 2004-06-22 15:21 ` [Bug libstdc++/16140] " James dot W dot Mckelvey at jpl dot nasa dot gov 2004-06-22 15:37 ` [Bug c++/16140] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-09 4:56 ` pinskia at gcc dot gnu dot org 2004-07-12 15:14 ` James dot W dot Mckelvey at jpl dot nasa dot gov 2004-07-12 15:16 ` James dot W dot Mckelvey at jpl dot nasa dot gov 2004-07-12 15:19 ` pinskia at gcc dot gnu dot org 2004-07-16 14:45 ` James dot W dot Mckelvey at jpl dot nasa dot gov 2004-08-12 14:55 ` James dot W dot Mckelvey at jpl dot nasa dot gov 2004-08-12 14:57 ` pinskia at gcc dot gnu dot 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=20040622152031.16140.James.W.Mckelvey@jpl.nasa.gov \ --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: 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).