aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/feeds
diff options
context:
space:
mode:
authorJo-Philipp Wich <jo@mein.io>2016-06-24 13:32:22 +0200
committerJo-Philipp Wich <jo@mein.io>2016-06-24 13:43:40 +0200
commit59e98b27c93d282edb62fad756fd1c1e587c067f (patch)
treeb8f603fe6fa2ecf226b1cecaa8ab4f576ae85bad /scripts/feeds
parent819cf75c408e1f03f95d516d87361d0047079d5b (diff)
downloadupstream-59e98b27c93d282edb62fad756fd1c1e587c067f.tar.gz
upstream-59e98b27c93d282edb62fad756fd1c1e587c067f.tar.bz2
upstream-59e98b27c93d282edb62fad756fd1c1e587c067f.zip
ar71xx: fix legacy image building
After the conversion from legacy device profiles to the newer profile information embedded in the image building code, the legacy recipes got triggered twice with different eval depths, leading to shell syntax errors when processing certain images. The double processing was caused by the remaining Image/Build macro in legacy.mk which serves as main entry point for the new style image build code in conjunction with the newly introduced LegacyDevice/* macros which caused the legacy image build fallback code to kick in. In order to fix the issue, rework all legacy macros to work under the legacy image build wrapper and remove the Image/Build macro of legacy.mk to prevent legacy profiles getting executed in the context of the new build code. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Diffstat (limited to 'scripts/feeds')
0 files changed, 0 insertions, 0 deletions