On Tuesday 04 March 2008, Neil Williams wrote: > If there are missing symbols when linking against this library, that > info should be in the pkgconfig data, under Requires. Are there missing > symbols in your build?
There are problems with the .la file. That isn't at all related to pkgconfig - or well pkgconfig is the new && better way to do .la files. > I'm not the maintainer, I'm just reviewing the bug report as it still > seems to be unnecessarily severe and the report itself incomplete. The report is fully complete. There is a .la file in the -dev package. That .la file requires other .la files to work - thus you need to either remove the references to the other .la files or make sure they are provided. > > You must let your -dev package depend on > > all packages that are listed in dependency_libs there, otherwise it > > simply won't be possible to link to your library, no matter if it is > > really needed by the code or not (and it isn't here it seems). > > Not necessarily - the -dev depends on what is *exported* by the API. please read up on .la files. > > Well, the package that fails to build otherwise is gvfs (from > > experimental). > > Which depends on another package in experimental and which, therefore > is somewhat low on the list of things to get done before Lenny. The package is broken. it needs to be done before lenny. > So, again, why does this bug need to be severity: serious ??? The package is broken. This is the same as if your /usr/include/foo.h has a #include <bar.h> and bar.h comes from another package, you also need to depend on that other package. (or make the #include statement go away) /Sune - not a gphoto maintainer -- Genius, I'm not able to overclock the window, how does it work? The point is that you neither should get access over the SCSI connector, nor can ever disable the FPU over a front-side bus to a 6-bit ISDN provider in order to remove a monitor of the case.
signature.asc
Description: This is a digitally signed message part.
