Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.unix.i386
Subject: Re: Linking Problems with SCO-ODT (Was: Compiling g++ under SCO)
Keywords: g++ SCO Unix
Message-ID: <1306@lupine.NCD.COM>
Date: 23 Aug 90 06:29:08 GMT
References: <20423@saleven.oz> <348@stephsf.stephsf.com>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 30

In article <348@stephsf.stephsf.com> wengland@stephsf.stephsf.com (Bill England) writes:
>In article <20423@saleven.oz> mykel@saleven.saleven.oz.au (Michael Landers) writes:
>>
>>
>>groff, actually) I get problems with multiply defined symbols...
...
>   I've similar problems when compiling and linking software.  For instance
>   I can not get ld to properly link items that contain ingres functions 
>   without getting multiple defines...

In case my prior message didn't make it out, let me say again that I believe
that this problem is rooted in ld++ (which gets installed as gcc-ld).
Unfortunately, I have not yet had sufficient time to isolate this problem
and to *prove* that the problem is being caused by ld++.  So this ought
still be be considered simply an informed conjecture at this point.

If this problem is really getting you down, you might try an experiment to
help isolate this problem.  Try linking the same set of .o files and libraries
with your native system linker.  You should be able to do this simply by
temporarily renaming your installed gcc-ld file to gcc-ld.save or something
and then using g++ to invoke the linker (as you normally would).  Use the
-v option so that you can see exactly which linker gets invoked.  If your
native linker gets invoked, and if the `multiply defined' errors go away
then we know that the bug is in ld++.  If you do this experiment, please
post the results here.
-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.