Menu

Building Fuppes Error

Help
adamp99
2010-11-02
2013-04-25
  • adamp99

    adamp99 - 2010-11-02

    I'm trying to build using the following script:

    # Contributor: Canute

    pkgname=fuppes
    pkgver=595
    pkgrel=1
    pkgdesc="FUPPES is a free multiplatform UPnP (TM) A/V Media Server."
    depends=('ffmpeg' 'pcre' 'libxml2' 'sqlite3' 'taglib')
    makedepends=('subversion' 'libtool' 'autoconf' 'automake' 'pkgconfig')
    arch=(i686)
    conflicts=()
    provides=('fuppes')
    replaces=()
    url="http://fuppes.ulrich-voelkel.de/"
    license="GPL"
    source=()
    md5sums=()

    _svntrunk=http://fuppes-svn.ulrich-voelkel.de/trunk
    _svnmod=fuppes

    build() {
            cd $startdir/src
            svn co $_svntrunk/ $_svnmod -config-dir ./
            cp -r $_svnmod $_svnmod-build
            cd $_svnmod-build
            autoreconf -vfi
            ./configure -prefix=/usr -enable-video-transcoding
            make -j 2 || return 1
            mkdir -p $startdir/pkg/usr/{bin,include,lib} || return 1
            make DESTDIR=$startdir/pkg install || return 1
    }

    However, I cannot resolve http://fuppes-svn.ulrich-voelkel.de/trunk. I don't seem to be able to resolve this on my PC either.

    Any advice? Is the site down?

     
  • Robert Massaioli

    Yeah, where you are now, sourceforge, is where the link should be pointing to really. So https://fuppes.svn.sourceforge.net/svnroot/fuppes/trunk is what that url should be. I would also not be surprised if the configure stages failed as well; the script looks like it might need more updating and at the bare minimum the version number should be upgraded to the revision number that the svn trunk is upto. Let me know how it goes though when you just change the build numbers and the svn trunk url.

     
  • adamp99

    adamp99 - 2010-11-14

    Thanks Robert.

    Changing the build number & url did work but I then ended up with further errors. Being very new to Linux I decided to install MiniDLNA  which already had a package available.

     

Log in to post a comment.