From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date: Mon, 23 Feb 2015 13:40:00 +0100
Subject: [Buildroot] [autobuild.buildroot.net] Build results for
 2015-02-22
In-Reply-To: <54EB1E71.5030904@imgtec.com>
References: <20150223073016.4059D1027D4@stock.ovh.net>
 <54EAFCAA.5070506@imgtec.com>
 <20150223122336.2de88dc7@free-electrons.com>
 <54EB1E71.5030904@imgtec.com>
Message-ID: <20150223134000.7f3f3c5b@free-electrons.com>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Dear Vicente Olivert Riera,

On Mon, 23 Feb 2015 13:34:57 +0100, Vicente Olivert Riera wrote:

> Yes, that was fixes 6 months ago by this commit:
> 
> https://gitlab.com/bminor/mesa-mesa/commit/5a4e0f3873657d874eb5ff52819f42ea38d54b91.patch
> 
> We could do a similar fix for openswan. The problem is I can't reproduce
> the failure so I wouldn't be able to test that fix to check if it works
> or not.

Did you try something like:

while true ; do make openswan-dirclean ; make openswan || exit 1 ; done

with a high BR2_JLEVEL value ? That's typically how I manage to
reproduce parallel build issues.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com