From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9386] ubinize fails with or without custom config
Date: Thu, 27 Oct 2016 21:24:38 +0000 [thread overview]
Message-ID: <bug-9386-163-BOHrC0yVkk@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9386-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9386
--- Comment #4 from Andrey Yurovsky <yurovsky@gmail.com> ---
Ok, I've reproduced it with your defconfig and I've left all paths in here. To
build I just ran:
make atmel_sama5d4_xplained_defconfig
make
And in the end the output is:
>>> Generating root filesystem image rootfs.ubi
rm -f /home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
rm -f
/home/ayurovsky/dev/build-system/buildroot/output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM
rm -f /home/ayurovsky/dev/build-system/buildroot/output/build/_users_table.txt
echo '#!/bin/sh' >
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
echo "set -e" >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
echo "chown -h -R 0:0 /home/ayurovsky/dev/build-system/buildroot/output/target"
>> /home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
printf ' \n' >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_users_table.txt
PATH="/home/ayurovsky/dev/build-system/buildroot/output/host/bin:/home/ayurovsky/dev/build-system/buildroot/output/host/sbin:/home/ayurovsky/dev/build-system/buildroot/output/host/usr/bin:/home/ayurovsky/dev/build-system/buildroot/output/host/usr/sbin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/ayurovsky/.local/bin:/home/ayurovsky/bin"
/home/ayurovsky/dev/build-system/buildroot/support/scripts/mkusers
/home/ayurovsky/dev/build-system/buildroot/output/build/_users_table.txt
/home/ayurovsky/dev/build-system/buildroot/output/target >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
cat system/device_table.txt >
/home/ayurovsky/dev/build-system/buildroot/output/build/_device_table.txt
printf ' /bin/busybox f 4755 0 0 - - - - -\n
/dev/console c 622 0 0 5 1 - - -\n\n' >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_device_table.txt
echo "/home/ayurovsky/dev/build-system/buildroot/output/host/usr/bin/makedevs
-d /home/ayurovsky/dev/build-system/buildroot/output/build/_device_table.txt
/home/ayurovsky/dev/build-system/buildroot/output/target" >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
printf ' /usr/bin/install -m 0644 fs/ubifs/ubinize.cfg
/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg\n
/usr/bin/sed -i -e
'\''s;BR2_ROOTFS_UBIFS_PATH;/home/ayurovsky/dev/build-system/buildroot/output/images/rootfs.ubifs;'\''
/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg\n
/home/ayurovsky/dev/build-system/buildroot/output/host/usr/sbin/ubinize -o
/home/ayurovsky/dev/build-system/buildroot/output/images/rootfs.ubi -m 0x1000
-p 0x40000
/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg\n rm
/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg\n' >>
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
chmod a+x /home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
PATH="/home/ayurovsky/dev/build-system/buildroot/output/host/bin:/home/ayurovsky/dev/build-system/buildroot/output/host/sbin:/home/ayurovsky/dev/build-system/buildroot/output/host/usr/bin:/home/ayurovsky/dev/build-system/buildroot/output/host/usr/sbin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/ayurovsky/.local/bin:/home/ayurovsky/bin"
/home/ayurovsky/dev/build-system/buildroot/output/host/usr/bin/fakeroot --
/home/ayurovsky/dev/build-system/buildroot/output/build/_fakeroot.fs
rootdir=/home/ayurovsky/dev/build-system/buildroot/output/target
table='/home/ayurovsky/dev/build-system/buildroot/output/build/_device_table.txt'
iniparser: cannot open
/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg
ubinize: error!: cannot load the input ini file
"/home/ayurovsky/dev/build-system/buildroot/output/build/ubinize.cfg"
/usr/bin/install -m 0644 support/misc/target-dir-warning.txt
/home/ayurovsky/dev/build-system/buildroot/output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-10-27 21:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 18:20 [Buildroot] [Bug 9386] New: ubinize fails with or without custom config bugzilla at busybox.net
2016-10-27 20:30 ` [Buildroot] [Bug 9386] " bugzilla at busybox.net
2016-10-27 20:39 ` bugzilla at busybox.net
2016-10-27 21:22 ` bugzilla at busybox.net
2016-10-27 21:24 ` bugzilla at busybox.net [this message]
2016-10-27 21:56 ` bugzilla at busybox.net
2016-10-27 22:13 ` bugzilla at busybox.net
2016-10-27 23:08 ` bugzilla at busybox.net
2016-10-28 18:42 ` bugzilla at busybox.net
2016-10-28 21:31 ` bugzilla at busybox.net
2016-10-29 7:45 ` bugzilla at busybox.net
2016-10-29 8:28 ` bugzilla at busybox.net
2016-11-03 20:40 ` bugzilla at busybox.net
2016-11-23 12:37 ` bugzilla at busybox.net
2016-11-23 12:41 ` bugzilla at busybox.net
2016-11-23 12:56 ` bugzilla at busybox.net
2016-11-27 20:29 ` bugzilla at busybox.net
2016-11-28 18:06 ` 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-9386-163-BOHrC0yVkk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.