Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#37994 closed defect (fixed)

qt4-mac: Objective-C block (^) support not detected

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: leopard Cc: heathn@…, EnekoGotzon
Port: qt4-mac

Description

Unable to upgrade qt4-mac 4.8.4_3 to 4.8.4_4 on Leopard:

:info:configure Determining system architecture... (Darwin:9.8.0:i386)
:info:configure     'macosx' is supported
:info:configure System architecture: 'macosx'
:info:configure CPATH support detected
:info:configure LIBRARY_PATH support detected
:info:configure compiler flag -fconstant-cfstrings support detected
:info:configure Objective-C block (^) support not detected
:info:configure error: The compiler (/usr/bin/g++-4.0) does not seem to support the Objective-C blocks (^), which are used by Qt when compiling on Mac OS X.

Attachments (1)

main.log (57.3 KB) - added by ryandesign (Ryan Carsten Schmidt) 12 years ago.

Download all attachments as: .zip

Change History (12)

Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: main.log added

comment:1 Changed 12 years ago by michaelld (Michael Dickens)

I take it that compiling using Apple's GCC 4.0 worked OK on 4.8.4_3 before the change I made to checking for ObjC blocks? If that's the case, then I need to figure out a better way to test for this condition.

comment:2 Changed 12 years ago by heathn@…

Cc: heathn@… added

Cc Me!

comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Yes, 4.8.4_3 was installed normally without needing to change anything.

comment:4 Changed 12 years ago by larryv (Lawrence Velázquez)

Does Apple’s GCC 4.0 actually support C blocks? I thought they were a Clang extension.

Unless you’re suggesting that lack of support shouldn’t actually be a failure state.

Last edited 12 years ago by larryv (Lawrence Velázquez) (previous) (diff)

comment:5 Changed 12 years ago by EnekoGotzon

Please, Cc me too! Thanks

comment:6 Changed 12 years ago by neverpanic (Clemens Lang)

Cc: enekogotzon@… added

To get Cc'd on a ticket, press the CcMe! button at the top. I have done this for you.

comment:7 Changed 12 years ago by michaelld (Michael Dickens)

Should be fixed in r102936. Please someone confirm, and then I'll close this ticket.

comment:8 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Anyone who experienced the problem, then ran selfupdate and tried again without manually cleaning, would still fail, because r102936 did not change the Portfile, and therefore MacPorts wouldn't know that it should clean before trying again. So I made a small unrelated change to the Portfile in r102951 to trigger the automatic clean.

comment:9 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

This does fix the problem for me; thanks.

comment:10 Changed 12 years ago by michaelld (Michael Dickens)

Yeah; I forgot that "minor" detail; thanks for dealing with it!

comment:11 Changed 12 years ago by EnekoGotzon

After an unsuccessful attempt, apparently due to my computer was overworking, the port has been correctly installed. Problem solved. Another victory. Congrats. Thenk you very much :)

Note: See TracTickets for help on using tickets.