Indeed, those warnings were seen on a Mac running Yosemite.
> On Oct 24, 2014, at 2:04 PM, Paul Hargrove wrote:
>
> I can shed some light on these warnings.
>
> sem_init() and sem_destroy() are POSIX-defined interfaces for UNNAMED
> semaphores.
> There are also POSX
I can shed some light on these warnings.
sem_init() and sem_destroy() are POSIX-defined interfaces for UNNAMED
semaphores.
There are also POSX interfaces, sem_{open,close,unlink}(), that operate on
NAMED semaphores.
See for more info:
Yes, will have a look at it next week.
Thanks
Edgar
On 10/24/2014 12:01 PM, Jeff Squyres (jsquyres) wrote:
Edgar -- can you have a look?
On Oct 24, 2014, at 12:04 PM, Ralph Castain wrote:
I’m not sure who owns that framework, but I’m seeing this warning:
Edgar -- can you have a look?
On Oct 24, 2014, at 12:04 PM, Ralph Castain wrote:
> I’m not sure who owns that framework, but I’m seeing this warning:
>
> sharedfp_sm_file_open.c: In function 'mca_sharedfp_sm_file_open':
> sharedfp_sm_file_open.c:159:5: warning: 'sem_init'
I’m not sure who owns that framework, but I’m seeing this warning:
sharedfp_sm_file_open.c: In function 'mca_sharedfp_sm_file_open':
sharedfp_sm_file_open.c:159:5: warning: 'sem_init' is deprecated (declared at
/usr/include/sys/semaphore.h:55) [-Wdeprecated-declarations]