summaryrefslogtreecommitdiff
path: root/board/omap1510inn
diff options
context:
space:
mode:
authorGrant Likely <grant.likely@secretlab.ca>2007-11-21 09:19:37 -0700
committerGrant Likely <grant.likely@secretlab.ca>2007-11-21 09:19:37 -0700
commit98e2867cc85409b919f862e6c16026461ec955df (patch)
tree8043a3f013ff7341a8394b81f72626bca3378ef2 /board/omap1510inn
parent4a43719a7738712811d822ca8125427b27a55cdc (diff)
downloadu-boot-imx-98e2867cc85409b919f862e6c16026461ec955df.zip
u-boot-imx-98e2867cc85409b919f862e6c16026461ec955df.tar.gz
u-boot-imx-98e2867cc85409b919f862e6c16026461ec955df.tar.bz2
[BUILD] Remove libraries when updating autoconf.mk
Fix library problems caused by conditional compilation. Using autoconf.mk to decide which files to compile has caused a problem when changing configuration from one board to another without clearing out the library (*.a) files. It used to be that the linker was always passed the same list of .o files when building the .a files. However, that is not longer true with conditional compilation. Now, a different board config will have a different file list passed to the linker. The problem occurs when a library has already been built and the board config is changed. Since the linker will update instead of replace a preexisting library, then if the file list changes to remove some object files the old objects will still exist in the library. The solution is to remove all old library files when autoconf.mk is made. Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Diffstat (limited to 'board/omap1510inn')
0 files changed, 0 insertions, 0 deletions