Corepure64 Released

[Juanito]

Team Tinycore is pleased to announce corepure64 - a fully 64-bit version of tinycore for x86_64.

• Based on version 4.7 of core/core64
• Fully 64-bit toolchain and base applications/libraries using the same source versions as core/core64
• Uses vmlinuz64 and the kernel modules *-tinycore64 from core64
• Not compatible with 32-bit extensions from core/core64
• Uses Xorg-7.6 as Xvesa is not 64-bit compatible
• compiletc toolchain available to build user supplied extensions
• editor/fluff and basic gtk2 applications available

Distribution files are available at: http://distro.ibiblio.org/tinycorelinux/4.x/x86_64


User feedback would be welcomed and much appreciated. As this is a first version, please approach with care and do not use on production systems.

Tested on one (dell e6220) machine with intel hd3000 graphics hardware and broadcom wireless.

Due to the (somewhat) protracted development cycle, some extensions are outdated as compared to the x86 repo, please feel free to add and update.


Edit: To clarify:

core64 - each 32-bit app can use up to 4gb of ram
corepure64 - each 64-bit app is only limited by the ram available

[coreplayer2]

 That's awesome thanks

[Lee]

...
User feedback would be welcomed and much appreciated. As this is a first version, please approach with care and do not use on production systems.
...

Tested (briefly) on Dell PowerEdge SC440 (one dual core cpu) and Dell Precision 1500 (1 quad core cpu) - excellent on both.

Excellent release.  Thank you.

[bmarkus]

Tested on AMD Athlon 64 X2 Dual Core 4200+ with 4GB RAM. Works fine, no issues foune

[bmarkus]

To check toolchain built liblzma.tcz and xz.tcz using my piCore build scripts. Without any modification extensions built, working as expected. Its great.

Tried ncurses applications, mc and htop. It fails due to lack of ncurses header files. ncurses-dev.tcz installed, there is something wrong.

[Juanito]

I think you may have to tell mc & htop that the ncurses headers are in /usr/local/include/ncurses in their ./configure scripts?

[bmarkus]

I think you may have to tell mc & htop that the ncurses headers are in /usr/local/include/ncurses in their ./configure scripts?

Will check what is wrong later, but my build scripts are working on x86 and piCore versions So there is something different here.

[beroje]

tc@box:~/Downloads$ la
total 6396
drwxr-xr-x    2 tc       staff           80 Nov 14 15:07 ./
drwxr-s---   15 tc       staff          620 Nov 14 14:54 ../
-rw-r--r--    1 tc       staff      6532297 Nov 14 15:07 corepure64.gz
-rw-r--r--    1 tc       staff           48 Nov 14 15:06 corepure64.gz.md5.txt
tc@box:~/Downloads$
tc@box:~/Downloads$ cat corepure64.gz.md5.txt
cfbbc116c4824223ba627e2515754cdf  corepure64.gz
tc@box:~/Downloads$ md5sum corepure64.gz
f8e54893041a2dfaaa2d0ba8b0fac764  corepure64.gz
tc@box:~/Downloads$

[Juanito]

I take it you mean there's a problem with the checksum.

I deleted and uploaded corepure64.gz again - from the repo on ibiblio:

Code: [Select]

$ cat corepure64.gz.md5.txt
f8e54893041a2dfaaa2d0ba8b0fac764  corepure64.gz
$ md5sum corepure64.gz
f8e54893041a2dfaaa2d0ba8b0fac764  corepure64.gz

[bmarkus]

I think you may have to tell mc & htop that the ncurses headers are in /usr/local/include/ncurses in their ./configure scripts?

Yes, specifiying explicitly solves the problem. htop builds fine, will submit. There is an issue with mc, will investigate.

In x86 and picore ncurses headers are in /usr/local/include so configure works without extra arg.

[Juanito]

In x86 and picore ncurses headers are in /usr/local/include so configure works without extra arg.

That's where ncurses put them by default and I left them there as it made it easier to symlink them to /usr/include in order for "make menuconfig" to work with a kernel source.

[bmarkus]

That"s OK. I will change in piCore and probably in x86 to be in sync.

[Su30FlankerC]

This is wonderful.
I can now use and maximize my RAM in Tiny Core.

[Juanito]

just to be clear:

core64 - each 32-bit app can use up to 4gb of ram
corepure64 - each 64-bit app is only limited by the ram available

[Lee]

just to be clear:

core64 - each 32-bit app can use up to 4gb of ram
corepure64 - each 64-bit app is only limited by the ram available

While that was not particularly unclear (at least to me), I can see where someone new to Core might not immediately see the distinction.  It might be worth while to add those few lines to the original post of this thread.