Date: Mon, 13 Mar 2006 09:17:16 +0100 From: "Svein Halvor Halvorsen" <svein.h@lvor.halvorsen.cc> To: "Chris Maness" <chris@chrismaness.com> Cc: freebsd-questions@freebsd.org Subject: Re: dvd-slideshow Message-ID: <bbe90d1d0603130017l369f71f8s9fbb78d214da5b43@mail.gmail.com> In-Reply-To: <4414A03E.8080504@chrismaness.com> References: <4414A03E.8080504@chrismaness.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/12/06, Chris Maness <chris@chrismaness.com> wrote: > I would like to see if others are getting similar errors with > dvd-slideshow. If you have the current ports tree, try to install and > run dvd-slideshow. The ports tree has version 7.2. When I try to run > the script, I get error messages like crazy. Anyone else get this? I > used the example files to try to get it to work. If I simply download > the latest version from sourceforge and run the script in the directory > it seems to MUCH further, but still fails. > > sample output: > > package sox is not installed > package ImageMagick is not installed > package dvdauthor is not installed > package ffmpeg is not installed > find: /usr/share/fonts/: No such file or directory > find: /usr/share/fonts/: No such file or directory : > [dvd-slideshow] ####wc: illegal option -- - : > /usr/local/bin/dvd-slideshow: line 2388: seq: command not found > wc: illegal option -- - Looks like this script is expecting to find the GNU util, and that they be installed in the usual GNU locations. On FreeBSD GNU wc is installed as gwc (from ports). > /usr/local/bin/dvd-slideshow: line 986: [: : integer expression expected > /usr/local/bin/dvd-slideshow: line 989: [: : integer expression expected > /usr/local/bin/dvd-slideshow: line 992: [: : integer expression expected > /usr/local/bin/dvd-slideshow: line 995: [: : integer expression expected These I don't know. But it might be that the interpreter is set to /bin/sh, which on Linux is aqtually /bin/bash. I don't know, however. > No such file or directory : > [dvd-slideshow] No audio files passed. Using silence. : > sox: Can't open output file : > Error while opening file These are probably because of some of the other errors. I think you are far beter off trying to get the port to run on your FreeBSD system, that to try to fix all these things yourself.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bbe90d1d0603130017l369f71f8s9fbb78d214da5b43>