sysutils/libcdio provides no cdio_paranoia.0 for ports/devel/gvfs

[Koop Mast]

On Mon, 2009-11-16 at 10:51 +0100, Tılman Linneweh wrote:
> Hello Julian!
> 
> (CC: devel/gvfs maintainer added)
> 
> Thanks for reporting this issue. 
> 
> On Nov 15, 2009, at 22:51 , Julian H. Stacey wrote:
> > int would be welcome please with sysutils/libcdio, Paranoia stuff seems
> > broken, but I'm not clear what's intended, hence mail rather than a send-pr.
> > 
> > 	===>   gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > 	===>    Verifying install for cdio_paranoia.0 in \
> > 		/usr/ports/sysutils/libcdio
> > 	===>   Returning to build of gvfs-1.2.1
> > 	Error: shared library "cdio_paranoia.0" does not exist
> > /usr/ports/devel/gvfs ; make
> > 	===>   gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > 	===>    Verifying install for cdio_paranoia.0 in \
> > 		/usr/ports/sysutils/libcdio
> > 	===>   Returning to build of gvfs-1.2.1
> > 	Error: shared library "cdio_paranoia.0" does not exist
> 
> There are two easy possible solutions.
> a) make gvfs depend on libcdio.so instead of the non-default cdio_paranoia.0 library
> b) Change libcdio to install cdio_paranoia.0 by default. 
> 
> Question to gnome@ - Does gvfs really need the cdio_paranoia library, or is this just a bug
> in the port Makefile and it is ok with the libcdio library?

a) The configure script of the gvfs port checks for cdio_paranoia
library. It needs it for the cdda backend. 
b) libcdio already got a option for paranoia support and it is default
to on.

Julian you can do two things now. Either you disable the cdda backend in
gvfs with the WITH_CDDA option. Or build libcdio with paranoia support.

-Koop

> regards
> arved_______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>