The only reference in libDX.a to _dxfHWload is as an unresolved reference.
(a "U" flag from nm).
In libDXcallm.a, nm finds _dxfHWload twice: with a U and with a T flag. I
think the T flag means that it found the actual code.
Some changes were needed for a successful compile under True64; could we
have somehow pushed _dxfHWload into the wrong archive?
Thanks!
Kent
I--On September 11, 2003 03:38:32 PM <[EMAIL PROTECTED]> wrote:
When I look at how this is being built, everything looks okay. Can you nm
libDX.a and see if for some reason it doesn't exist in that lib?
nm libDX.a |grep dxfHWload
You may also try rebuilding the lib and see if that solves the problem.
David
_dxfHWload is returned as an unresolved reference when linking only
to libDX.a for DX 4.3.3 on aTrue64 (alpha) system. However, it
works. Adding libDXcallm.a to the link resolves the reference but
adds many "multiply defined" references; and the resulting shared
object does not work. Neither result seems good. Suggestions?
Kent
