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 9096] New: rootfs.ubi not created
Date: Thu, 21 Jul 2016 09:10:35 +0000	[thread overview]
Message-ID: <bug-9096-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9096
           Summary: rootfs.ubi not created
           Product: buildroot
           Version: 2016.02
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: matthias.wieloch at few-bauer.de
                CC: buildroot at uclibc.org
  Target Milestone: ---

When I select to create an embedded UBI Image with buildroot 2016.02 and newer
the creation fails with:
iniparser: cannot open <BR_PATH>/output/build/ubinize.cfg
ubinize: error!: cannot load the input ini file
"/<BR_PATH>/output/build/ubinize.cfg"

With buildroot 2015.08.1 the creation still works.

I know this tells me that the ubinize.cfg is missing but in all versions
following line is added to the fakeroot script _fakeroot.fs
        /usr/bin/install -m 0644 fs/ubifs/ubinize.cfg
<BR_PATH>/output/build/ubinize.cfg ;

I tested it with default configs for sama5d4_xplained.

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

             reply	other threads:[~2016-07-21  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21  9:10 bugzilla at busybox.net [this message]
2016-07-21  9:53 ` [Buildroot] [Bug 9096] rootfs.ubi not created bugzilla at busybox.net
2016-09-12 14:42 ` 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-9096-163@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