From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Mon, 11 Nov 2013 23:21:17 +0100 Subject: [Buildroot] [PATCH] gcc: don't patch gcc if there are no patches to apply In-Reply-To: <52815482.4010802@mind.be> (Arnout Vandecappelle's message of "Mon, 11 Nov 2013 23:04:50 +0100") References: <1384180596-15125-1-git-send-email-mjonker@synopsys.com> <87d2m661nc.fsf@dell.be.48ers.dk> <52815482.4010802@mind.be> Message-ID: <878uwu60ma.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Arnout" == Arnout Vandecappelle writes: > On 11/11/13 22:59, Peter Korsgaard wrote: >>>>>>> "Mischa" == Mischa Jonker writes: >> >>> While the generic package handler checks for a directory with patches >>> before starting apply-patches.sh, this is not the case for gcc: the >>> script is called, even if there is no directory with patches. This results >>> into a build failure, as apply-patches exits with error code 1 if the >>> directory doesn't exist. >> >> Arnout already posted another patch solving the same issue, but I prefer >> this one for 2013.11 - So committed, thanks. > Should I refresh my patch on top of this or do you want to drop my patch? I think it's still a better aproach long term (especially if/when we get out-of-tree support), so yes - Please do. -- Bye, Peter Korsgaard