Bug 5780 - spurious build failure because it cannot remove ubinize.cfg
Summary: spurious build failure because it cannot remove ubinize.cfg
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: Yann E. MORIN
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-07 11:11 UTC by Tilman Keskinöz
Modified: 2014-02-09 06:18 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
patch to create ubinize.cfg in BUILD_DIR (801 bytes, application/octet-stream)
2012-12-07 11:11 UTC, Tilman Keskinöz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tilman Keskinöz 2012-12-07 11:11:28 UTC 
Created attachment 4694 [details]
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.
Comment 1 Thomas Petazzoni 2013-10-30 22:05:24 UTC 
This would be fixed if we decide to commit:

Subject: [Buildroot] [PATCH v2] fs/ubi: add option to use custom ubinize config file
Date: Sun, 15 Sep 2013 21:04:07 -0400

http://patchwork.ozlabs.org/patch/275088/
Comment 2 Thomas De Schampheleire 2014-02-09 06:18:29 UTC 
Fixed with commit 
http://git.buildroot.net/buildroot/commit/?id=74a0f963ed364f90b937fc24f06573f5512c612c