linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "ian reinhart geiser (ADMIN)" <geiseri@msoe.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Unresolved symbols....
Date: Thu, 22 Jul 1999 13:15:59 -0400	[thread overview]
Message-ID: <19990722131559.A4092@drow.res.cmu.edu> (raw)
In-Reply-To: <Pine.OSF.3.96.990722115246.30323A-100000@torres.msoe.edu>; from ian reinhart geiser (ADMIN) on Thu, Jul 22, 1999 at 11:54:54AM -0500


On Thu, Jul 22, 1999 at 11:54:54AM -0500, ian reinhart geiser (ADMIN) wrote:
> 
> i am compileing the postgres ODBC drivers and i get the following
> error on linking:
> 
> ld -Bdynamic -shared -soname libpsqlodbc.so.0.25 -Bsymbolic -lc -lm -o
> libpsqlod
> bc.so.0.25 info.o bind.o columninfo.o connection.o convert.o drvconn.o
> environ.o
>  execute.o lobj.o misc.o options.o pgtypes.o psqlodbc.o qresult.o
> results.o sock
> et.o parse.o statement.o gpps.o tuple.o tuplelist.o dlg_specific.o   -lc

I'm not so sure that you want -Bsymbolic.  Plus, using ld for linking
is rarely a good idea; you should always use gcc.

> /lib/libc.so.6: undefined reference to `_r_debug@@GLIBC_2.0'
> /lib/libc.so.6: undefined reference to `_dl_unload_cache@@GLIBC_2.1'

All of these are symbols from the dynamic linker.  That they aren't
being found implies mislinking.


Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-07-22 17:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-19 13:39 Is the vger 2.2 kernel branch dead VALETTE Eric
1999-07-19 20:39 ` Matt Porter
1999-07-19 21:07   ` Hartmut Koptein
1999-07-19 21:41     ` cdrecord (Re: Is the vger 2.2 kernel branch dead) Brad Midgley
1999-07-19 21:52   ` Is the vger 2.2 kernel branch dead Johnnie Peters
1999-07-19 22:47     ` Tom Rini
1999-07-20 17:40       ` Neil Piercy
1999-07-20 17:56         ` Tom Rini
1999-07-20 19:46           ` Martin Costabel
1999-07-21 16:20     ` Matt Porter
1999-07-21 19:47       ` Johnnie Peters
1999-07-22  7:57       ` VALETTE Eric
1999-07-22  8:14         ` Geert Uytterhoeven
1999-07-22  8:41           ` VALETTE Eric
1999-07-22 15:01             ` Matt Porter
1999-07-22 15:53               ` VALETTE Eric
1999-07-22 16:54                 ` Unresolved symbols ian reinhart geiser (ADMIN)
1999-07-22 17:15                   ` Daniel Jacobowitz [this message]
1999-07-22 17:23                     ` ian reinhart geiser (ADMIN)
1999-07-24  8:46                   ` Franz Sirl
1999-07-23  2:41             ` Is the vger 2.2 kernel branch dead Paul Mackerras
1999-07-23  7:48               ` VALETTE Eric
1999-07-20  7:57   ` VALETTE Eric

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=19990722131559.A4092@drow.res.cmu.edu \
    --to=drow@false.org \
    --cc=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).