[giaur]

Hello,

I want to to use xbmc to using tv with tvheadent pvr backend. My system is Debian Sid. There is xbmc in debian multimedia repository, but unfortunatelly, without pvr support. I've also tried to add some ubuntu repos and install xbmc, but installation seems to be impossible due to package conflicts.

So, I finally decided to compile xbmc by myself, with pvr support enabled. I was looking for tutorial how to do this and I found this: http://wiki.xbmc.org/index.php?title=HOW..._for_Linux - seems to be not very difficult, but I have some questions:
- is this tutorial applies to Debian too?
- after I compile as described there - will I have pvr tvheadend supoort enabled? If not - what exactly should I do to have pvr tvheadend enabled? I don't waste my time for compilation without pvr, bacause watching tv is what I want to use xbmc for.

Or, maybe there are debian packages/repo available and I can install full xbmc version from there on my debian system? As I wrote above, ubuntu repos are not suitable and impossible to use...

[darkscout]

1) Yes.

2) You need to download the pvr source, it's not in mainline yet.

[giaur]

Hello,

Where can I download pvr source from?

[darkscout]

https://github.com/opdenkamp/xbmc

Just follow the same procedure that you would as compiling for mainline. I run sid on everything in my house and compile my own XBMC, if you have multiple computers distcc makes easy work of it.

[giaur]

Hmm, no success still:

NFSDirectory.cpp: In member function ‘bool XFILE::CNFSDirectory::ResolveSymlink(const CStdString&, nfsdirent*, CURL&)’:
NFSDirectory.cpp:160:15: error: ‘struct nfsdirent’ has no member named ‘mode’
NFSDirectory.cpp:161:15: error: ‘struct nfsdirent’ has no member named ‘size’
NFSDirectory.cpp:162:15: error: ‘struct nfsdirent’ has no member named ‘atime’
NFSDirectory.cpp:163:15: error: ‘struct nfsdirent’ has no member named ‘mtime’
NFSDirectory.cpp:164:15: error: ‘struct nfsdirent’ has no member named ‘ctime’
NFSDirectory.cpp:167:69: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:168:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:169:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:170:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:171:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:172:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:173:74: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp: In member function ‘virtual bool XFILE::CNFSDirectory::GetDirectory(const CStdString&, CFileItemList&)’:
NFSDirectory.cpp:236:19: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:248:24: error: ‘struct nfsdirent’ has no member named ‘size’
NFSDirectory.cpp:249:25: error: ‘struct nfsdirent’ has no member named ‘type’
NFSDirectory.cpp:250:28: error: ‘struct nfsdirent’ has no member named ‘mtime’
NFSDirectory.cpp:257:32: error: ‘struct nfsdirent’ has no member named ‘ctime’
make[1]: *** [NFSDirectory.o] Błąd 1
make: *** [xbmc/filesystem/filesystem.a] Błąd 2

Some problems with libnfs version? So, what version I need to compile this? I'm trying to build xbmc downloaded today (lates snapshot) and I have linbnfs git20110724.48593f5-1

There is no newer libnfs-dev in Debian Sid and in Ubuntu. So what to do? Any suggestions?

[giaur]

Ok, compilation succesfull but there is another problem. I want to create .deb package using checkinstall but it fails:

tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Cyrillic): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Simple): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Traditional): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (US): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Devanagiri): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Devanagiri): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Brazil): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Cyrillic): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Cyrillic): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: (Mexico): Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Bubbles: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: Bubbles: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
OK

Stripping ELF binaries and libraries...OK

Compressing man pages...OK

Building file list...OK

Building Debian package... FAILED!

*** Failed to build the package

What's the problem?

[darkscout]

Since I just use it for personal use I don't bother with making a deb, you're going to have to talk on the Debian forums about that.

I would stick to the version of libnfs that he is using. PVR development lags behind the main because it's an entirely different branch.

https://github.com/opdenkamp/xbmc/blob/m...s/Makefile

Looks like he's using 0804e67. Check out xbmc-pvr and install all libraries based on that.

[giaur]

Hello,

I just wonder why checkinstall fails when creating xbmc .deb. I always use checkinstall and I it always works...
So, finally - I compiled xbmc with custom prefix (/xbmc) and I assume all xbmc files are located there.

I really don't like "make install", because there is no simple method to uninstall, without "make uninstall" in source directory. And uninstall is impossible without sources I compiled. I really don't like it.

About libnfs. Seems xbmc uses most recent libnfs version. So, I've simply downloaded latest source, compiled and installed (yes, checkinstall again and it worked) and everything is ok.

But still, there is a question: if anybody use checkinstall to install xbmc, please tell me how to do this correctly. Personally, I suspect some bugs in checkinstall, but maybe there is any workaround

[darkscout]

I just did a checkinstall on the main git and it worked fine.

[Jimmer]

But still, there is a question: if anybody use checkinstall to install xbmc, please tell me how to do this correctly. Personally, I suspect some bugs in checkinstall, but maybe there is any workaround

Code:

sudo checkinstall -y --fstrans=no --install=yes --pkgname=git-xbmc-tsp --pkgversion="`date +%Y%m%d`.`git rev-parse --short HEAD`"

is what I use. You'll have to change the pkgname to something that suits you, but since I switch branches I like to give them distinct names (I'm currently using tsp's branch). For clarity: I use this on Ubuntu and it works fine, but it should work the same on debian too. I use it on Maverick (using the latest 3.x series kernels) and also on an appletv 1 running Hardy. Different version number of checkinstall on each machine and no problems over many compilations. If it compiles, checkinstall will install it in my experience....

Jimmer

[giaur]

This is what I used (as root, sudo is not enabled by defult on Debian):

Code:

checkinstall -D --install=no

-D - create debian package
--install=no - not install, just write .deb

And then, all neccesary options like package name etc. was set by choosing menu entries. I'm not sure about meaning some options you provided in commandline but I'll try to use it to see if it works in my case.

Can you tell me what tar and checkinstall versions do you have? I found on google similar problems when creating some packages with checkinstall, but without clear solution.