Re: Linker warnings

New Message Reply Date view Thread view Subject view Author view

Jenny Zhao (zhz++at++dandan.asd.sgi.com)
Tue, 16 Jul 1996 10:34:42 -0700


On Jul 16, 12:58pm, Gan Wang wrote:
> Subject: Linker warnings
> Hi there,
>
> I asked a similar question a few days ago but did not receive any responses.
> So I will ask again here.
>
> I am working with Performer 2.1 under 6.2. The following warnings are echoed
> every time linking is invoked:
>
> ld: WARNING 84: /usr/lib/libpfdu_ogl.so is not used for resolving any symbol.
> ld: WARNING 85: definition of getData__8pfMemoryCFv in /usr/lib/libpf_ogl.so
> preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of isOfType__8pfMemoryFP6pfType in
> /usr/lib/libpf_ogl.so preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of isExactType__8pfMemoryFP6pfType in
> /usr/lib/libpf_ogl.so preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of __as__8pfMemoryFPC8pfMemory in
> /usr/lib/libpf_ogl.so preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of getRef__8pfMemoryFv in /usr/lib/libpf_ogl.so
> preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of getGLHandle__8pfObjectCFv in
> /usr/lib/libpf_ogl.so preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 85: definition of getUserData__8pfObjectFv in
/usr/lib/libpf_ogl.so
> preempts that definition in /usr/lib/libpfui.so.
> ld: WARNING 84: /usr/lib/libpfui.so is not used for resolving any symbol.
> ld: WARNING 84: /usr/lib/libmpc.a is not used for resolving any symbol.
> ld: WARNING 84: /usr/lib/libGLw.a is not used for resolving any symbol.
> ld: WARNING 84: /usr/lib/libXm.so is not used for resolving any symbol.
> ld: WARNING 85: definition of _calloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of _cfree in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of cfree in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of __checktraps in /usr/lib/libfpe.so preempts
that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of __readenv_sigfpe in /usr/lib/libfpe.so preempts
> that definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of _malloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of _realloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of _free in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of calloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of memalign in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of malloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of realloc in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
> ld: WARNING 85: definition of free in /usr/lib/libmalloc.so preempts that
> definition in /usr/lib/libc.so.
>
> I don't understand the environment very well. But I am reluctant to turn off
> the warnings because I rely on them to find my own conflicts and potential
> errors.
>
> Any help from you would be greatly appreciated.
>
> Thanks,
> Gan
>
> --

these warnings are expected. and we understand it is not helpful at all
to leave these warnings there because they may hide the real warnings.
we will resolve them in the next release.

sorry about that.

-- 
Jenny Zhao                                   
zhz++at++asd.sgi.com                    
415 933-5091 (Voice)           
415 965-2658 (Fax)         
Silicon Graphics - IRIS Performer      

======================================================================= List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:11 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.