i installed xuggler for jvm 32bit from here http://www.liferay.com/community/wiki/-/wiki/Main/Preview+Generation, it worked perfectly, but now i need this for 64bit jvm, can anyone help?
thanks
You can have Liferay download the version for you: Go to ControlPanel/Server/Server Administration/External Services (at least on tomcat this is the easiest way, I'm not sure about other platforms)
The platforms there explicitly list win64 and you can be reasonably sure to get the supported version.
Update: I found this in portal.properties. You can construct the URL from this:
#
# Set the properties used to install Xuggler at runtime.
#
xuggler.jar.file[32-linux]=xuggle-xuggler-arch-i686-pc-linux-gnu.jar
xuggler.jar.file[32-mac]=xuggle-xuggler-arch-i386-xuggle-darwin11.jar
xuggler.jar.file[32-win]=xuggle-xuggler-arch-i686-w64-mingw32.jar
xuggler.jar.file[64-linux]=xuggle-xuggler-arch-x86_64-pc-linux-gnu.jar
xuggler.jar.file[64-mac]=xuggle-xuggler-arch-x86_64-xuggle-darwin11.jar
xuggler.jar.file[64-win]=xuggle-xuggler-arch-x86_64-w64-mingw32.jar
xuggler.jar.name[32-linux]=Linux 32-bit JVM (with GNU libc v6)
xuggler.jar.name[32-mac]=Mac OS X 10.7 32-bit JVM
xuggler.jar.name[32-win]=Windows 32-bit JVM
xuggler.jar.name[64-linux]=Linux 64-bit JVM (with GNU libc v6)
xuggler.jar.name[64-mac]=Mac OS X 10.7 64-bit JVM
xuggler.jar.name[64-win]=Windows 64-bit JVM
xuggler.jar.options=32-linux,32-mac,32-win,64-linux,64-mac,64-win
xuggler.jar.url=http://xuggle.googlecode.com/svn/trunk/repo/share/java/xuggle/xuggle-xuggler/5.4/
Related
I have installed qtcreator in lubuntu 16.04 and when trying to open it, i am getting an error
This program requires an x86 processor that supports SSE2 extension, at least a Pentium 4 or newer
Aborted (core dumped)
can someone help me to solve this problem.
I'm using ICOP borad with Lubuntu 16.04
You'll probably need to compile from source with -mno-sse (Or just -mno-sse2 if your CPU has SSE1 but not SSE2). If you're not cross-compiling from a faster machine, use -march=native to enable all the instruction sets your CPU supports, and not enable any that it doesn't.)
The 32-bit qtcreator package probably enables SSE2 on purpose, because detected it and printed an error instead of just dying with a SIGILL. Likely it can be built from source (or the Ubuntu source package) with a different config.
Apparently 32-bit Ubuntu is intended to run on CPUs without SSE2, according to this guide posted in the Ubuntu forums. (It's talking about old desktops with old mainstream CPUs, not modern embedded, but same difference.) So this might be considered a bug.
gcc's 32-bit code-gen does default to assuming cmov support and other P6 (Pentium Pro / Pentium II) instructions, but I guess Ubuntu configures their 32-bit gcc to not enable -msse2 by default. So you couldn't even boot the kernel on a P5 Pentium or older. (Makes sense, if you have SSE2 you probably have an x86-64 capable CPU; running on 32-bit-only CPUs is one of the few reasons for not just using x86-64 Ubuntu. But some people do use 32-bit systems for some reason on modern HW, and gimping it too much by disabling cmov and other P6 new instructions might be undesirable.)
A few years ago (like 2013 maybe?) I booted an Ubuntu live CD on an Athlon XP (SSE1 but not SSE2). It mostly booted to the desktop, but there was a popup from one program that it had died with SIGILL. i.e. it tried to run an SSE2 instruction and got an illegal-instruction exception. I guess this would be considered a but if 32-bit Ubuntu really does aim to support CPUs without SSE2
I am doing some tests on the performance of QEMU (qemu-system-i386) in full emulation mode (with TCG), and avoiding KVM. I have installed the version available in the debian repository (QEMU emulator version 1.1.2 (Debian 1.1.2+dfsg-6a+deb7u6), and downloaded and compiled the sources for Qemu 2.3.0, Qemu 1.0.0, Qemu 1.1.2, and also the source for Debian 1.1.2+dfsg-6a+deb7u6.
I am configuring the project in the following way, in all cases:
./configure --enable-sdl --target-list=i386-softmmu --disable-kvm --enable-tcg-interpreter
The version installed from the repository is quite faster than any of the versions manually compiled. I am always using the same image for the hard drive). I have ensured that kvm is never enabled or loaded:
* Querying qemu (info kvm)
* Looking for loaded drivers (lsmod | grep kvm), and (ls /dev/kvm).
Kvm is not loaded in any of the cases.
I have also tried to change the -O2 by -O3 in the configuration file, and stripped the symbols in the binary (which should not be a difference).
I must be missing something (default configuration for the debian package, compilation options... but I cannot figure out what).
Which could be the reason for this performance difference? (Any idea, experience?)
Thank you very much!
The problem here is your '--enable-tcg-interpreter' argument to configure. This disables the usual JIT-based TCG backend for the host CPU in favour of a slow interpreted backend. You never want the interpreter unless QEMU would otherwise not support your host CPU at all; as you have found, it is markedly slower than the default JIT.
I try to understand the requirements for developing Linux application running on 64-bit OS (with 64-bit architecture).
If the code was written for 32-bits architecture, does it mean that on regular compilation (gcc -m32) it will run on the 64-bit system OS, without any problems ?
Thank you,
Ran
Yes, it will. The only caveats to this are that you need 32 bit libraries to run the program, and 32 bit development packages to compile it. Most distros provide these and make it simple to install them as well.
I have installed java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5.x86_64 on Cent OS 6.6. When i am trying to run my software it is thorwing error in "libjvm.so wrong ELF class ELFCLASS64". while I ran java -version output is-->
java version 1.7.0_15
java SE runtime environment (build 1.7.0_15)
Java Hotspot 64Bit Server VM (build 23.7-b01, mixed mode)
JRE version on machine
Jre – 1.7.0_15-fcs.x86_84
JDK version
java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5.x86_64
Your software is a 32-bit ELF file but libjvm.so is only available as a 64-bit ELF library. The runtime linker therefor cannot link the library.
You either need to compile your program in 64-bit mode or get a 32-bit JVM.
As title said, I have C program complied and created a binary in 64-bit machine.Will this binary work under 32-bit ?
64-bit binaries cannot run on a 32-bit OS. If file reports ELF 64-bit, you have a 64-bit binary.
In order to build 32-bit binaries on a 64-bit Linux, you need pass -m32 to gcc. You also need to have 32-bit libraries installed (sudo apt-get install libc6-dev-i386).
The compiling machine does not matter. What matters is: is the code generated 32 bits (answer: yes) or 64 bits (answer: no).
Will it work on a 32-bit machine? One with a CPU which doesn't support 64-bit mode? No.
Will it work on a 64-bit VM on a 32-bit native OS? Yes, in my experience.
A surprising result is that 64-bit VMs CAN be run under a 32-bit host OS, provided the CPU is capable and you don't want to allocate too much ram (>2G or thereabouts) to the guest.