public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Sangwan, Vikas (CORP, GEITC)" <Vikas.Sangwan@geind.ge.com>
To: gcc@gcc.gnu.org
Subject: Clarification
Date: Tue, 13 Feb 2001 13:43:00 -0000	[thread overview]
Message-ID: <4DE51758E7CDD411A78700508B6FEB1E0120A54B@ban03xbindge.geind.ge.com> (raw)

Hello All,

	I am trying to build a shared library from a set of '.o's.  Reason
being, trying to use JNI to invoke some API code and it expects a shared
library.  

What have I done so far ?

	Earler I had static libraries with me i.e the '.a's, so used "ar -x
<file.a>" and extracted out the ..o's.  However I am trying to build a
shared object on Solaris using the folloiwiing command but there are a lof
external reference symbols thrown back.

	Text relocation remains                         referenced
    against symbol                  offset      in file
<unknown>                           0x14        tcp_scb.o
<unknown>                           0x18        tcp_scb.o
<unknown>                           0x30        tcp_scb.o
<unknown>                           0x34        tcp_scb.o
<unknown>                           0x3c        tcp_scb.o
<unknown>                           0x40        tcp_scb.o
<unknown>                           0x69c       tcp_scb.o
<unknown>                           0x6a0       tcp_scb.o
inet_ntoa                           0x790       tcp_scb.o
gethostbyaddr                       0x744       tcp_scb.o
strdup                              0x6e0       tcp_scb.o
GuStrMake                           0x6c8       tcp_scb.o
com_addr_tcpaddr_str                0x694       tcp_scb.o
strcpy                              0x620       tcp_scb.o
strcpy                              0x674       tcp_scb.o
strcpy                              0x7b4       tcp_scb.o
GuComAddrFree                       0x4d4       tcp_scb.o
ComRemoteAddr                       0x43c       tcp_scb.o
ComTcpSetAddr                       0x3b8       tcp_scb.o

	If any of you could shared your experiences, it will ge great.

Rgds
Vikas

             reply	other threads:[~2001-02-13 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13 13:43 Sangwan, Vikas (CORP, GEITC) [this message]
2001-02-14 17:09 ` Clarification Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2000-07-06  3:58 Clarification Damian Minihan
2000-07-06  4:03 ` Clarification Alexandre Oliva
2000-07-06  4:32   ` Clarification Neelakanth
2000-07-06 12:31     ` Clarification Martin v. Loewis
2000-07-06  6:42   ` Clarification Philipp Thomas
1999-02-21 15:34 Clarification Jeffrey A Law
1999-02-28 22:53 ` Clarification Jeffrey A Law

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=4DE51758E7CDD411A78700508B6FEB1E0120A54B@ban03xbindge.geind.ge.com \
    --to=vikas.sangwan@geind.ge.com \
    --cc=gcc@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).