From: "Ajay Bansal" <abansal@netegrity.com>
To: "'Ajay Bansal'" <abansal@netegrity.com>, <gcc-help@gcc.gnu.org>
Subject: RE: Strange warning for program compiled with gcc 3.2.1
Date: Mon, 15 Sep 2003 16:41:00 -0000 [thread overview]
Message-ID: <20030915164100.emeaXQyG1AZ3IkuqjLKysY2Pp9GmtQhUhUi2eYKDUo4@z> (raw)
In-Reply-To: <GTSMTP02wQ21ju2iDL60000ae2e@gtsmtp02.ad.infosys.com>
Nobody for this one.. :(
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Ajay Bansal
Sent: Thursday, August 28, 2003 11:36 PM
To: gcc-help@gcc.gnu.org
Hey guys...
Please help me finding a quick and good solution for the same.
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Ajay Bansal
Sent: Thursday, August 28, 2003 10:54 AM
To: gcc-help@gcc.gnu.org
Hi All
I am receiving the following warning when I run a program, which has been
compiled with gcc 3.2.1 on Linux Advanced Server 2.1
/home/porting/abansal/lib/libstdc++.so.5: no version information available
(required by
/home/porting/abansal/lib/libbtunicode.so)
/tmp/1224.tmp/program.exe:
/home/porting/abansal/lib/libstdc++.so.5: no version information available
(required by
/home/porting/abansal/lib/libbtunicode.so)
What could be it???
---Ajay
next parent reply other threads:[~2003-09-15 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GTSMTP02wQ21ju2iDL60000ae2e@gtsmtp02.ad.infosys.com>
2003-09-15 16:41 ` Ajay Bansal [this message]
2003-09-15 16:41 ` Ajay Bansal
[not found] <GTSMTP02n6U9BekWo760000996d@gtsmtp02.ad.infosys.com>
2003-08-28 18:01 ` Ajay Bansal
2003-08-28 18:01 ` Ajay Bansal
2003-08-27 21:25 C programming Student Victoria Alvarez
2003-08-28 5:19 ` Strange warning for program compiled with gcc 3.2.1 Ajay Bansal
2003-08-28 5:19 ` Ajay Bansal
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=20030915164100.emeaXQyG1AZ3IkuqjLKysY2Pp9GmtQhUhUi2eYKDUo4@z \
--to=abansal@netegrity.com \
--cc=gcc-help@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).