commit 5f0d1aa3863201994f433e6eaab63fba364dd872
author Adriana Kobylak <anoo@us.ibm.com> Mon Jul 08 14:16:15 2019 -0500
committer Adriana Kobylak <anoo@us.ibm.com> Mon Jul 08 14:20:44 2019 -0500
tree f14b39d673700ace7c44aa1889012ef39d123467
parent 5a8aa48c0f4365a4622ddde9265711b501dfb921

build-setup: Remove setting BB_ENV_EXTRAWHITE

The BB_ENV_EXTRAWHITE variable already has MACHINE included as default:

BB_ENV_EXTRAWHITE=ALL_PROXY BBPATH_EXTRA BB_NO_NETWORK BB_NUMBER_THREADS BB_SETSCENE_ENFORCE BB_SRCREV_POLICY DISTRO FTPS_PROXY FTP_PROXY GIT_PROXY_COMMAND HTTPS_PROXY HTTP_PROXY MACHINE NO_PROXY PARALLEL_MAKE SCREENDIR SDKMACHINE SOCKS5_PASSWD SOCKS5_USER SSH_AGENT_PID SSH_AUTH_SOCK STAMPS_DIR TCLIBC TCMODE all_proxy ftp_proxy ftps_proxy http_proxy https_proxy no_proxy

In addition, the script was trying to append "MACHINE" incorrectly,
the $BB_ENV_EXTRAWHITE is a script variable which had not been defined
before, not the actual environment variable as when you'd get when executing
from the command line. Therefore, the BB_ENV_EXTRAWHITE variable was being
cleared and just being set to "MACHINE".

Tested:
  Printed the environment after setting MACHINE and verified
  BB_ENV_EXTRAWHITE had MACHINE in it:

  + export MACHINE=qemux86-64
  + MACHINE=qemux86-64
  + env
  MACHINE=qemux86-64
  BB_ENV_EXTRAWHITE=ALL_PROXY BBPATH_EXTRA BB_NO_NETWORK BB_NUMBER_THREADS BB_SETSCENE_ENFORCE BB_SRCREV_POLICY DISTRO FTPS_PROXY FTP_PROXY GIT_PROXY_COMMAND HTTPS_PROXY HTTP_PROXY MACHINE

Change-Id: I03a198218c7a87f6b706a6a2fdc503188bf8ea15
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>