From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] gc20 no space left issue
Date: Sun, 09 Oct 2016 21:20:13 +0200 [thread overview]
Message-ID: <87vax1ib2q.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20161009204509.49fc7a4b@free-electrons.com> (Thomas Petazzoni's message of "Sun, 9 Oct 2016 20:45:09 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello Peter,
> Due to a lack of disk space, gcc20 reports some build failures, such as:
> http://autobuild.buildroot.net/results/6a2/6a2d4cb453128c0aa1fc9ed0ac04ec7c8306e7e1/
> Could you see if you can fix this ?
I dropped some of the bigger tarballs from instance-*/dl, so now there's
11G free.
> Perhaps we should start thinking about a way of ignoring the build
> results caused by a lack of disk space ?
Perhaps, if we can come up with a simple & robust way of detecting
it. On the other hand, this doesn't happen that often - And when it does
it is good to get notified about it.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-10-09 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 18:45 [Buildroot] gc20 no space left issue Thomas Petazzoni
2016-10-09 19:20 ` Peter Korsgaard [this message]
2016-10-09 19:53 ` Thomas Petazzoni
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=87vax1ib2q.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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