#67590 closed defect (fixed)

openexr @3.1.8: build failures: 10.8 and earlier (unknown type name 'dispatch_semaphore_t'); ppc/gcc: ('isnan' was not declared in this scope)

Reported by: barracuda156 Owned by: mascguy (Christopher Nielsen)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: powerpc, leopard, snowleopard, lion, mountainlion Cc:
Port: openexr

Description (last modified by mascguy (Christopher Nielsen))

For Intel, 10.8 and earlier:

work/openexr-3.1.8/src/lib/IlmThread/IlmThreadSemaphore.h:64:13: error: unknown type name 'dispatch_semaphore_t'

For PPC, 10.5/10.6:

work/openexr-3.1.8/src/test/OpenEXRCoreTest/compression.cpp:162:10: error: 'isnan' was not declared in this scope; did you mean 'std::isnan'?

Also See:

Change History (11)

comment:1 Changed 11 months ago by mascguy (Christopher Nielsen)

Description: modified (diff)
Keywords: lion mountainlion added
Summary: openexr now broken with GCC due to cmath issue: error: 'isnan' was not declared in this scope; did you mean 'std::isnan'?openexr @3.1.8: build failures: 10.8 and earlier (unknown type name 'dispatch_semaphore_t'); ppc/gcc: ('isnan' was not declared in this scope)

comment:2 Changed 11 months ago by mascguy (Christopher Nielsen)

Description: modified (diff)

comment:4 in reply to:  3 ; Changed 11 months ago by mascguy (Christopher Nielsen)

Replying to barracuda156:

isnan error fixed in https://github.com/AcademySoftwareFoundation/openexr/commit/729f42648d5a522bba0d8f52061c0368a5d31bbb

Can you also let them know about the error related to dispatch_semaphore_t, occurring for 10.8 and earlier?

comment:5 in reply to:  4 Changed 11 months ago by barracuda156

Replying to mascguy:

Replying to barracuda156:

isnan error fixed in https://github.com/AcademySoftwareFoundation/openexr/commit/729f42648d5a522bba0d8f52061c0368a5d31bbb

Can you also let them know about the error related to dispatch_semaphore_t, occurring for 10.8 and earlier?

Sure: https://github.com/AcademySoftwareFoundation/openexr/issues/1449

(I can also take a look into this, but not tonight.)

comment:6 in reply to:  4 Changed 11 months ago by barracuda156

Replying to mascguy:

Replying to barracuda156:

isnan error fixed in https://github.com/AcademySoftwareFoundation/openexr/commit/729f42648d5a522bba0d8f52061c0368a5d31bbb

Can you also let them know about the error related to dispatch_semaphore_t, occurring for 10.8 and earlier?

We might have fixed that already, but commit went past released version somehow. Could you check if this works? https://github.com/AcademySoftwareFoundation/openexr/commit/6773e77bade3b4d8284881e477bee9c1f91c0f8b

comment:7 Changed 11 months ago by Christopher Nielsen <mascguy@…>

In 1393fcec9ada1be1f7b4216a043092f11e2c804d/macports-ports (master):

openexr: add patch for macos ver defs; use mp-libcxx for 10.7/10.8
See: #67590

comment:8 Changed 11 months ago by mascguy (Christopher Nielsen)

Queued builds of openexr dependents, for 10.6 thru 10.8.

comment:9 in reply to:  8 ; Changed 11 months ago by barracuda156

Replying to mascguy:

Queued builds of openexr dependents, for 10.6 thru 10.8.

I guess 10.7–10.8 did not run? https://ports.macports.org/port/openexr/details Given that 10.6 is all good now.

comment:10 in reply to:  9 ; Changed 11 months ago by mascguy (Christopher Nielsen)

Replying to barracuda156:

Replying to mascguy:

Queued builds of openexr dependents, for 10.6 thru 10.8.

I guess 10.7–10.8 did not run? https://ports.macports.org/port/openexr/details Given that 10.6 is all good now.

No, the buildbots had a significant backlog yesterday, and may still be catching up today. (Haven't looked.)

So I expect it to be built within the next 24-ish hours.

comment:11 in reply to:  10 Changed 11 months ago by mascguy (Christopher Nielsen)

Resolution: fixed
Status: assignedclosed

Replying to mascguy:

Replying to barracuda156:

Replying to mascguy:

Queued builds of openexr dependents, for 10.6 thru 10.8.

I guess 10.7–10.8 did not run? https://ports.macports.org/port/openexr/details Given that 10.6 is all good now.

No, the buildbots had a significant backlog yesterday, and may still be catching up today. (Haven't looked.)

So I expect it to be built within the next 24-ish hours.

All good now, closing as fixed.

Note: See TracTickets for help on using tickets.