Build SageTV (Linux Specific) + GitHub primer

[Taddeusz]

I tried building on 32-bit and got an error during the buildso phase. It appears that it's trying to target amd64 rather than the i386 Java that's installed. Using both the default-jre and default-jdk on Ununtu Server 15.04.

64-bit built but I was getting a core dump during channel scanning on my HDHR's.

[tmiranda]

Originally Posted by stuckless

Do you have a $JDK_HOME/include/ dir?

ls $JDK_HOME/include/

Also what is you JDK_HOME pointing to...

echo $JDK_HOME

If not, then you are likely only pointing a JRE and you'll need the full SDK.

Maybe I had that wrong? I tried it again and now it got farther. This time it failed building the shared libraries with an error saying it could not find -ljawt.

[Fuzzy]

Originally Posted by stuckless

Do you have a $JDK_HOME/include/ dir?

ls $JDK_HOME/include/

Also what is you JDK_HOME pointing to...

echo $JDK_HOME

If not, then you are likely only pointing a JRE and you'll need the full SDK.

HA! yeah.. I should know better than that. did a fresh linux VM for this, and somehow missed setting the pointer. So not used to having to do everything manually in linux.. ;-)

[Taddeusz]

Originally Posted by tmiranda

Maybe I had that wrong? I tried it again and now it got farther. This time it failed building the shared libraries with an error saying it could not find -ljawt.

Same error I was getting on 32-bit. Does the jre path show its trying to target amd64?

[stuckless]

Originally Posted by Taddeusz

Same error I was getting on 32-bit. Does the jre path show its trying to target amd64?

Yeah, as a general rule, if you are on a 64bit system then keep EVERYTHING (ie, Java) 64bit... don't mix and match.

[MrD]

To build 32 bit on a 64bit OS, you will need to install / setup / cross compile the native code.

[Taddeusz]

Originally Posted by stuckless

Yeah, as a general rule, if you are on a 64bit system then keep EVERYTHING (ie, Java) 64bit... don't mix and match.

I think you don't understand. I was on 32-bit Ubuntu with the 32-bit default-jre & default-jdk from the Ubuntu repository. During by the compilation of the so's it showed it was trying to target amd64 while it was running on 32-bit. I believe that's the reason for the compilation error.

[stuckless]

Originally Posted by Taddeusz

I think you don't understand. I was on 32-bit Ubuntu with the 32-bit default-jre & default-jdk from the Ubuntu repository. During by the compilation of the so's it showed it was trying to target amd64 while it was running on 32-bit. I believe that's the reason for the compilation error.

That is interesting, since I would not expect a 32bit system to even attempt a 64bit compile. I don't have a 32bit system to even test this on (I could setup a VM though). So, did you ever get it to compile, or are you still failing? I'm assuming Jeff compiled this all the time on 32bit a system. Eventually we might get this to cross to compile 32/64 bit, as MrD noted, but I think you have to be on 64bit system to create a 64bit binary (I think)... that why, I find it really odd that it would attempt it, in your case.

[tmiranda]

Originally Posted by Taddeusz

I think you don't understand. I was on 32-bit Ubuntu with the 32-bit default-jre & default-jdk from the Ubuntu repository. During by the compilation of the so's it showed it was trying to target amd64 while it was running on 32-bit. I believe that's the reason for the compilation error.

This is what I am seeing as well. I'm going from memory at the moment but I think I saw a -L in the command line that contained a reference to a path with "amd64" in it.

[routerunner]

Originally Posted by stuckless

...but I think you have to be on 64bit system to create a 64bit binary (I think)... that why, I find it really odd that it would attempt it, in your case.

Fortunately not . If you have multilib GCC is just as simple as adding "-m64" to CFLAGS and LDFLAGS (of course this is for the C/C++ part not JAVA).

Eddy

[stuckless]

Originally Posted by tmiranda

This is what I am seeing as well. I'm going from memory at the moment but I think I saw a -L in the command line that contained a reference to a path with "amd64" in it.

After doing a search for amd64
https://github.com/google/sagetv/sea...%9C%93&q=amd64

native/so/SageLinux/Makefile 
Showing the top match. Last indexed 3 days ago.

1	JDK_HOME ?= /usr/local/j2sdk
2	#JAVA_ARCH ?= i386
3	JAVA_ARCH ?= amd64

I'd modify the Makefile and comment out the amd64 line and uncomment the i386 line (or export JAVA_ARCH=i386 from the command line before the build)

Originally Posted by routerunner

Fortunately not . If you have multilib GCC is just as simple as adding "-m64" to CFLAGS and LDFLAGS (of course this is for the C/C++ part not JAVA).

Eddy

That's good know... I have very little experience with cross compiling, but I have feeling we'll have to do it

[Taddeusz]

Originally Posted by stuckless

After doing a search for amd64
https://github.com/google/sagetv/sea...%9C%93&q=amd64

native/so/SageLinux/Makefile 
Showing the top match. Last indexed 3 days ago.

1	JDK_HOME ?= /usr/local/j2sdk
2	#JAVA_ARCH ?= i386
3	JAVA_ARCH ?= amd64

I'd modify the Makefile and comment out the amd64 line and uncomment the i386 line (or export JAVA_ARCH=i386 from the command line before the build)



That's good know... I have very little experience with cross compiling, but I have feeling we'll have to do it

I wonder if there is a way to automatically detect the architecture from the makefile?

Currently I have dropped back to Ubuntu 14.04LTS 64-bit just in case systemd might be causing issues. I'll report if it has changed anything. I'll try 32-bit again if this test doesn't work.

[stuckless]

Originally Posted by Taddeusz

I wonder if there is a way to automatically detect the architecture from the makefile?

Currently I have dropped back to Ubuntu 14.04LTS 64-bit just in case systemd might be causing issues. I'll report if it has changed anything. I'll try 32-bit again if this test doesn't work.

I'm pretty it can be done, since most of the other 3rd party stuff uses autoconf and create the Makefiles... maybe this should get an upgrade (or maybe simpler to just do a check in the Makefile as you suggested, but I don't know how to do that)

[Taddeusz]

Originally Posted by stuckless

After doing a search for amd64
https://github.com/google/sagetv/sea...%9C%93&q=amd64

native/so/SageLinux/Makefile 
Showing the top match. Last indexed 3 days ago.

1	JDK_HOME ?= /usr/local/j2sdk
2	#JAVA_ARCH ?= i386
3	JAVA_ARCH ?= amd64

I'd modify the Makefile and comment out the amd64 line and uncomment the i386 line (or export JAVA_ARCH=i386 from the command line before the build)



That's good know... I have very little experience with cross compiling, but I have feeling we'll have to do it

A fix for this is to add the export JAVA_ARCH to the setup. Setting it to i386 or amd64 depending on your platform. You can actually add both of those to /etc/environment on Ubuntu to have them permanently set.

[Taddeusz]

Ok, the test on 14.04LTS 64-bit was unsuccessful. Still got the crash during channel scanning. Installed 15.05 32-bit. Set the JAVA_ARCH environment variable to i386 and successfully built 32-bit.

I also changed the dependencies for the deb packages to "default-jre" and successfully installed from the deb. The only caveat to this is that your "activkey" file must go into /etc/init.d.

Running a channel scan now. So far no crash but it's also not finding any channels.

[wildgoose]

Originally Posted by Fuzzy

I have the same issue, says it's missing jni.h

I hit the same issue last night. Turns out I set JAVA_HOME instead of JDK_HOME. With that fixed, everything did built!

I started with a clean Ubuntu Server 14.04 VM. Installed Oracle Java 8 by follow the instruction at: http://askubuntu.com/questions/52114...n-ubuntu-14-04

sudo apt-add-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer

Then followed stuckless's instructions on getting the extra packages, etc. It finished the built at the end and I got the .tar.gz and .deb files:

-rw-r--r-- 1 raychi raychi  6563356 Aug 12 18:55 sagetv-client_9.0.0_i386.deb
-rw-rw-r-- 1 raychi raychi  7747117 Aug 12 18:55 sagetv-client_9.0.0.tar.gz
-rw-r--r-- 1 raychi raychi 19870062 Aug 12 18:55 sagetv-server_9.0.0_i386.deb
-rw-rw-r-- 1 raychi raychi 27081501 Aug 12 18:55 sagetv-server_9.0.0.tar.gz

[Taddeusz]

Originally Posted by Taddeusz

Ok, the test on 14.04LTS 64-bit was unsuccessful. Still got the crash during channel scanning. Installed 15.05 32-bit. Set the JAVA_ARCH environment variable to i386 and successfully built 32-bit.

I also changed the dependencies for the deb packages to "default-jre" and successfully installed from the deb. The only caveat to this is that your "activkey" file must go into /etc/init.d.

Running a channel scan now. So far no crash but it's also not finding any channels.

Ok, channel scans complete. It does fine with QAM but for some reason fails to detect ATSC and sets it up as QAM.

[jbuszkie]

Where the windows specific "how to build"! :-)


Jim "Stuck in windows land"

[stuckless]

Originally Posted by jbuszkie

Where the windows specific "how to build"! :-)


Jim "Stuck in windows land"

Well, there's not "full" end to end build, as it has in Linux... but, I add add gradle support that enables Windows users to rebuild the Sage.jar quite easily. This would allow windows users to at least make changes to the Sage core java, and add it into their existing system.

https://github.com/google/sagetv/blo...er/BUILDING.md

[jbuszkie]

Originally Posted by stuckless

Well, there's not "full" end to end build, as it has in Linux... but, I add add gradle support that enables Windows users to rebuild the Sage.jar quite easily. This would allow windows users to at least make changes to the Sage core java, and add it into their existing system.

https://github.com/google/sagetv/blo...er/BUILDING.md

Thanks! Now if I only had time to play with this all!!!