public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "birender.singh at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53297] Linker error on solaris 10 using gcc-4.4.4 64bit.
Date: Thu, 10 May 2012 06:09:00 -0000 [thread overview]
Message-ID: <bug-53297-4-199Qa5P3Gz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53297-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53297
--- Comment #3 from birender.singh at hotmail dot com 2012-05-10 05:37:31 UTC ---
(In reply to comment #2)
> Oh well.
>
> *** This bug has been marked as a duplicate of bug 53275 ***
This bugs reported have been problems caused by GCC-4.4.4 libstdc++ library on
solaris10 sparc, please have a look below, am using this library but still
getting below error.
Undefined first referenced symbol in file
std::basic_streambuf<char, std::char_traits<char> >::seekoff(long long,
std::_Ios_Seekdir, std::_Ios_Openmode)
../../../nobuilds/lib/sparc_SunOS_64/release/libPoco.a(Base64Decoder.o)
ld: fatal: Symbol referencing errors. No output written to
sparc_SunOS_64/release/SuiteMain
collect2: ld returned 1 exit status
Accepting the Bug 53275 was invalid due to library missing
next prev parent reply other threads:[~2012-05-10 5:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:08 [Bug libstdc++/53297] New: " birender.singh at hotmail dot com
2012-05-09 16:29 ` [Bug libstdc++/53297] " paolo.carlini at oracle dot com
2012-05-09 16:29 ` paolo.carlini at oracle dot com
2012-05-10 6:09 ` birender.singh at hotmail dot com [this message]
2012-05-11 11:06 ` birender.singh at hotmail dot com
2012-05-11 11:14 ` paolo.carlini at oracle dot com
2012-05-11 11:19 ` paolo.carlini at oracle dot com
2012-05-11 13:52 ` redi 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-53297-4-199Qa5P3Gz@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).