1# 2# For a description of the syntax of this configuration file, 3# see scripts/kbuild/config-language.txt. 4# 5 6mainmenu "BusyBox Configuration" 7 8config HAVE_DOT_CONFIG 9 bool 10 default y 11 12menu "Busybox Settings" 13 14menu "General Configuration" 15 16config DESKTOP 17 bool "Enable options for full-blown desktop systems" 18 default y 19 help 20 Enable options and features which are not essential. 21 Select this only if you plan to use busybox on full-blown 22 desktop machine with common Linux distro, not on an embedded box. 23 24config EXTRA_COMPAT 25 bool "Provide compatible behavior for rare corner cases (bigger code)" 26 default n 27 help 28 This option makes grep, sed etc handle rare corner cases 29 (embedded NUL bytes and such). This makes code bigger and uses 30 some GNU extensions in libc. You probably only need this option 31 if you plan to run busybox on desktop. 32 33config INCLUDE_SUSv2 34 bool "Enable obsolete features removed before SUSv3" 35 default y 36 help 37 This option will enable backwards compatibility with SuSv2, 38 specifically, old-style numeric options ('command -1 <file>') 39 will be supported in head, tail, and fold. (Note: should 40 affect renice too.) 41 42config USE_PORTABLE_CODE 43 bool "Avoid using GCC-specific code constructs" 44 default n 45 help 46 Use this option if you are trying to compile busybox with 47 compiler other than gcc. 48 If you do use gcc, this option may needlessly increase code size. 49 50config PLATFORM_LINUX 51 bool "Enable Linux-specific applets and features" 52 default y 53 help 54 For the most part, busybox requires only POSIX compatibility 55 from the target system, but some applets and features use 56 Linux-specific interfaces. 57 58 Answering 'N' here will disable such applets and hide the 59 corresponding configuration options. 60 61choice 62 prompt "Buffer allocation policy" 63 default FEATURE_BUFFERS_USE_MALLOC 64 help 65 There are 3 ways BusyBox can handle buffer allocations: 66 - Use malloc. This costs code size for the call to xmalloc. 67 - Put them on stack. For some very small machines with limited stack 68 space, this can be deadly. For most folks, this works just fine. 69 - Put them in BSS. This works beautifully for computers with a real 70 MMU (and OS support), but wastes runtime RAM for uCLinux. This 71 behavior was the only one available for BusyBox versions 0.48 and 72 earlier. 73 74config FEATURE_BUFFERS_USE_MALLOC 75 bool "Allocate with Malloc" 76 77config FEATURE_BUFFERS_GO_ON_STACK 78 bool "Allocate on the Stack" 79 80config FEATURE_BUFFERS_GO_IN_BSS 81 bool "Allocate in the .bss section" 82 83endchoice 84 85config SHOW_USAGE 86 bool "Show applet usage messages" 87 default y 88 help 89 Enabling this option, BusyBox applets will show terse help messages 90 when invoked with wrong arguments. 91 If you do not want to show any (helpful) usage message when 92 issuing wrong command syntax, you can say 'N' here, 93 saving approximately 7k. 94 95config FEATURE_VERBOSE_USAGE 96 bool "Show verbose applet usage messages" 97 default y 98 depends on SHOW_USAGE 99 help 100 All BusyBox applets will show verbose help messages when 101 busybox is invoked with --help. This will add a lot of text to the 102 busybox binary. In the default configuration, this will add about 103 13k, but it can add much more depending on your configuration. 104 105config FEATURE_COMPRESS_USAGE 106 bool "Store applet usage messages in compressed form" 107 default y 108 depends on SHOW_USAGE 109 help 110 Store usage messages in .bz compressed form, uncompress them 111 on-the-fly when <applet> --help is called. 112 113 If you have a really tiny busybox with few applets enabled (and 114 bunzip2 isn't one of them), the overhead of the decompressor might 115 be noticeable. Also, if you run executables directly from ROM 116 and have very little memory, this might not be a win. Otherwise, 117 you probably want this. 118 119config BUSYBOX 120 bool "Include busybox applet" 121 default y 122 help 123 The busybox applet provides general help regarding busybox and 124 allows the included applets to be listed. It's also required 125 if applet links are to be installed at runtime. 126 127 If you can live without these features disabling this will save 128 some space. 129 130config FEATURE_INSTALLER 131 bool "Support --install [-s] to install applet links at runtime" 132 default y 133 depends on BUSYBOX 134 help 135 Enable 'busybox --install [-s]' support. This will allow you to use 136 busybox at runtime to create hard links or symlinks for all the 137 applets that are compiled into busybox. 138 139config INSTALL_NO_USR 140 bool "Don't use /usr" 141 default n 142 help 143 Disable use of /usr. busybox --install and "make install" 144 will install applets only to /bin and /sbin, 145 never to /usr/bin or /usr/sbin. 146 147config LOCALE_SUPPORT 148 bool "Enable locale support (system needs locale for this to work)" 149 default n 150 help 151 Enable this if your system has locale support and you would like 152 busybox to support locale settings. 153 154config UNICODE_SUPPORT 155 bool "Support Unicode" 156 default y 157 help 158 This makes various applets aware that one byte is not 159 one character on screen. 160 161 Busybox aims to eventually work correctly with Unicode displays. 162 Any older encodings are not guaranteed to work. 163 Probably by the time when busybox will be fully Unicode-clean, 164 other encodings will be mainly of historic interest. 165 166config UNICODE_USING_LOCALE 167 bool "Use libc routines for Unicode (else uses internal ones)" 168 default n 169 depends on UNICODE_SUPPORT && LOCALE_SUPPORT 170 help 171 With this option on, Unicode support is implemented using libc 172 routines. Otherwise, internal implementation is used. 173 Internal implementation is smaller. 174 175config FEATURE_CHECK_UNICODE_IN_ENV 176 bool "Check $LC_ALL, $LC_CTYPE and $LANG environment variables" 177 default n 178 depends on UNICODE_SUPPORT && !UNICODE_USING_LOCALE 179 help 180 With this option on, Unicode support is activated 181 only if locale-related variables have the value of the form 182 "xxxx.utf8" 183 184 Otherwise, Unicode support will be always enabled and active. 185 186config SUBST_WCHAR 187 int "Character code to substitute unprintable characters with" 188 depends on UNICODE_SUPPORT 189 default 63 190 help 191 Typical values are 63 for '?' (works with any output device), 192 30 for ASCII substitute control code, 193 65533 (0xfffd) for Unicode replacement character. 194 195config LAST_SUPPORTED_WCHAR 196 int "Range of supported Unicode characters" 197 depends on UNICODE_SUPPORT 198 default 767 199 help 200 Any character with Unicode value bigger than this is assumed 201 to be non-printable on output device. Many applets replace 202 such chars with substitution character. 203 204 The idea is that many valid printable Unicode chars are 205 nevertheless are not displayed correctly. Think about 206 combining charachers, double-wide hieroglyphs, obscure 207 characters in dozens of ancient scripts... 208 Many terminals, terminal emulators, xterms etc will fail 209 to handle them correctly. Choose the smallest value 210 which suits your needs. 211 212 Typical values are: 213 126 - ASCII only 214 767 (0x2ff) - there are no combining chars in [0..767] range 215 (the range includes Latin 1, Latin Ext. A and B), 216 code is ~700 bytes smaller for this case. 217 4351 (0x10ff) - there are no double-wide chars in [0..4351] range, 218 code is ~300 bytes smaller for this case. 219 12799 (0x31ff) - nearly all non-ideographic characters are 220 available in [0..12799] range, including 221 East Asian scripts like katakana, hiragana, hangul, 222 bopomofo... 223 0 - off, any valid printable Unicode character will be printed. 224 225config UNICODE_COMBINING_WCHARS 226 bool "Allow zero-width Unicode characters on output" 227 default n 228 depends on UNICODE_SUPPORT 229 help 230 With this option off, any Unicode char with width of 0 231 is substituted on output. 232 233config UNICODE_WIDE_WCHARS 234 bool "Allow wide Unicode characters on output" 235 default n 236 depends on UNICODE_SUPPORT 237 help 238 With this option off, any Unicode char with width > 1 239 is substituted on output. 240 241config UNICODE_BIDI_SUPPORT 242 bool "Bidirectional character-aware line input" 243 default n 244 depends on UNICODE_SUPPORT && !UNICODE_USING_LOCALE 245 help 246 With this option on, right-to-left Unicode characters 247 are treated differently on input (e.g. cursor movement). 248 249config UNICODE_NEUTRAL_TABLE 250 bool "In bidi input, support non-ASCII neutral chars too" 251 default n 252 depends on UNICODE_BIDI_SUPPORT 253 help 254 In most cases it's enough to treat only ASCII non-letters 255 (i.e. punctuation, numbers and space) as characters 256 with neutral directionality. 257 With this option on, more extensive (and bigger) table 258 of neutral chars will be used. 259 260config UNICODE_PRESERVE_BROKEN 261 bool "Make it possible to enter sequences of chars which are not Unicode" 262 default n 263 depends on UNICODE_SUPPORT 264 help 265 With this option on, on line-editing input (such as used by shells) 266 invalid UTF-8 bytes are not substituted with the selected 267 substitution character. 268 For example, this means that entering 'l', 's', ' ', 0xff, [Enter] 269 at shell prompt will list file named 0xff (single char name 270 with char value 255), not file named '?'. 271 272config PAM 273 bool "Support for PAM (Pluggable Authentication Modules)" 274 default n 275 help 276 Use PAM in some busybox applets (currently login and httpd) instead 277 of direct access to password database. 278 279config FEATURE_USE_SENDFILE 280 bool "Use sendfile system call" 281 default y 282 select PLATFORM_LINUX 283 help 284 When enabled, busybox will use the kernel sendfile() function 285 instead of read/write loops to copy data between file descriptors 286 (for example, cp command does this a lot). 287 If sendfile() doesn't work, copying code falls back to read/write 288 loop. sendfile() was originally implemented for faster I/O 289 from files to sockets, but since Linux 2.6.33 it was extended 290 to work for many more file types. 291 292config LONG_OPTS 293 bool "Support for --long-options" 294 default y 295 help 296 Enable this if you want busybox applets to use the gnu --long-option 297 style, in addition to single character -a -b -c style options. 298 299config FEATURE_DEVPTS 300 bool "Use the devpts filesystem for Unix98 PTYs" 301 default y 302 help 303 Enable if you want BusyBox to use Unix98 PTY support. If enabled, 304 busybox will use /dev/ptmx for the master side of the pseudoterminal 305 and /dev/pts/<number> for the slave side. Otherwise, BSD style 306 /dev/ttyp<number> will be used. To use this option, you should have 307 devpts mounted. 308 309config FEATURE_CLEAN_UP 310 bool "Clean up all memory before exiting (usually not needed)" 311 default n 312 help 313 As a size optimization, busybox normally exits without explicitly 314 freeing dynamically allocated memory or closing files. This saves 315 space since the OS will clean up for us, but it can confuse debuggers 316 like valgrind, which report tons of memory and resource leaks. 317 318 Don't enable this unless you have a really good reason to clean 319 things up manually. 320 321config FEATURE_UTMP 322 bool "Support utmp file" 323 default y 324 help 325 The file /var/run/utmp is used to track who is currently logged in. 326 With this option on, certain applets (getty, login, telnetd etc) 327 will create and delete entries there. 328 "who" applet requires this option. 329 330config FEATURE_WTMP 331 bool "Support wtmp file" 332 default y 333 depends on FEATURE_UTMP 334 help 335 The file /var/run/wtmp is used to track when users have logged into 336 and logged out of the system. 337 With this option on, certain applets (getty, login, telnetd etc) 338 will append new entries there. 339 "last" applet requires this option. 340 341config FEATURE_PIDFILE 342 bool "Support writing pidfiles" 343 default y 344 help 345 This option makes some applets (e.g. crond, syslogd, inetd) write 346 a pidfile at the configured PID_FILE_PATH. It has no effect 347 on applets which require pidfiles to run. 348 349config PID_FILE_PATH 350 string "Path to directory for pidfile" 351 default "/var/run" 352 depends on FEATURE_PIDFILE 353 help 354 This is the default path where pidfiles are created. Applets which 355 allow you to set the pidfile path on the command line will override 356 this value. The option has no effect on applets that require you to 357 specify a pidfile path. 358 359config FEATURE_SUID 360 bool "Support for SUID/SGID handling" 361 default y 362 help 363 With this option you can install the busybox binary belonging 364 to root with the suid bit set, enabling some applets to perform 365 root-level operations even when run by ordinary users 366 (for example, mounting of user mounts in fstab needs this). 367 368 Busybox will automatically drop privileges for applets 369 that don't need root access. 370 371 If you are really paranoid and don't want to do this, build two 372 busybox binaries with different applets in them (and the appropriate 373 symlinks pointing to each binary), and only set the suid bit on the 374 one that needs it. 375 376 The applets which require root rights (need suid bit or 377 to be run by root) and will refuse to execute otherwise: 378 crontab, login, passwd, su, vlock, wall. 379 380 The applets which will use root rights if they have them 381 (via suid bit, or because run by root), but would try to work 382 without root right nevertheless: 383 findfs, ping[6], traceroute[6], mount. 384 385 Note that if you DONT select this option, but DO make busybox 386 suid root, ALL applets will run under root, which is a huge 387 security hole (think "cp /some/file /etc/passwd"). 388 389config FEATURE_SUID_CONFIG 390 bool "Runtime SUID/SGID configuration via /etc/busybox.conf" 391 default y 392 depends on FEATURE_SUID 393 help 394 Allow the SUID / SGID state of an applet to be determined at runtime 395 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.) 396 The format of this file is as follows: 397 398 APPLET = [Ssx-][Ssx-][x-] [USER.GROUP] 399 400 s: USER or GROUP is allowed to execute APPLET. 401 APPLET will run under USER or GROUP 402 (reagardless of who's running it). 403 S: USER or GROUP is NOT allowed to execute APPLET. 404 APPLET will run under USER or GROUP. 405 This option is not very sensical. 406 x: USER/GROUP/others are allowed to execute APPLET. 407 No UID/GID change will be done when it is run. 408 -: USER/GROUP/others are not allowed to execute APPLET. 409 410 An example might help: 411 412 [SUID] 413 su = ssx root.0 # applet su can be run by anyone and runs with 414 # euid=0/egid=0 415 su = ssx # exactly the same 416 417 mount = sx- root.disk # applet mount can be run by root and members 418 # of group disk (but not anyone else) 419 # and runs with euid=0 (egid is not changed) 420 421 cp = --- # disable applet cp for everyone 422 423 The file has to be owned by user root, group root and has to be 424 writeable only by root: 425 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf) 426 The busybox executable has to be owned by user root, group 427 root and has to be setuid root for this to work: 428 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox) 429 430 Robert 'sandman' Griebl has more information here: 431 <url: http://www.softforge.de/bb/suid.html >. 432 433config FEATURE_SUID_CONFIG_QUIET 434 bool "Suppress warning message if /etc/busybox.conf is not readable" 435 default y 436 depends on FEATURE_SUID_CONFIG 437 help 438 /etc/busybox.conf should be readable by the user needing the SUID, 439 check this option to avoid users to be notified about missing 440 permissions. 441 442config SELINUX 443 bool "Support NSA Security Enhanced Linux" 444 default n 445 select PLATFORM_LINUX 446 help 447 Enable support for SELinux in applets ls, ps, and id. Also provide 448 the option of compiling in SELinux applets. 449 450 If you do not have a complete SELinux userland installed, this stuff 451 will not compile. Specifially, libselinux 1.28 or better is 452 directly required by busybox. If the installation is located in a 453 non-standard directory, provide it by invoking make as follows: 454 CFLAGS=-I<libselinux-include-path> \ 455 LDFLAGS=-L<libselinux-lib-path> \ 456 make 457 458 Most people will leave this set to 'N'. 459 460config FEATURE_PREFER_APPLETS 461 bool "exec prefers applets" 462 default n 463 help 464 This is an experimental option which directs applets about to 465 call 'exec' to try and find an applicable busybox applet before 466 searching the PATH. This is typically done by exec'ing 467 /proc/self/exe. 468 This may affect shell, find -exec, xargs and similar applets. 469 They will use applets even if /bin/<applet> -> busybox link 470 is missing (or is not a link to busybox). However, this causes 471 problems in chroot jails without mounted /proc and with ps/top 472 (command name can be shown as 'exe' for applets started this way). 473 474config BUSYBOX_EXEC_PATH 475 string "Path to BusyBox executable" 476 default "/proc/self/exe" 477 help 478 When Busybox applets need to run other busybox applets, BusyBox 479 sometimes needs to exec() itself. When the /proc filesystem is 480 mounted, /proc/self/exe always points to the currently running 481 executable. If you haven't got /proc, set this to wherever you 482 want to run BusyBox from. 483 484# These are auto-selected by other options 485 486config FEATURE_SYSLOG 487 bool #No description makes it a hidden option 488 default n 489 #help 490 # This option is auto-selected when you select any applet which may 491 # send its output to syslog. You do not need to select it manually. 492 493config FEATURE_HAVE_RPC 494 bool #No description makes it a hidden option 495 default n 496 #help 497 # This is automatically selected if any of enabled applets need it. 498 # You do not need to select it manually. 499 500endmenu 501 502menu 'Build Options' 503 504config STATIC 505 bool "Build BusyBox as a static binary (no shared libs)" 506 default n 507 help 508 If you want to build a static BusyBox binary, which does not 509 use or require any shared libraries, then enable this option. 510 This can cause BusyBox to be considerably larger, so you should 511 leave this option false unless you have a good reason (i.e. 512 your target platform does not support shared libraries, or 513 you are building an initrd which doesn't need anything but 514 BusyBox, etc). 515 516 Most people will leave this set to 'N'. 517 518config PIE 519 bool "Build BusyBox as a position independent executable" 520 default n 521 depends on !STATIC 522 help 523 Hardened code option. PIE binaries are loaded at a different 524 address at each invocation. This has some overhead, 525 particularly on x86-32 which is short on registers. 526 527 Most people will leave this set to 'N'. 528 529config NOMMU 530 bool "Force NOMMU build" 531 default n 532 help 533 Busybox tries to detect whether architecture it is being 534 built against supports MMU or not. If this detection fails, 535 or if you want to build NOMMU version of busybox for testing, 536 you may force NOMMU build here. 537 538 Most people will leave this set to 'N'. 539 540# PIE can be made to work with BUILD_LIBBUSYBOX, but currently 541# build system does not support that 542config BUILD_LIBBUSYBOX 543 bool "Build shared libbusybox" 544 default n 545 depends on !FEATURE_PREFER_APPLETS && !PIE && !STATIC 546 help 547 Build a shared library libbusybox.so.N.N.N which contains all 548 busybox code. 549 550 This feature allows every applet to be built as a tiny 551 separate executable. Enabling it for "one big busybox binary" 552 approach serves no purpose and increases code size. 553 You should almost certainly say "no" to this. 554 555### config FEATURE_FULL_LIBBUSYBOX 556### bool "Feature-complete libbusybox" 557### default n if !FEATURE_SHARED_BUSYBOX 558### depends on BUILD_LIBBUSYBOX 559### help 560### Build a libbusybox with the complete feature-set, disregarding 561### the actually selected config. 562### 563### Normally, libbusybox will only contain the features which are 564### used by busybox itself. If you plan to write a separate 565### standalone application which uses libbusybox say 'Y'. 566### 567### Note: libbusybox is GPL, not LGPL, and exports no stable API that 568### might act as a copyright barrier. We can and will modify the 569### exported function set between releases (even minor version number 570### changes), and happily break out-of-tree features. 571### 572### Say 'N' if in doubt. 573 574config FEATURE_INDIVIDUAL 575 bool "Produce a binary for each applet, linked against libbusybox" 576 default y 577 depends on BUILD_LIBBUSYBOX 578 help 579 If your CPU architecture doesn't allow for sharing text/rodata 580 sections of running binaries, but allows for runtime dynamic 581 libraries, this option will allow you to reduce memory footprint 582 when you have many different applets running at once. 583 584 If your CPU architecture allows for sharing text/rodata, 585 having single binary is more optimal. 586 587 Each applet will be a tiny program, dynamically linked 588 against libbusybox.so.N.N.N. 589 590 You need to have a working dynamic linker. 591 592config FEATURE_SHARED_BUSYBOX 593 bool "Produce additional busybox binary linked against libbusybox" 594 default y 595 depends on BUILD_LIBBUSYBOX 596 help 597 Build busybox, dynamically linked against libbusybox.so.N.N.N. 598 599 You need to have a working dynamic linker. 600 601### config BUILD_AT_ONCE 602### bool "Compile all sources at once" 603### default n 604### help 605### Normally each source-file is compiled with one invocation of 606### the compiler. 607### If you set this option, all sources are compiled at once. 608### This gives the compiler more opportunities to optimize which can 609### result in smaller and/or faster binaries. 610### 611### Setting this option will consume alot of memory, e.g. if you 612### enable all applets with all features, gcc uses more than 300MB 613### RAM during compilation of busybox. 614### 615### This option is most likely only beneficial for newer compilers 616### such as gcc-4.1 and above. 617### 618### Say 'N' unless you know what you are doing. 619 620config LFS 621 bool "Build with Large File Support (for accessing files > 2 GB)" 622 default y 623 help 624 If you want to build BusyBox with large file support, then enable 625 this option. This will have no effect if your kernel or your C 626 library lacks large file support for large files. Some of the 627 programs that can benefit from large file support include dd, gzip, 628 cp, mount, tar, and many others. If you want to access files larger 629 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'. 630 631config CROSS_COMPILER_PREFIX 632 string "Cross Compiler prefix" 633 default "" 634 help 635 If you want to build BusyBox with a cross compiler, then you 636 will need to set this to the cross-compiler prefix, for example, 637 "i386-uclibc-". 638 639 Note that CROSS_COMPILE environment variable or 640 "make CROSS_COMPILE=xxx ..." will override this selection. 641 642 Native builds leave this empty. 643 644config SYSROOT 645 string "Path to sysroot" 646 default "" 647 help 648 If you want to build BusyBox with a cross compiler, then you 649 might also need to specify where /usr/include and /usr/lib 650 will be found. 651 652 For example, BusyBox can be built against an installed 653 Android NDK, platform version 9, for ARM ABI with 654 655 CONFIG_SYSROOT=/opt/android-ndk/platforms/android-9/arch-arm 656 657 Native builds leave this empty. 658 659config EXTRA_CFLAGS 660 string "Additional CFLAGS" 661 default "" 662 help 663 Additional CFLAGS to pass to the compiler verbatim. 664 665config EXTRA_LDFLAGS 666 string "Additional LDFLAGS" 667 default "" 668 help 669 Additional LDFLAGS to pass to the linker verbatim. 670 671config EXTRA_LDLIBS 672 string "Additional LDLIBS" 673 default "" 674 help 675 Additional LDLIBS to pass to the linker with -l. 676 677endmenu 678 679menu 'Debugging Options' 680 681config DEBUG 682 bool "Build BusyBox with extra Debugging symbols" 683 default n 684 help 685 Say Y here if you wish to examine BusyBox internals while applets are 686 running. This increases the size of the binary considerably, and 687 should only be used when doing development. If you are doing 688 development and want to debug BusyBox, answer Y. 689 690 Most people should answer N. 691 692config DEBUG_PESSIMIZE 693 bool "Disable compiler optimizations" 694 default n 695 depends on DEBUG 696 help 697 The compiler's optimization of source code can eliminate and reorder 698 code, resulting in an executable that's hard to understand when 699 stepping through it with a debugger. This switches it off, resulting 700 in a much bigger executable that more closely matches the source 701 code. 702 703config DEBUG_SANITIZE 704 bool "Enable runtime sanitizers (ASAN/LSAN/USAN/etc...)" 705 default n 706 help 707 Say Y here if you want to enable runtime sanitizers. These help 708 catch bad memory accesses (e.g. buffer overflows), but will make 709 the executable larger and slow down runtime a bit. 710 711 If you aren't developing/testing busybox, say N here. 712 713config UNIT_TEST 714 bool "Build unit tests" 715 default n 716 help 717 Say Y here if you want to build unit tests (both the framework and 718 test cases) as a Busybox applet. This results in bigger code, so you 719 probably don't want this option in production builds. 720 721config WERROR 722 bool "Abort compilation on any warning" 723 default n 724 help 725 Selecting this will add -Werror to gcc command line. 726 727 Most people should answer N. 728 729choice 730 prompt "Additional debugging library" 731 default NO_DEBUG_LIB 732 help 733 Using an additional debugging library will make BusyBox become 734 considerable larger and will cause it to run more slowly. You 735 should always leave this option disabled for production use. 736 737 dmalloc support: 738 ---------------- 739 This enables compiling with dmalloc ( http://dmalloc.com/ ) 740 which is an excellent public domain mem leak and malloc problem 741 detector. To enable dmalloc, before running busybox you will 742 want to properly set your environment, for example: 743 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile 744 The 'debug=' value is generated using the following command 745 dmalloc -p log-stats -p log-non-free -p log-bad-space \ 746 -p log-elapsed-time -p check-fence -p check-heap \ 747 -p check-lists -p check-blank -p check-funcs -p realloc-copy \ 748 -p allow-free-null 749 750 Electric-fence support: 751 ----------------------- 752 This enables compiling with Electric-fence support. Electric 753 fence is another very useful malloc debugging library which uses 754 your computer's virtual memory hardware to detect illegal memory 755 accesses. This support will make BusyBox be considerable larger 756 and run slower, so you should leave this option disabled unless 757 you are hunting a hard to find memory problem. 758 759 760config NO_DEBUG_LIB 761 bool "None" 762 763config DMALLOC 764 bool "Dmalloc" 765 766config EFENCE 767 bool "Electric-fence" 768 769endchoice 770 771endmenu 772 773menu 'Installation Options ("make install" behavior)' 774 775choice 776 prompt "What kind of applet links to install" 777 default INSTALL_APPLET_SYMLINKS 778 help 779 Choose what kind of links to applets are created by "make install". 780 781config INSTALL_APPLET_SYMLINKS 782 bool "as soft-links" 783 help 784 Install applets as soft-links to the busybox binary. This needs some 785 free inodes on the filesystem, but might help with filesystem 786 generators that can't cope with hard-links. 787 788config INSTALL_APPLET_HARDLINKS 789 bool "as hard-links" 790 help 791 Install applets as hard-links to the busybox binary. This might 792 count on a filesystem with few inodes. 793 794config INSTALL_APPLET_SCRIPT_WRAPPERS 795 bool "as script wrappers" 796 help 797 Install applets as script wrappers that call the busybox binary. 798 799config INSTALL_APPLET_DONT 800 bool "not installed" 801 help 802 Do not install applet links. Useful when you plan to use 803 busybox --install for installing links, or plan to use 804 a standalone shell and thus don't need applet links. 805 806endchoice 807 808choice 809 prompt "/bin/sh applet link" 810 default INSTALL_SH_APPLET_SYMLINK 811 depends on INSTALL_APPLET_SCRIPT_WRAPPERS 812 help 813 Choose how you install /bin/sh applet link. 814 815config INSTALL_SH_APPLET_SYMLINK 816 bool "as soft-link" 817 help 818 Install /bin/sh applet as soft-link to the busybox binary. 819 820config INSTALL_SH_APPLET_HARDLINK 821 bool "as hard-link" 822 help 823 Install /bin/sh applet as hard-link to the busybox binary. 824 825config INSTALL_SH_APPLET_SCRIPT_WRAPPER 826 bool "as script wrapper" 827 help 828 Install /bin/sh applet as script wrapper that calls 829 the busybox binary. 830 831endchoice 832 833config PREFIX 834 string "BusyBox installation prefix" 835 default "./_install" 836 help 837 Define your directory to install BusyBox files/subdirs in. 838 839endmenu 840 841source libbb/Config.in 842 843endmenu 844 845comment "Applets" 846 847source archival/Config.in 848source coreutils/Config.in 849source console-tools/Config.in 850source debianutils/Config.in 851source editors/Config.in 852source findutils/Config.in 853source init/Config.in 854source loginutils/Config.in 855source e2fsprogs/Config.in 856source modutils/Config.in 857source util-linux/Config.in 858source miscutils/Config.in 859source networking/Config.in 860source printutils/Config.in 861source mailutils/Config.in 862source procps/Config.in 863source runit/Config.in 864source selinux/Config.in 865source shell/Config.in 866source sysklogd/Config.in 867