Busybox handles file systems without symlink or hard link support.
It is a build time/installation option -
each function becomes a one line script.
Each of the configuration choices in the config system has a 'help' entry.
Somehow you must have missed reading the ones about the installation choices.
= = = = =
Intel had a full architecture license - not just a license to use ARM produced cores.
And Intel kept that license when they sold xScale to Marvell - -
Marvell had to be compatible with xScale (since Intel did not re-sell the license) but that is as far as compatibility went.
It was that full architecture license that they based their switch from CISC to RISC (internally) with the Pentium (IIRC) processor.
....
Well, whatever the public model was, Intel has been building RISC processors (with a CISC -> RISC decoder glued to the front bus) for over twenty years now.
Welcome to the 21st century.
= = = =
Post one of your "runs on K1 but does not run on anything else ARM" binary examples.
Do us a favor and do not strip it.
= = = =
Edit:
Go to:
https://www.mobileread.com/forums/sho...d.php?t=240616
Download:
base-0.3-a8_armhf_vfp3d16.tar.gz
Browse the esys/bin, esys/sbin parts of the file tree.
There you will find about 160 Busybox functions that do not use hard links, symbolic links, or copies of the Busybox binary as examples.
(No, I didn't do those, they where produced by the Busybox install command.)
For the express hint (the esys/bin/bunzip2 file contents):
Code:
#!/mnt/us/esys/bin/busybox
bunzip2
That thread is also the worked example of concurrently using multiple system libraries (Kindle soft-float and Debian hard-float) on an ELF system.
That 'base system' will run Debian/Jessie binaries in /mnt/us/esys/** with a bit of PatchELF magic to the downloaded Debian binaries.
(Debian/Jessie ARM standard is hard-float, the Kindle system libraries are not.)
- - - -
Less than a hundred downloads in two years -
Not one of my more popular projects.
