This is regarding my posting last night regarding linkage problems
when linking programs against a library which was built, in part, from
a convenience library.

There is a grevious error in my description of the problem.  Rather
than conflicting symbols, the current problem is that there are
unresolved symbols.  These unresolved symbols only occur due to a
static library (built using libtool and called libttf.a) which is
linked as a dependency when the target library (libMagick) is created.  
Therefore, it seems that CVS libtool's dependency support is not
applying this dependency library when programs are built against the
target library (libMagick). Symbols from the other static libraries
(which were not built using libtool) do not show up as unresolved.

Pictorially:

 convenience  libttf.la  other static
     lib       (static)     libs
      \           |         /
       \          |        /
        \         |       /
         \        |      /
          \       |     /
           \      |    /
            \     |   /
             \    |  /
              \   | /
             libMagick.so
                  |
                  |
               program

   Symbols from libttf.la are unresolved.

Is there a workaround for this?  I would prefer for libtool to take
care of this rather than attempting to guess which libraries are
static or shared libs, and applying them at different points in the
build cycle.  These other libraries are from other packages than my
own.

Thanks,

Bob
======================================
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen

Reply via email to