Re: unresolved symbol & __nw__....

tim wrote:
: I'm still unsatisfied with what the dynamic loader is doing. Is there
: anyway to determine how/why it believes certain symbols are needed?

If there is an unsat for a symbol in an aC++ shared lib, it must be
satisfied, if its address is taken.

: I've tried looking with nm at the symbols as they occur in the library
: and there are only 2 places. One where the ctors and dtors are
: located, and another in an entry of unsat symbols.

nm(1) is the wrong tool to look at PA32 shared libs.
Use "/usr/ccs/bin/odump -slimport -slexport" instead.
If you have both definitions and uses for the symbol, I don't see why you
should have a problem??

: So I'm confused why the dld doesn't simply mark these symbols as
: unreachable and continue?

It doesn't know they are unreachable. Advanced AI technology is needed to
determine this.

: According to the linker and libraries user
: guide on the PA 32 system this is how it is suppose to work (page 181).

I assume it is this one?
Resolution of Unsatisfied Shared Library References
http://docs.hp.com/en/B2355-90655/B2355-90655.pdf

aC++ is special and defeats Smartbind. And it isn't available for PA64 or
IPF.

: NOTE: I will cross post this question to HPUX-DEVTOOLS because it is
: more related to the linker and symbol resolution than C++ specific
: tim

Probably not really, it is aC++ specific.
.

Relevant Pages

  • Re: AIX shared libraries and lazyloading.
    ... then it's dependents are examined in the same ... 0xD/0xF are shared lib segs. ... > I used that when building main and also all libraries. ...
    (comp.unix.aix)
  • Re: any problem building both static and shared tcl libs for 8.4.6
    ... Tim wrote: ... I regularly build and install both types of libraries on my Linux box ...
    (comp.lang.tcl)
  • Re: Upgrading to 7.0 - stupid requirements
    ... e.g. a shared library used by other ports. ... If prior to any recompile such a shared lib was copied ... Tools like portupgrade do save copies of old libraries in /usr/local/lib/compat (which helps in other upgrade scenarios), but it doesn't help in the OS upgrade case because the old and new shared port libraries have the same version and cannot be distinguished automatically by the linker. ...
    (freebsd-stable)
  • Re: WORST CASE SCENARIO
    ... Tim K. wrote: ... libraries and laboratories of our local world class univerities and ...
    (sci.physics)
  • Re: maximize JInternalFrame
    ... you could use different LAF... ... libraries for LAF, forms and animation. ... "Tim" wrote in message ... > also interesting when creating an MDI application, helas doesn't help me ...
    (comp.lang.java.gui)