public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: HKOELMAN@bouyguestelecom.fr
To: gcc-help@gcc.gnu.org
Subject: Link error
Date: Thu, 17 Oct 2002 08:11:00 -0000	[thread overview]
Message-ID: <776BD5C0BA88D4118ABD0008C79F307704AE57F1@bt1sqteb.bpa.bouyguestelecom.fr> (raw)

Hello,

I'm puzzled with the following link error.

I'm using gcc 3.0.1 on Solaris 8. The libcometpfas.so compiles with gcc
2.1.95 and refuses with gcc 3.0.1.

The message is :
----- start -----
bonobo> make -f test.mk
/usr/users/armili/testcomet/COMET_U_1002/S28T710/test/tst01
g++ -o /usr/users/armili/testcomet/COMET_U_1002/S28T710/test/tst01
/usr/users/armili/testcomet/COMET_U1002/S28T710/obj/tst01.
o -L/usr/users/armili/testcomet/COMET_U_1002/S28T710/lib -lcometpfas
-L/usr/users/armili/testcomet/COMET_U1002/CORATN/lib/S28T710 -lAtn
-L/u01/app/tuxedo/710/lib -ltux -lbuft  -lfml -lfml32
Undefined                       first referenced
 symbol                             in file
CCppsvcfrm::doSvcsCall(char*, context_t*, CParam_in&, CParam_out&,
ils_err_t*)/usr/users/armili/testcomet/COMET_U1002/S28T710/obj/tst01.o
ostream::operator<<(ostream &(*)(ostream
&))/usr/users/armili/testcomet/COMET_U_1002/S28T710/lib/libcometpfas.so
endl(ostream &)
/usr/users/armili/testcomet/COMET_U_1002/S28T710/lib/libcometpfas.so
CCppsvcfrm::CCppsvcfrm()
/usr/users/armili/testcomet/COMET_U_1002/S28T710/obj/tst01.o
cerr
/usr/users/armili/testcomet/COMET_U_1002/S28T710/lib/libcometpfas.so
CCppsvcfrm::~CCppsvcfrm()
/usr/users/armili/testcomet/COMET_U_1002/S28T710/obj/tst01.o
ostream::operator<<(char const *)
/usr/users/armili/testcomet/COMET_U_1002/S28T710/lib/libcometpfas.so
ld: fatal: Symbol referencing errors. No output written to
/usr/users/armili/testcomet/COMET_U_1002/S28T710/test/tst01
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target
`/usr/users/armili/testcomet/COMET_U_1002/S28T710/test/tst01'
----- end -----

Any help is appreciated

Regards Herbert

             reply	other threads:[~2002-10-17 15:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  8:11 HKOELMAN [this message]
     [not found] <AANLkTiniPnQ-ioijpQXhMC1ygSqNSZsEGW2O-OVS5Qa8@mail.gmail.com>
2010-08-12 10:18 ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2009-04-01 13:23 link error Duan Wang
2009-04-01 13:42 ` Axel Freyn
2008-08-15 20:39 Link error Vardhan, Sundara (GE Infra, Energy)
2008-07-24 21:03 Vardhan, Sundara (GE Infra, Energy)
2008-07-24 23:55 ` Rob Sherry
2008-07-25 13:32   ` Vardhan, Sundara (GE Infra, Energy)
2008-07-28 11:41     ` Andrew Haley
2008-07-28 12:14       ` Vardhan, Sundara (GE Infra, Energy)
2008-07-28 13:26         ` Andrew Haley
2008-07-29  8:56           ` Ralf Wildenhues
2008-07-29 11:49             ` Andrew Haley
2008-07-29 13:43               ` Vardhan, Sundara (GE Infra, Energy)
2008-07-24 10:04 Vardhan, Sundara (GE Infra, Energy)
2005-10-21 20:22 link error Moon Hwang
2005-10-21 23:08 ` Brian Dessent
2002-08-13  6:54 Link Error Tom Browder
2002-08-13  7:16 ` Ish Rattan
2002-08-13  7:30   ` Tom Browder
2002-08-13  7:59     ` Ish Rattan
2001-06-05 14:22 link error Alex Fridman

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=776BD5C0BA88D4118ABD0008C79F307704AE57F1@bt1sqteb.bpa.bouyguestelecom.fr \
    --to=hkoelman@bouyguestelecom.fr \
    --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).