From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5780] New: spurious build failure because it cannot remove ubinize.cfg
Date: Fri, 7 Dec 2012 11:11:29 +0000 (UTC) [thread overview]
Message-ID: <bug-5780-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5780
Summary: spurious build failure because it cannot remove
ubinize.cfg
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: arved at arved.at
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4694
--> https://bugs.busybox.net/attachment.cgi?id=4694
patch to create ubinize.cfg in BUILD_DIR
Our jenkins sometimes (especially after cleaning the workspace) because it
fails to remove the file ubinize.cfg
The code in fs/ubifs/ubi.mk generates a ubinize.cfg in "." and removes it
later.
I think it is better to generate the ubinize.cfg in an absolute path like
BUILD_DIR and not remove it at all as it gets regenerated with every
regenerated image anyway.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-12-07 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:11 bugzilla at busybox.net [this message]
2013-05-26 22:14 ` [Buildroot] [Bug 5780] spurious build failure because it cannot remove ubinize.cfg bugzilla at busybox.net
2013-10-30 22:05 ` bugzilla at busybox.net
2014-02-09 6:18 ` 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-5780-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 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.