When using scripts/env, .config is most likely a symbolic link
pointing to env/.config. Previously the symbolic link got
copied as-is into the SDK tarball, leading to a dangling .config
symlink on the target system which prevented the SDK from working.
SVN-Revision: 29927
rm -rf \
$(SDK_BUILD_DIR)/target/linux/*/files \
$(SDK_BUILD_DIR)/target/linux/*/patches
- $(CP) \
+ $(CP) -L \
$(TOPDIR)/LICENSE \
$(TOPDIR)/rules.mk \
$(TOPDIR)/.config \