Busybox config file

[wysiwyg]

Good afternoon everyone!  I need to recompile busybox to include one or more applets than what comes with TC by default.  Is there anywhere that I can get the config file (and perhaps the compile script) used for busybox?

Thanks,
Dave

[Juanito]

http://tinycorelinux.net/6.x/x86/release/src/busybox/

[gerald_clark]

Click the download link at the top of this screen.
Under release files you will find the src.

What exactly do you need, You may find it in an extension.
Ex: busybox-httpd.tcz

[wysiwyg]

Awesome!  Thanks guys!

Dave

[wysiwyg]

There appears to be multiple config files for that software with the compile script calling both of them.  Why does the binary get compiled twice?  Also, are those the patches to upgrade to version 1.23.2 from 1.23.1 (the names correspond with patches from the bb website)?  Lastly, are the compile flags the same for 64bit?  I tried looking under the appropriate directory structure for the x64 build of bb, but it doesn't exist.

Thanks,
Dave

[Juanito]

The binary is split into applets that require suid (linked to busybox.suid) and those that do not (linked to busybox) - hence two config files.

The patched source has two tinycore custom patches appled and yes, the other patches add up to 1.23.2, which wasn't available at the time.

For x86_64 you need:

Code: [Select]

$ make CC="gcc -mtune=generic -Os -pipe" CXX="g++ -mtune=generic -Os -pipe -fno-exceptions -fno-rtti"

[wysiwyg]

Thanks Juanito!  I'll add it in the compile script I wrote!

Thanks,
Dave

[wysiwyg]

Good evening everyone!  As stated, I'm attempting to recompile BB to add in extra functionality, but I could never get the system to configure correctly during boot (modules were not loading correctly) when I compiled my own version.  By just copying back the TC versions of the two binaries, the system works correctly.  My next step was to recompile using the OEM .config files for BB.  This too produced the same results as if I were using my custom .config files.  I'm not quite sure what could be going wrong.  I did notice that compiling with the OEM .config files, the binary sizes don't match:

-rwxr-xr-x 1 root root 540824 Apr 30 19:16 busybox
-rwsr-xr-x 1 root root  69360 Apr 30 19:16 busybox.suid
-rwsr-xr-x 1 root root  69352 Apr 18 18:44 busybox.suid.tc
-rwxr-xr-x 1 root root 534480 Apr 18 18:44 busybox.tc

I'm using the compile flags that were provided along with the following two commands to compile:

make
make CONFIG_PREFIX=/tmp/package install

I'm using the source code from the official busybox website (v1.23.1) without the two TC custom patches.  Those patches wouldn't be stopping this from working correctly right? Any thoughts on what's happening here?

Thanks,
Dave

[Juanito]

One of the custom patches concerns depmod - you'll need this one for modules to load correctly

[wysiwyg]

Ahhhhh, I will apply those patches and report back!  Thanks Juanito!

Dave

[wysiwyg]

Good morning everyone!  I am attempting to apply those two patches, but it doesn't seem to work.  I'm trying:

patch -p1 [-N|-R] < busybox_1.21.1_depmod.patch

but I keep getting a:

hunk #1 FAILED on 206

error message.  I'm attempting to apply this patch to 1.23.1.  Will this not work on that version?  I see there is a  busybox-1.23.1-patched.tar.bz2 file.  As the name suggests, is this a patched 1.21.1 up to 1.23.1 while applying the two custom patches as well?

Thanks,
Dave

[wysiwyg]

Just as a side question, is there an advantage to compiling the files as applets instead of symlinks?

Thanks,
Dave

[Juanito]

yes, the patched source has the two custom patches applied.

[wysiwyg]

Thanks Juanito, I ended up getting things going not too long ago using the patched version.

Thanks,
Dave