public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wendell Beckwith <wbeckwith@directlink.net>
To: egcs@cygnus.com
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Help! Solaris 7/gcc 2.95.1 shared lib link error
Date: Fri, 29 Oct 1999 11:43:00 -0000	[thread overview]
Message-ID: <3819EB01.DE002996@directlink.net> (raw)
In-Reply-To: <E969EBF3CCF7D01195560000F804A52F041DFEA1@emss04m05.ems.lmco.com>

I upgraded from egcs 1.1.2 to gcc 2.95.2 and I have the following
linking error:

//usr/local/bin//g++ -shared file1.o file2o file3.o file4.o file5.o
file6.o   -o /tmp/mystuff/lib/libmylib.so -lnsl -lsocket  -lpthread
-lposix4
Text relocation remains                  referenced
    against symbol      offset in file
<unknown>                           0xf28
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0x44
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0x48
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0xf14
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

The above continues for several pages worth of errors.  egcs 1.1.2
compiled and link flawlessly and gcc 2.95.2 compiles flawlessly, but it
fails to link.  Has anyone seen this before (please say yes, I hate
being the only one), and more important is there a fix?

Wendell Beckwith





WARNING: multiple messages have this Message-ID

From: Wendell Beckwith <wbeckwith@directlink.net>
To: egcs@cygnus.com
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Help! Solaris 7/gcc 2.95.1 shared lib link error
Date: Sun, 31 Oct 1999 13:57:00 -0000	[thread overview]
Message-ID: <3819EB01.DE002996@directlink.net> (raw)
Message-ID: <19991031135700.KIR2a0qv-9x6oy_PqhoN6jSUDkKrNV5IxNgb7pNRqU8@z> (raw)
In-Reply-To: <E969EBF3CCF7D01195560000F804A52F041DFEA1@emss04m05.ems.lmco.com>

I upgraded from egcs 1.1.2 to gcc 2.95.2 and I have the following
linking error:

//usr/local/bin//g++ -shared file1.o file2o file3.o file4.o file5.o
file6.o   -o /tmp/mystuff/lib/libmylib.so -lnsl -lsocket  -lpthread
-lposix4
Text relocation remains                  referenced
    against symbol      offset in file
<unknown>                           0xf28
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0x44
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0x48
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

<unknown>                           0xf14
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.2/libstdc++.a(iostream.o)

The above continues for several pages worth of errors.  egcs 1.1.2
compiled and link flawlessly and gcc 2.95.2 compiles flawlessly, but it
fails to link.  Has anyone seen this before (please say yes, I hate
being the only one), and more important is there a fix?

Wendell Beckwith





  reply	other threads:[~1999-10-29 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-29  6:14 Linker question Barrera, Antonio
1999-10-29 11:43 ` Wendell Beckwith [this message]
1999-10-31 13:57   ` Help! Solaris 7/gcc 2.95.1 shared lib link error Wendell Beckwith
1999-10-31 13:57 ` Linker question Barrera, Antonio

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=3819EB01.DE002996@directlink.net \
    --to=wbeckwith@directlink.net \
    --cc=egcs@cygnus.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).