On Sun, 27 Feb 2000, Scott Presnell wrote:

> Alexander Larsson wrote:
> > 
> > On Sat, 26 Feb 2000, Scott Presnell wrote:
> > 
> > >
> > >
> > >       Hi,
> > >               I've also been trying to run dia under NetBSD
> > >       and got the same:
> > >
> > >       > "Couldn't find standard object when looking for object lib..."
> > >
> > >       message (the so files are named .so.0.0). So I made links to them
> > >       with just .so and also tried renaming the file.
> > >
> > >       When I start dia I get a seg fault.  Here's the stack trace...
> > >       Any suggestions about where to go from here?
> > >
> > 
> >  Report it at bugs.gnome.org as a bug in the glib package.
> 
> Thanks, I also found a fix for the problem and reported on it.
> See gtk bug ticket #6660.
> 
> However I've run into another (the next) problem: when building
> some of the object libraries libtool barfs and skips building the
> shared object in favor of a static library.  See below for an example
> for uml.
> 
> Correctly built:
> libflowchart_objects.so*  libstandard_objects.so*
> libnetwork_objects.so*    libsybase_objects.so*
> 
> Incorrectly built:
> liber_objects.a     libfs_objects.a     libuml_objects.a
> 
> IMHO, debugging dlsym() problems is a piece of cake compared to
> understanding libtool. :-(
> 
> Can someone give me a clue on how I should go about addressing this?
> 
> Is it related to the fact that the .so's are built with .0.0 version
> numbers under NetBSD?
> 
>       Thanks for any help.
> 
>       - Scott
> 
> 
> /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

I've seen this problem before. It is due to not having inter-library
dependencies in some OS'es. Linux has this, but it is actually not
needed. The warning is triggered because some of the object libraries link
with Gtk+. This is not needed.
Stuff like:
libuml_objects_la_LIBADD = @GTK_LIBS@
In object/UML/Makefile.am should be removed.

I'm cleaning this in CVS now.

/ Alex


Reply via email to