| Summary: | mkostemp() not implemented | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Pseudo | Reporter: | Richard Tollerton <rich.tollerton> |
| Component: | pseudo | Assignee: | Seebs <seebs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | juro.bystricky, ross.burton, stephano, yp.pseudo.watcher, yp.watcher |
| Version: | unspecified | ||
| Target Milestone: | 2.5 M3 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Tollerton
2017-12-22 23:29:03 UTC
I wonder if we could just intercept __gen_tempname()? But yes, the mkostemp() family probably needs to get added. Doesn't look like anything fancy. In my defense, I'm pretty sure everything even similar to mkstemp() should never be used in the first place. I'll try to get these added. Have implemented the family of related mk*temp* functions and pushed changes to master for experimentation. The functions were added to pseudo in sha d7c31a25e4b02af0c64e6be0b4b0a9ac4ffc9da2, and oe-core upgraded to that sha in 7c3df6782bbd5b623dcb6ee8a9bc914926640cdd. |