Do you know if inter library dependencies are supported on your platform
(eg. If you link to libXt will it automatically link your app to libX11
for instance?).
Another thing to try would be to download the latest version of libtool
and install that on your system. Then from the base directory of dia, run
"libtoolize --force". If things still don't build correctly, you could
try helping the libtool people fix the problem in libtool.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Sun, 27 Feb 2000, Scott Presnell wrote:
> /bin/sh ../../libtool --mode=link gcc -g -O2 -o libuml_objects.la
> -rpath /usr/local/lib/dia -export-dynamic -module -avoid-version uml.lo
> class.lo class_dialog.lo note.lo actor.lo usecase.lo realizes.lo
> constraint.lo small_package.lo large_package.lo implements.lo
> generalization.lo association.lo dependency.lo message.lo object.lo
> lifeline.lo component.lo classicon.lo state.lo -L/usr/local/lib
> -L/usr/X11R6/lib -lgtk -lgdk -lgmodule -lglib -lXext -lX11 -lm
> mkdir .libs
>
> *** Warning: inter-library dependencies are not known to be supported.
> *** All declared inter-library dependencies are being dropped.
>
> *** Warning: libtool could not satisfy all declared inter-library
> *** dependencies of module libuml_objects. Therefore, libtool will
> create
> *** a static module, that should work as long as the dlopening
> *** application is linked with the -dlopen flag.
> ar cru .libs/libuml_objects.a uml.lo class.lo class_dialog.lo note.lo
> actor.lo usecase.lo realizes.lo constraint.lo small_package.lo
> large_package.lo implements.lo generalization.lo association.lo
> dependency.lo message.lo object.lo lifeline.lo component.lo classicon.lo
> state.lo
> ranlib .libs/libuml_objects.a
> creating libuml_objects.la
>
