← Commit list

c8e41157a

Rob Landley
Rob Landley
2006-01-19
SOURCE BUG Duration: 16s

Subject

Update readme and install.sh usage message.

SOURCE BUG

This commit was genuinely broken at the time (not related to our build system): scripts/config/mkconfigs.c (2005-08-01 - 2006-10-05 arasi) uretilen bbconfigopts.h icine .config satirlarini kacissiz, ham newline'larla gömüyordu - gecerli C degildi, busybox'un kendi bb_mkdep araci bile parse edemiyordu (7d219aab7 ile duzeltildi, mkconfigs shell scripte cevrildi)

→ Bu hatanin tam hikayesini ve duzeltme diffini gor

Binary

No binary (build failed)

Architecture & Compiler Flags

Architecture: x86_64-linux-gnu Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04.3) 11.4.0

—

Build Log

(log yok)

Commit Diff GitHub →

README+10 -9
@@ -5,12 +5,12 @@ What is busybox:
BusyBox combines tiny versions of many common UNIX utilities into a single
small executable. It provides minimalist replacements for most of the
- utilities you usually find in bzip2, coreutils, file, findutils, gawk, grep,
- inetutils, modutils, net-tools, procps, sed, shadow, sysklogd, sysvinit, tar,
- util-linux, and vim. The utilities in BusyBox often have fewer options than
- their full-featured cousins; however, the options that are included provide
- the expected functionality and behave very much like their larger
- counterparts.
+ utilities you usually find in bzip2, coreutils, e2fsprogs, file, findutils,
+ gawk, grep, inetutils, less, modutils, net-tools, procps, sed, shadow,
+ sysklogd, sysvinit, tar, util-linux, and vim. The utilities in BusyBox
+ often have fewer options than their full-featured cousins; however, the
+ options that are included provide the expected functionality and behave
+ very much like their larger counterparts.
BusyBox has been written with size-optimization and limited resources in
mind, both to produce small binaries and to reduce run-time memory usage.
@@ -50,9 +50,10 @@ Using busybox:
The build automatically generates a file "busybox.links", which is used by
'make install' to create symlinks to the BusyBox binary for all compiled in
- commands. Use the PREFIX environment variable to specify where to install
- the busybox binary and symlink forest. (i.e., 'make PREFIX=/tmp/foo install',
- or 'make PREFIX=/tmp/foo install-hardlinks' if you prefer hard links.)
+ commands. This uses the PREFIX environment variable to specify where to
+ install, and installs hardlinks or symlinks depending on the configuration
+ preferences. (You can also manually run the install script at
+ "applets/install.sh").
----------------
applets/install.sh+1 -1
@@ -5,7 +5,7 @@ export LC_CTYPE=POSIX
prefix=${1}
if [ -z "$prefix" ]; then
- echo "No installation directory, aborting."
+ echo "usage: applets/install.sh DESTINATION [--symlinks/--hardlinks]"
exit 1;
fi
h=`sort busybox.links | uniq`