From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Build error from time to time
Date: Wed, 12 Feb 2014 17:49:21 +0100 [thread overview]
Message-ID: <52FBA611.2000402@mind.be> (raw)
In-Reply-To: <CANxTyt52zqEJk=tbSW7Mc6J369kqRBNUaqSat3q_sAh+2_WecA@mail.gmail.com>
On 12/02/14 16:30, Danomi Manchego wrote:
> On Wed, Feb 12, 2014 at 2:10 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 11/02/14 16:23, Sagaert Johan wrote:
>> Took me a while to find it, but it looks like a parallel build issue in
>> nettle combined with ccache. In the configure step, all the *.d files are
>> created as empty files. These files are included unconditionally in the
>> Makefile, so you get an error if they don't exist. Unfortunately, ccache
>> does an unlink() just before creating the new file, so there is a tiny
>> window of time where the file doesn't exist. It looks like you have a
>> filesystem where this window is relatively large (NFS?), which is why you
>> see the problem and others don't.
>>
>> This is a tough nut to crack fundamentally.
>>
>> * You could say that nettle's behaviour of including empty dependency
>> files is bad. To overcome that, a - can be added in front of the include.
>>
>> * You can say the behaviour of ccache is bad. The unlink could be removed
>> there, except in the case of CCACHE_HARDLINK because it is not possible
>> to create a hardlink to an existing file.
>>
>> Any suggestions on how to proceed?
>
> Would forcing non-parallel build (MAKE1) get around this issue?
Yes, but that would be a pity since nettle is fairly large.
Regards,
Arnout
> Danomi -
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-02-12 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 15:23 [Buildroot] Build error from time to time Sagaert Johan
2014-02-12 7:10 ` Arnout Vandecappelle
2014-02-12 15:30 ` Danomi Manchego
2014-02-12 16:49 ` Arnout Vandecappelle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FBA611.2000402@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox