my prob seems to be only a format issue, conclusion contradicted by
http://www.citlink.net/~messengertj/htmlhelp.htm

not a reply to my issue, but something to be aware, possibly related
,
a zoom scope on the tech

There are several things that you need to realize here.  First, ELF and
PE work quite differently, specifically ELF has the ability to link a
library or program with undefined symbols that are lazily resolved at
program runtime by the runtime dynamic linker ld.so.  You can't do this
on PE systems, which require that all symbols be resolvable at link
time.

Completely separate from those architectural design differences, libtool
also has a -no-undefined flag with a somewhat overloaded meaning.  On
platforms like PE where undefined symbols cause a link failure, libtool
requires that you specify -no-undefined if you want to build a shared
library.  Doing this tells libtool "yes, this library was designed to
work this way, so it's okay to try to create a shared library."
Otherwise it won't even try.  You can normally just add this flag to
foo_la_LDFLAGS and things will work fine -- assuming of course that the
package itself was not designed to rely on this ELF ability to do lazy
binding.  In that case you'll have more work to do.

(ELF is an acronym for Executable and Linking Format) is a standard for object
modules, libraries, executables, and core files.

PE-COFF the "P" stands for "portable" (Microsoft's PE-COFF was another standard
they documented.)

Standards and specs: An unsung hero: The hardworking ELF
http://www.ibm.com/developerworks/power/library/pa-spec12/index.html

Post a reply to this message