>>>>> On Sat, 20 Mar 1999 19:46:19 -0500 (EST), Will Lowe <[EMAIL PROTECTED]> >>>>> said:
Will> Can anybody tell me what this means, and what to do about it? Will> W: rosegarden: shared-lib-without-dependency-information Will> usr/X11R6/lib/rosegarden/petal/Petal.so Will> E: rosegarden: shlib-with-non-pic-code Will> usr/X11R6/lib/rosegarden/petal/Petal.so First one: it means you have a shared library in your package without providing dependency information about it. In this case it shouldn't cause a problem because the shared object looks like it'll only be used by rosegarden. A little more info: when you link a program and do ldd on it you get back a list of libraries it loads at startup. If the packages that provide that library also provides a shlib file automated tools like dpkg-shlibs can figure out some of the dependency for the package (with versions). Second one: shared library objects are compiled in a special way (command line option -fPIC) so that they can be shared. The object it is complaining about includes code that can not be shared. This would be _very_ bad for something like libc, but since this looks like a single program shared object it shouldn't cause any troubles. The worst that happens in any case is that each process that uses this lib gets its own copy (so you can see how bad a thing having libc compiled this way would be :). HTH Dres -- @James LewisMoss <[EMAIL PROTECTED]> | Blessed Be! @ http://www.ioa.com/~dres | Linux is kewl! @"Argue for your limitations and sure enough, they're yours." Bach
