Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: nickjf20 on August 23, 2011, 02:08:39 PM
-
Hi,
I'm trying to get Java x64 self extracting binaries to extract, but am getting error messages during the unpack reading
error './install.sfx.3456 where 3456 takes a seemingly random value from 3-4000.
On further inspection and forum trawling, it seems the Java developers didn't take into account those running off pure x64 systems (What I understand to be tiny core) and the vastly more common multilib systems.
The fix many had was symlinking certain pure x64 libs to the position of their x64 multi lib counterparts (i.e. ln -s /lib/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2) or installing g++ multi lib libraries (currently not available in the 3.x repo)
x64 Java will not function without these x64 libraries in the multi lib locations, and changing the location of these libs results in a segmentation fault during the installation, again resulting in no java.
Bascially, it seems like I need '/lib64/ld-linux-x86-64.so.2' to run Java x64
Any ideas ? Does microcorex64 store these x64 libs in a different location ?
Thanks
Nick
Similar semi-solved problem http://www.linuxquestions.org/questions/linux-from-scratch-13/jdk-install-fails-with-install-sfx-no-such-file-during-installation-506082/ (http://www.linuxquestions.org/questions/linux-from-scratch-13/jdk-install-fails-with-install-sfx-no-such-file-during-installation-506082/ here)
-
The microcore64 currently offered is a 64-bit kernel combined with 32-bit userspace. We don't currently have a pure 64-bit port.
-
Is there a timescale for supporting an x64 user space in Microcore anytime soon ?
If no, is there any way I can botch together this one lib to allow Java to work ?
-
No timescale that I know of.
The 64-bit cross-toolchain contains a 64-bit libc (toolchain64-lib.tcz). You might get away with linking /lib64 to /usr/local/x64/lib. But Java may require other libraries as well.
-
Thanks a bunch ! Extracts like a charm now, I'll report back when it's working.
If I made an extension out of it, could I copy the single required x64 lib into the squash file so it unpacks into the correct /lib64/ directory ?
EDIT: Works fine -- CPU usage is high though -- could just be RAM starved. I'll look further into it.
-
I've got a standalone extension which now works with no dependencies.
It does have the mentioned library above included so I don't know whether it's allowed in the repo or not ...
If you want it, I'll happily upload it and the file list.
-
Yes, for the repo it would be better to have it depend on the toolchain64-lib extension. That way no need to update things in multiple places.