From: David Edelsohn <dje@watson.ibm.com>
To: "Prashant S Kulkarni" <prashant.s.kulkarni@aexp.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Help Needed
Date: Wed, 28 Apr 2004 17:51:00 -0000 [thread overview]
Message-ID: <200404281751.i3SHpWT33134@makai.watson.ibm.com> (raw)
In-Reply-To: Message from "Prashant S Kulkarni" <prashant.s.kulkarni@aexp.com> of "Tue, 27 Apr 2004 22:19:38 PDT." <OFCC93C288.0528455F-ON07256E84.001CA2E4-07256E84.001D4276@ipc.us.aexp.com>
>>>>> Prashant S Kulkarni writes:
Prashant> I am compiling xerces-c25.0 using gcc 3.0 on AIX 4.2.2 and i have all objects
Prashant> file created. But when while linking all .o file I am getting error...
Prashant> AIX uses makeC++SharedLib for shared lib creation. Can you please tell me what
Prashant> option or which compiler in gcc suite should I use to create shared lib for
Prashant> above on gcc??.
Prashant> I am getting the error as follows. Any help is really appreciated..
GCC can create shared libraries with the -shared commandline
option. The default is AIX-style shared libraries, but you can use -Wl,-G
to compile the library and -Wl,-brtl during the final link to generate
SVR4-style libraries.
When compiling and linking C++ code, you should use the "g++"
driver, not the "gcc" driver.
When compiling and linking pthread code, you should use the
-pthreads commandline option, which implicitly links with -lpthreads.
-p 5000
and
-bmap:/home/pkulka/poc/xerces-c-src_2_5_0//obj/libxerces-c25.0.map
are IBM xlC compiler options. You need to use the correct GCC commandline
options.
/usr/lpp/xlC/lib contains libraries for xlC. xlC C++ ABI is not
compatible with G++ ABI -- you cannot mix C++ object files produced by the
two compilers.
David
next prev parent reply other threads:[~2004-04-28 17:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 5:19 Prashant S Kulkarni
2004-04-28 17:51 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-27 10:17 help needed anandulle
2009-07-27 18:10 ` Andi Hellmund
2006-03-07 2:03 Help needed wenghwee
2005-08-25 23:40 RALPH OLD JR
2005-08-26 5:20 ` Arturas Moskvinas
[not found] <20040830122911.24797.qmail@webmail17.rediffmail.com>
2004-08-30 16:09 ` Help Needed Eljay Love-Jensen
2004-06-08 16:22 help needed lrtaylor
2004-06-09 9:25 ` Claudio Bley
2004-06-06 2:55 Naga Raju Thogiti
2004-06-08 10:17 ` Claudio Bley
2004-06-08 14:22 ` Claudio Bley
2004-05-29 0:41 xuyi
2004-05-29 19:03 ` Sumith Makam
2003-11-20 12:46 Jomy Abraham
2003-03-17 7:51 Help Needed Dockeen
2003-03-16 21:32 R.Karthik Narayanan
2003-03-17 3:02 ` LLeweLLyn Reese
2003-03-18 0:25 ` Karthik Narayanan
[not found] ` <1048367240.1224.51.camel@x1-6-00-e0-18-67-55-94>
2003-03-18 1:51 ` LLeweLLyn Reese
2001-10-13 0:36 help needed ram
2001-10-13 1:41 ` Florian Weimer
2000-09-26 6:30 Kazu Hirata
2000-09-26 4:44 BRAHMAIAH VALLABHANENI
2000-09-26 21:49 ` Kiran Kumar K
2000-09-13 3:54 brahmaiah vallabhaneni
2000-04-09 21:24 Help needed Mahadev Cholachgudda
2000-04-07 23:07 Mahadev Cholachgudda
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=200404281751.i3SHpWT33134@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=prashant.s.kulkarni@aexp.com \
/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).