← Commit list

e8ce0626d

Denis Vlasenko
Denis Vlasenko
2007-02-03
FAILED Duration: 11s

Subject

s/PREFIX/CONFIG_PREFIX/

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 →

INSTALL+2 -2
@@ -5,7 +5,7 @@ The BusyBox build process is similar to the Linux kernel build:
make menuconfig # This creates a file called ".config"
make # This creates the "busybox" executable
- make install # or make PREFIX=/path/from/root install
+ make install # or make CONFIG_PREFIX=/path/from/root install
The full list of configuration and install options is available by typing:
@@ -114,7 +114,7 @@ configuration step, as in:
make O=/some/empty/directory allyesconfig
cd /some/empty/directory
make
- make PREFIX=. install
+ make CONFIG_PREFIX=. install
More Information:
=================
Makefile.help+1 -1
@@ -27,7 +27,7 @@ help:
@echo ' make SED="$(objtree)/sed"'
@echo
@echo 'Installation:'
- @echo ' install - install busybox into $(PREFIX)'
+ @echo ' install - install busybox into $(CONFIG_PREFIX)'
@echo ' uninstall'
@echo
@echo 'Development:'
README+4 -4
@@ -50,10 +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. 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").
+ commands. This uses the CONFIG_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").
----------------
docs/busybox_header.pod+5 -5
@@ -33,11 +33,11 @@ menuconfig' to select the functionality that you wish to enable. Then run
After the compile has finished, you should use 'make install' to install
BusyBox. This will install the 'bin/busybox' binary, in the target directory
-specified by PREFIX. PREFIX can be set when configuring BusyBox, or you can
-specify an alternative location at install time (i.e., with a command line
-like 'make PREFIX=/tmp/foo install'). If you enabled any applet installation
-scheme (either as symlinks or hardlinks), these will also be installed in
-the location pointed to by PREFIX.
+specified by CONFIG_PREFIX. CONFIG_PREFIX can be set when configuring BusyBox,
+or you can specify an alternative location at install time (i.e., with a
+command line like 'make CONFIG_PREFIX=/tmp/foo install'). If you enabled
+any applet installation scheme (either as symlinks or hardlinks), these will
+also be installed in the location pointed to by CONFIG_PREFIX.
=head1 USAGE
examples/bootfloppy/bootfloppy.txt+1 -1
@@ -72,7 +72,7 @@ The following steps will create a root file system.
- Install the Busybox binary and accompanying symlinks:
(chdir to busybox directory)
- make PREFIX=(path to)loop/ install
+ make CONFIG_PREFIX=(path to)loop/ install
- Make device files in /dev:
examples/bootfloppy/mkrootfs.sh+1 -1
@@ -76,7 +76,7 @@ cd $BASE_DIR
cd $BUSYBOX_DIR
make distclean
make CC=$BASE_DIR/$UCLIBC_DIR/extra/gcc-uClibc/i386-uclibc-gcc
-make PREFIX=$BASE_DIR/$TARGET_DIR install
+make CONFIG_PREFIX=$BASE_DIR/$TARGET_DIR install
cd $BASE_DIR
examples/busybox.spec+1 -1
@@ -34,7 +34,7 @@ make
%Install
rm -rf $RPM_BUILD_ROOT
-make PREFIX=$RPM_BUILD_ROOT install
+make CONFIG_PREFIX=$RPM_BUILD_ROOT install
%Clean
rm -rf $RPM_BUILD_ROOT