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 22:13:41 +0000 [thread overview]
Message-ID: <bug-9386-163-vKCIcoIbKH@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 #6 from Andrey Yurovsky <yurovsky@gmail.com> ---
I have SELinux but it's set to 'permissive' right now, nothing else is
configured differently from a standard Fedora 24 install.
ubi.mk rm's the ubinize.cfg file, if I comment that out it'll be left behind
and then:
$ stat output/build/ubinize.cfg
File: 'output/build/ubinize.cfg'
Size: 124 Blocks: 8 IO Block: 4096 regular file
Device: fd03h/64771d Inode: 1596887 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ayurovsky) Gid: ( 1000/ayurovsky)
Context: unconfined_u:object_r:user_home_t:s0
Access: 2016-10-27 15:10:37.142923074 -0700
Modify: 2016-10-27 15:10:37.142923074 -0700
Change: 2016-10-27 15:10:37.142923074 -0700
Birth: -
What I can't explain is that if instead I leave everything alone and just
insert a line like:
stat $(BUILD_DIR)/ubinize.cf
in ubi.mk (in its _CMD), stat reports that the path doesn't exist (as does
ubinize). So why does it exist if I remove the last line in _CMD (the rm) but
it doesn't exist after the first line (the $(INSTALL)) ... ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-10-27 22:13 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
2016-10-27 21:56 ` bugzilla at busybox.net
2016-10-27 22:13 ` bugzilla at busybox.net [this message]
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-vKCIcoIbKH@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