• 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 14
Linux HOW-TO compile XBMC from a GIT source
#76
Don't know if it's related, but got the following error when trying

aptitude update -y

W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 632D16BB0C713DA6

So maybe there lies the cause. Anyhow I fixed this using the following commands:
Code:
gpg --keyserver keyserver.ubuntu.com --recv 632D16BB0C713DA6
gpg --export --armor 632D16BB0C713DA6| sudo apt-key add -

Which seems that an upgrade can now occur. Hope this will fix my build problem.

Don't know if this is OK, but the following error I got while upgrading:
Code:
dpkg: dependency problems prevent configuration of xbmc-standalone:
xbmc-standalone depends on xbmc-data (= 2:11.0~git20110622.d849637-0ubuntu1~ppa1~karmic); however:
  Version of xbmc-data on system is 1:9.11-karmic1.
dpkg: error processing xbmc-standalone (--configure):
dependency problems - leaving unconfigured
Setting up libsgutils2-2 (1.27-0.1) ...

Setting up libatasmart4 (0.16-1) ...

dpkg: dependency problems prevent configuration of xbmc-skin-confluence:
xbmc-skin-confluence depends on xbmc-data (= 2:11.0~git20110622.d849637-0ubuntu1~ppa1~karmic); however:
  Version of xbmc-data on system is 1:9.11-karmic1.
dpkg: error processing xbmc-skin-confluence (--configure):
dependency problems - leaving unconfigured
Setting up linux-headers-2.6.31-23 (2.6.31-23.75) ...
Setting up linux-headers-2.6.31-23-generic (2.6.31-23.75) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms

dpkg: dependency problems prevent configuration of xbmc:
xbmc depends on xbmc-data (= 2:11.0~git20110622.d849637-0ubuntu1~ppa1~karmic); however:
  Version of xbmc-data on system is 1:9.11-karmic1.
xbmc depends on xbmc-skin-confluence (= 2:11.0~git20110622.d849637-0ubuntu1~ppa1~karmic); however:
  Package xbmc-skin-confluence is not configured yet.
dpkg: error processing xbmc (--configure):
dependency problems - leaving unconfigured
Setting up libpolkit-backend-1-0 (0.94-1ubuntu1.1) ...

dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic (= 2.6.31.23.36); however:
  Package linux-image-generic is not configured yet.
dpkg: error processing linux-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of xbmc-live:
xbmc-live depends on xbmc-standalone (= 2:11.0~git20110622.d849637-0ubuntu1~ppa1~karmic); however:
  Package xbmc-standalone is not configured yet.
dpkg: error processing xbmc-live (--configure):
dependency problems - leaving unconfigured
Reply
#77
Lightbulb 
nims Wrote:There is a typo in your script:

libmodplug-devlibboost-thread-dev

Is not something I can install.

libmodplug-dev and libboost-thread-dev, though can be installed.

There is no typo anywhere I can assure you of that, I triple double triple checked it... if you gt the script from here should be 100%

nims Wrote:I've installed libboost-thread-dev, but somehow I cannot compile:

checking for main in -lboost_thread... no
configure: error: Could not find a required library. Please see the README for your platform.

I have no clue why it cannot build. Any clues here?

p.s. I've copied a paste-bin with my build progress here:

http://pastebin.com/cnkaKjwG

what version libboost-thread-dev did you install? I'm on lucid minimal and compiled ok, any distro lower than that will prolly require a backport or compile from source or if your anything that has a lib lower then 1.4...

Ill leave the instructions on how to compile libboost from source http://www.boost.org/doc/libs/1_46_1/mor...iants.html

prefix used is =/usr

you can get the source package from their website.

Failing that go on freenode IRC #XBMC-Linux...

nims Wrote:Don't know if it's related, but got the following error when trying

aptitude update -y

W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 632D16BB0C713DA6

snip
snip
snip

ok having read your last shotgun post all I can say is read my post on my blog here for failed xbmc packages

http://x3webworx.wordpress.com/2011/03/0...nd-beyond/

read under the update 15th May for the commands to run.... its fairly straight forward. for failed xbmc-packages.... as for libbost if your on karmic my guess is you need a compile from source since I do believe there is a minimum required version, dost ask me which...

I haven't compiled backports yet and not sure if its worth it.

can you please double check your stuff before posting? its hard work keeping up with you eh... :p
Reply
#78
X3lectric Wrote:There is no typo anywhere I can assure you of that, I triple double triple checked it... if you gt the script from here should be 100%
Well check it again Wink on page one of your installation you can see the line:
aptitude install ccache libyajl-dev libvdpau-dev debhelper zip git-core make g++ gcc gawk pmount libtool yasm nasm automake cmake gperf gettext unzip bison libsdl-dev libsdl-image1.2-dev libsdl-gfx1.2-dev libsdl-mixer1.2-dev libfribidi-dev liblzo2-dev libfreetype6-dev libsqlite3-dev libogg-dev libasound-dev python-sqlite libglew-dev libcurl3 libcurl4-openssl-dev x11proto-xinerama-dev libxinerama-dev libxrandr-dev libxrender-dev libmad0-dev libogg-dev libvorbisenc2 libsmbclient-dev libmysqlclient-dev libpcre3-dev libdbus-1-dev libhal-dev libhal-storage-dev libjasper-dev libfontconfig-dev libbz2-dev libboost-dev libfaac-dev libenca-dev libxt-dev libxtst-dev libxmu-dev libpng-dev libjpeg-dev libpulse-dev mesa-utils libcdio-dev libsamplerate-dev libmms-dev libmpeg3-dev libfaad-dev libflac-dev libiso9660-dev libass-dev libssl-dev fp-compiler gdc libwavpack-dev libmpeg2-4-dev libmicrohttpd-dev libmodplug-devlibboost-thread-dev -y -q
which is missing a space. Whilst on the version from your link:
it says:
aptitude install ccache libyajl-dev libvdpau-dev debhelper zip git-core make g++ gcc gawk pmount libtool yasm nasm automake cmake gperf gettext unzip bison libboost-thread-dev libsdl-dev libsdl-image1.2-dev libsdl-gfx1.2-dev libsdl-mixer1.2-dev libfribidi-dev liblzo2-dev libfreetype6-dev libsqlite3-dev libogg-dev libasound-dev python-sqlite libglew-dev libcurl3 libcurl4-openssl-dev x11proto-xinerama-dev libxinerama-dev libxrandr-dev libxrender-dev libmad0-dev libogg-dev libvorbisenc2 libsmbclient-dev libmysqlclient-dev libpcre3-dev libdbus-1-dev libhal-dev libhal-storage-dev libjasper-dev libfontconfig-dev libbz2-dev libboost-dev libfaac-dev libenca-dev libxt-dev libxtst-dev libxmu-dev libpng-dev libjpeg-dev libpulse-dev mesa-utils libcdio-dev libsamplerate-dev libmms-dev libmpeg3-dev libfaad-dev libflac-dev libiso9660-dev libass-dev libssl-dev fp-compiler gdc libwavpack-dev libmpeg2-4-dev libmicrohttpd-dev libmodplug-dev -y -q

Which is actually correct. See my bold section.

X3lectric Wrote:what version libboost-thread-dev did you install? I'm on lucid minimal and compiled ok, any distro lower than that will prolly require a backport or compile from source or if your anything that has a lib lower then 1.4...
From aptitude I installed:
apt-get install libboost-thread1.40.0
X3lectric Wrote:Ill leave the instructions on how to compile libboost from source http://www.boost.org/doc/libs/1_46_1/mor...iants.html

prefix used is =/usr

you can get the source package from their website.

Failing that go on freenode IRC #XBMC-Linux...
Good idea, since it is 1_46 that is on your page.
X3lectric Wrote:ok having read your last shotgun post all I can say is read my post on my blog here for failed xbmc packages
Thanks! I feel like hammering my xmbc with a shotgun Wink. Which seems to fail.
X3lectric Wrote:http://x3webworx.wordpress.com/2011/03/0...nd-beyond/

read under the update 15th May for the commands to run.... its fairly straight forward. for failed xbmc-packages.... as for libbost if your on karmic my guess is you need a compile from source since I do believe there is a minimum required version, dost ask me which...
Yes I am on Karmic, and I think I need to upgrade it from source. Your link above will help me there.
X3lectric Wrote:I haven't compiled backports yet and not sure if its worth it.

can you please double check your stuff before posting? its hard work keeping up with you eh... :p
Sorry about dumping it here, but I always think it is helpfull to post here, so that Google knows what's up Wink. Also helps me keeping track of what I done.

Just to make sure if my source is ok, I removed the complete source, downloaded the update script again and am now building a new git. So I am trying that now, to see if it now builds. Let you know what my findings are Smile.
Reply
#79
Well, no Smile

checking for main in -lboost_thread... no


So try now building it from source.
Reply
#80
nims Wrote:There is a typo in your script:

libmodplug-devlibboost-thread-dev

Is not something I can install.

libmodplug-dev and libboost-thread-dev, though can be installed.

ok please double check your end... Script does not have a typo...

script is not manual compile instructions (script != manual compile)

the typo is on manual compile instructions, which has now been corrected. thx.

also please note

when you download the updated script that contains the updated dependencies, IF you run the <upgrade> option you will run into problems because the 1st part of script does not include a makedistclean this will result in failed compiles...

the correct procedure is to install the missing deps manually and use the <refresh> option, alternatively you need to manually run makedistclean on your system xbmc git directory before running <upgrade> option on script.

just in case your getting things crossed.... Wink

nims Wrote:Good idea, since it is 1_46 that is on your page.

What page? you mean my suggestion link?

nims Wrote:Sorry about dumping it here, but I always think it is helpfull to post here, so that Google knows what's up Wink. Also helps me keeping track of what I done.

Just to make sure if my source is ok, I removed the complete source, downloaded the update script again and am now building a new git. So I am trying that now, to see if it now builds. Let you know what my findings are Smile.

Sometimes its not a good thing... Most people don't read all posts in a thread (when treads are huge) even though they should (we all a bit guilty of that, including me). It also depends if you also include proper tags on your posts so forums search provides relevant results. idk...
Reply
#81
Yes finally it is compiling again Smile.

Indeed I meant your link to version 1.46 http://www.boost.org/doc/libs/1_46_1/mor...iants.html did the trick. Thanks for your help! And also thanks for fixing the manual script on the first page Wink.

For the people who want to install this too but don't know linux so much here are the commands:
Code:
mkdir /setups
cd /setups
wget http://sourceforge.net/projects/boost/files/boost/1.46.1/boost_1_46_1.tar.gz/download
mv download boost_1_46_1.tar.gz
tar -xvzf boost_1_46_1.tar.gz
cd boost_1_46_1
./bootstrap.sh -prefix=/usr
./bjam install --prefix=/usr

Happy compiling Wink.

p.s. Maybe I need to upgrade my box to lucid, but I am not so fond of updating to a new version. What you think?
Reply
#82
you mean upgrading from karmic to lucid? Not a good idea generally... Fresh install ya.
Reply
#83
Trying to avoid a fresh install as long as possible Wink.
Reply
#84
well all depends on a lot of things for e.g xbmc now depends on python greater than 2.4, Im also updating script to do a git clean --force which will remove all old crap that cannot be used or compiled like xbmc/lib/addons/script.module.pysqlite

The script will now compile with nfs support by default
The script will compile xbmc/lib/addons/script.module.pil by default

and a couple of changes to main post especially bluray support which remains optional compile support. Other minor changes.
Reply
#85
All updates to main topic both manual compile instructions ***updates sections and script have been done new script was uploaded a minute ago to dropbox.

I checked as best as I could to ensure there's no typos anywhere if anything needs correcting or you can suggest improvements lemme know.

http://ppa.launchpad.net/team-xbmc/unstable/ubuntu

replaced

http://ppa.launchpad.net/team-xbmc-svn/ppa/ubuntu (this one has not existed for a while now)

similarly

add-apt-repository ppa:team-xbmc-svn/ppa wont work and result in keyserver error on imports and also failures in build-dep xbmc.

People downloading script and using it for first time from today onwards should get a working

apt-get build-dep xbmc -y

Those dependencies are only to build binaries like in ppas and only affects Ubuntu users other distros are unaffected by this.

The main post has reached around 10K characters which is max allowed in forums, I've shuffled and trimmed as much as possible. My blog will takeover at some stage cause of limitations of forums.

thx
Reply
#86
Well actually I wasn't able to maintain the old version very long Smile. After the compile was sucessfully, xbmc wouldn't run anymore on my box. Also the autostarts where gone, so probably the upgrade failed or broken something. So just downloaded the new live version, formatted my disk, and did a fresh install. So now I am trying your new and improved script Smile. So if I run into anything you are the first to hear.
Reply
#87
A second compile will fix it straight up, its happened to me numerous times... Compiling xbmc again fixed whatever went "wrong", you're way too rash... Perhaps the failure only served as an excuse for what you been "wanting" to do for longer then you care to admit eh?
Reply
#88
Who knows Smile. Anyhow, I am now on a "supported"-version Wink.

Which means I will ask direct a question, because my build failed using the script from your dropbox:

configure: error:
Could not link test program to Python. Maybe the main Python library has been
installed in some non-standard library path. If so, pass it to configure,
via the LDFLAGS environment variable.
Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
============================================================================
ERROR!
You probably have to install the development version of the Python package
for your distribution. The exact name of this package varies among them.
============================================================================

See `config.log' for more details.
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
Reply
#89
Well actually, I suspect this to causing the problem:

"apt-get build-dep xbmc -y" seems not to be executed correctly in the script, because now I run it manually on my box from the shell, and the following was done:

The following packages will be REMOVED:
libcurl4-openssl-dev
The following NEW packages will be installed:
libavcodec-dev libavcodec52 libavformat-dev libavformat52 libavutil-dev libavutil49 libbluetooth-dev libbluetooth3 libcrystalhd-dev libcrystalhd3
libcurl4-gnutls-dev libcwiid-dev libcwiid1 libcwiid1-dev libgcrypt11-dev libgnutls-dev libgpg-error-dev libgsm1 libmpcdec-dev libmpcdec3 liboil0.3
libpostproc-dev libpostproc51 librtmp-dev libschroedinger-1.0-0 libspeex1 libswscale-dev libswscale0 libtasn1-3-dev libtheora0 python-dev python2.6-dev
The following packages will be upgraded:
libcurl3-gnutls
1 upgraded, 32 newly installed, 1 to remove and 56 not upgraded.


So it seems that the script in <upgrade> mode does not properly update, and goes straight into building.
Reply
#90
nims; Wrote:Which means I will ask direct a question, because my build failed using the script from your dropbox:

What direct question is that? I saw no question at all, so Im presuming you made some mistake.

So let me ask you a rhetorical question... How do I know you are not responsible for these errors knowingly or otherwise?

Also looking at your post after
nims Wrote:1 upgraded, 32 newly installed, 1 to remove and 56 not upgraded.

56 not upgraded?

like I said to you before, double check your stuff... Your posts don't make it very easy, tbh.

I cant do anything about that, scripts run each command one after another, its well beyond my control what happens with each user.

TBH your the first person and only person to complain about this, none of the alterations I made to script affect that, so idk...

If you have a better way to do it, that is 100% foolproof for everyone, please go ahead, more hands make light work.

cheers and thx
Reply
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 14

Logout Mark Read Team Forum Stats Members Help
HOW-TO compile XBMC from a GIT source12