Bug 12449 - mkostemp() not implemented
Summary: mkostemp() not implemented
Status: RESOLVED FIXED
Alias: None
Product: Pseudo
Classification: Yocto Project Subprojects
Component: pseudo (show other bugs)
Version: unspecified
Hardware: All Multiple
: High normal
Target Milestone: 2.5 M3
Assignee: Seebs
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-12-22 23:29 UTC by Richard Tollerton
Modified: 2018-03-15 08:02 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
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 Richard Tollerton 2017-12-22 23:29:03 UTC 
pseudo is intercepting mkstemp() but not mkostemp(). This causes permissions for coreutils `sed -i` to break, and probably a couple of other build-related commands too.

In principle, any function which glibc implements under the hood as __gen_tempname() probably needs to get implemented.
Comment 1 Seebs 2018-02-26 19:02:40 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.
Comment 2 Seebs 2018-02-26 20:48:33 UTC 
Have implemented the family of related mk*temp* functions and pushed changes to master for experimentation.
Comment 3 Ross Burton 2018-03-15 08:02:22 UTC 
The functions were added to pseudo in sha d7c31a25e4b02af0c64e6be0b4b0a9ac4ffc9da2, and oe-core upgraded to that sha in 7c3df6782bbd5b623dcb6ee8a9bc914926640cdd.