Re: cryptic libtool error message

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Tue Jan 26 1999 - 23:37:05 EST


>
> Yes, the actual dependencies will be the ones listed in the libtool
> command line.

What if only some of them are unresolved, but others are not?
For instance, if I create libfoo with -lbar and -lbaz, but only
-lbaz could not be found, how will it tell me?

>
> It only does that for convenience libraries, and then, it does it for
> both shared and static libraries. object modules of inconvenience :-)
> libraries are never copied into another library (except when libtool
> is allowed to pass static libraries in the link command line of a
> shared library and the shared library linker copies some of its object
> modules into the shared library on its own)
>

Alright. I'll stop complaining. I think my point is made.

Read your last sentence back to you and then maybe you can see why
I think that libtool is a typical example for a tool that tries
to fight complexity with even more conventions, rules, and options.

        - Godmar


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:49 EDT