| Summary: | spurious build failure because it cannot remove ubinize.cfg | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Tilman Keskinöz <arved> |
| Component: | Other | Assignee: | Yann E. MORIN <yann.morin.1998> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | patch to create ubinize.cfg in BUILD_DIR | ||
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/ |
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.