This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: undefined symbols in shared libraries
- From: Robert Schweikert <Robert dot Schweikert at abaqus dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: binutils <binutils at sources dot redhat dot com>,Robert Schweikert <rjschwei at abaqus dot com>
- Date: 11 Mar 2004 11:05:07 -0500
- Subject: Re: undefined symbols in shared libraries
- Organization: ABAQUS
- References: <1079017566.20460.146.camel@cheetah.hks.com> <m34qsvtlxi.fsf@redhat.com>
Nick,
That didn't do the trick either.
`_ZN23thr_ThreadSingletonBaseI18rgx_ReCompileCacheEC9Ev':
: warning: undefined reference to `thr_GlobalLock::Unlock()'
> echo $status
0
Thanks,
Robert
On Thu, 2004-03-11 at 10:58, Nick Clifton wrote:
> Hi Robert,
>
> > There appears to have been a change in behavior w.r.t. using -z
> > defs. At some point using -z defs caused the linker to exit with an
> > error if there were unresolved symbols in a shared library. We
> > recently upgraded to a new linker (needed the weak symbol handling
> > fix for performance reasons) and now we only get warnings when using
> > -z defs. I also tried --no-undefined just in case the long option
> > behaves differently, but it doesn't. I further tried the combination
> > of --no-undefined and --error-unresolved-symbols and that still
> > didn't help.
>
> Please try using:
>
> --no-allow-shlib-undefined
>
> Cheers
> Nick
>
--
Robert Schweikert <Robert.Schweikert@abaqus.com>
ABAQUS