Makefile: don't export O to the environment

Several projects use the kernel style O=<dir> syntax to build out of tree,
and atleast uClibc doesn't check that it was explictly passed on the command
line, so setting it in the environment breaks the build.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
Peter Korsgaard 2013-01-14 10:02:29 +01:00
parent 0bc0da0bb4
commit 1300cb5562
2 changed files with 2 additions and 2 deletions

View File

@ -291,7 +291,7 @@ export TARGET_DIR
export STAGING_DIR export STAGING_DIR
export HOST_DIR export HOST_DIR
export BINARIES_DIR export BINARIES_DIR
export BASE_DIR O # O and BASE_DIR are the same export BASE_DIR
############################################################# #############################################################
# #

View File

@ -43,7 +43,7 @@ there are a few ways to customize the resulting target filesystem.
xref:generic-package-reference[] xref:generic-package-reference[]
- +BINARIES_DIR+: the place where all binary files (aka images) are - +BINARIES_DIR+: the place where all binary files (aka images) are
stored stored
- +BASE_DIR+ (or +O+): the base output directory - +BASE_DIR+: the base output directory
* A special package, 'customize', stored in +package/customize+ can be * A special package, 'customize', stored in +package/customize+ can be
used. You can put all the files that you want to see in the final used. You can put all the files that you want to see in the final