Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9906] genimage: Disk full
Date: Tue, 30 May 2017 21:16:57 +0000	[thread overview]
Message-ID: <bug-9906-163-jl90vC8k1f@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9906-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9906

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|ASSIGNED                    |RESOLVED
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Alexander, Peter, All,

> I just did a test build with 2017.05-rc3 here and raspberrypi3_64_defconfig,
> and I end up with ~15 MB used in the fat partition[...]

Ditto.

> If you change the configuration significantly then it isn't surprising
> that you may need to tweak other things, so this IMHO isn't a bug.

Agreed.

I'm closing this report. If you still have the issue with a stock
Buildroot rpi3_64 defconfig, please re-open.

Thanks! :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-05-30 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 12:09 [Buildroot] [Bug 9906] New: genimage: Disk full bugzilla at busybox.net
2017-05-30 19:49 ` [Buildroot] [Bug 9906] " bugzilla at busybox.net
2017-05-30 21:16 ` bugzilla at busybox.net [this message]
2017-05-31  7:26 ` bugzilla at busybox.net
2017-06-04  9:28 ` bugzilla at busybox.net

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=bug-9906-163-jl90vC8k1f@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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