building core.gz from scratch

[ulfr]

    thank you very much guys for all your time 

    you have set me on the path 

    i now have a good general idea of where to look and how things are done

    i'll poke around and see if i can learn a little more 

    and thanks for making such a great distro 

    its my favorite


    ulfr   

[linic]

It's not a script, it is just build notes - you start at the beginning and work your way to the end 

Hi Juanito, in summary, there is no build script for rootfs.gz even for the current latest TC 16 x86. Is that right?
For example, if one wants to rebuild rootfs.gz, let's say to change

Code: [Select]

--enable-kernel=6.1.2 to

Code: [Select]

--enable-kernel=4.4.302, one would have to

• read the http://tinycorelinux.net/16.x/x86/release/src/toolchain/compile_tc16_x86
• infer the commands to run
• manually run them until reaching the end of the build notes (fixing the errors if some show up or filling the gaps if there are any)
• probably running an additional repacking to generate the rootfs.gz command because the build notes end with "[remove files to match base/extension setup]"

Would that be it?

Also, thank you Juanito everyone for tinycore! It's fascinating!

[Juanito]

probably running an additional repacking to generate the rootfs.gz command because the build notes end with "remove files to match base/extension setup"

Not exactly, the "remove files to match base/extension setup" refers to the chroot environment.

To update rootfs.gz, you need to overwrite the existing files with the newly built files (after first stripping them) like this:

Code: [Select]

mkdir /tmp/extract
cd /tmp/extract
zcat /tmp/rootfs.gz | sudo cpio -i -H newc -d
rm /tmp/rootfs.gz

[overwrite/update existing files]

cd /tmp/extract
find | sudo cpio -o -H newc | gzip -2 > ../rootfs.gz
cd /tmp
advdef -z4 rootfs.gz

Would that be it?

Yes 

[linic]

Hi Juanito,

I'm interested to obtain copies of

Code: [Select]

binutils_usr.tce.list
gcc_usr_remove.tce.list
gcc_local_remove.tce.list

They are referenced in http://tinycorelinux.net/16.x/x86/release/src/toolchain/compile_tc16_x86. Are they hosted anywhere? Are there any other .tce.list files which were used in making TC16 x86? I am interested in those too.

Also, thank you for your last reply!

Oh, and the compile_tc16_x86 notes are great! I was able to compile roughly 1/3 of the required sources so far. I'm automating the steps in a couple of .sh scripts. I plan to release those scripts once I have a working result.

[Juanito]

binutils_usr.tce.list is created by:

Code: [Select]

touch mymarker
sudo make install
sudo find / -not -type 'd' -cnewer mymarker | grep -v "\/proc\/" | grep -v "^\/sys\/" | tee files
vi files (remove any obviously unneeded files)
mv files binutils_usr.tce.list
The other two were made by a similar process and then editing to leave only the files I wanted to remove.

Sorry, but I didn't keep the lists 

[linic]

No worries 

Thanks for your answer! Very interesting!

[linic]

I wrote a couple of scripts which I released here https://github.com/linic/tcc
I was able to compile all the sources mentioned in compile_tc16_x86 (http://tinycorelinux.net/16.x/x86/release/src/toolchain/compile_tc16_x86) and busybox (using the compile notes in 15.x http://tinycorelinux.net/15.x/x86/release/src/busybox/compile_busybox).
I changed some flags. I think I mentioned them all in the README.md (https://github.com/linic/tcc/blob/main/README.md)
I'm not done with repacking rootfs.gz, but I thought it was a nice state to share it.

[Yleisajattelija]

I'm trying to building minimal command line version of tc (=MicroCore?) for VSRVES01 board.

I have experience with loaders and linkers 30 years ago, but unfortunately zero experience with GNU tool chain. I suppose it is standard tool chain for linux development, so standard procedure exists.

But this is a obvious problem now, 2025 dated ld documentation without RISC-V...

https://sourceware.org/binutils/docs/ld.pdf

...problems with compile/link/load -process anticipated...

I tried same thing with Guruplug plus, but even with help Martin Michlmayr Debian installer wouldn't start. That HW loaded two images by U-boot (kernel and ramdisk), and same would be logical on tc, too.

I think building batch for Rasperry Pi would be good starting point (I know, it is somewhere on source tree, and documentation is missing, too... )