Post

Replies

Boosts

Views

Activity

Comment on FTS and firmlinks
The solution that was proposed by the Apple engineer was to use getattrlist (2) with ATTR_CMNEXT_NOFIRMLINKPATH. Regardless the current implementation already breaks POSIX and UNIX filesystem interfaces: FTS will fail to traverse /System/Volumes/Data/ correctly unless initialized with FTS_NOCHDIR and so will many tools that use it without this flag such as ls (1) and find (1). Should I re-file this as a bug in ls (1) and find (1) instead?
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’22
Comment on Recommended approach to generate the Exported Symbols List file
By the target executable I meant the executable that static library is linked with. In my case it needs to re-export symbols because the executable will load "plugins" in runtime. The static library is the binary dependency supplied by a 3rd party and cannot be converted to a dynamic library that could be linked both with the executable and plugins.
Replies
Boosts
Views
Activity
Jun ’24
Comment on FTS and firmlinks
The solution that was proposed by the Apple engineer was to use getattrlist (2) with ATTR_CMNEXT_NOFIRMLINKPATH. Regardless the current implementation already breaks POSIX and UNIX filesystem interfaces: FTS will fail to traverse /System/Volumes/Data/ correctly unless initialized with FTS_NOCHDIR and so will many tools that use it without this flag such as ls (1) and find (1). Should I re-file this as a bug in ls (1) and find (1) instead?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’22