Opened 11 years ago

Closed 11 years ago

#37874 closed defect (fixed)

qt4-mac @4.8.4_3: fails to build on osx 10.8.2 with xcode 4.6

Reported by: mavaugha@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: qt4-mac

Description

I just tried a clean build of qt4-mac on my mac running mountain lion (10.8.2) after having updated xcode to 4.6, and the build fails:

null-60334b211b03:~ Michelle$ sudo port install qt4-mac +debug +universal
--->  Computing dependencies for qt4-mac
--->  Fetching archive for qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_3+debug+universal.darwin_12.i386-x86_64.tbz2 from http://packages.macports.org/qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_3+debug+universal.darwin_12.i386-x86_64.tbz2 from http://lil.fr.packages.macports.org/qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_3+debug+universal.darwin_12.i386-x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/qt4-mac
--->  Fetching distfiles for qt4-mac
--->  Verifying checksum(s) for qt4-mac
--->  Extracting qt4-mac
--->  Applying patches to qt4-mac
--->  Configuring qt4-mac
--->  Building qt4-mac
Error: org.macports.build for port qt4-mac returned: command execution failed
Please see the log file for port qt4-mac for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt4-mac/qt4-mac/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port qt4-mac failed

I attached the log (hope this might be a quick fix...)

Attachments (1)

main.log (2.1 MB) - added by mavaugha@… 11 years ago.

Change History (7)

Changed 11 years ago by mavaugha@…

Attachment: main.log added

comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)

Cc: michaelld@… removed
Keywords: mountain lion Xcode removed
Milestone: MacPorts 2.1.3
Owner: changed from macports-tickets@… to michaelld@…
Summary: qt4-mac fails to build on osx 10.8.2 with xcode 4.6qt4-mac @4.8.4_3: fails to build on osx 10.8.2 with xcode 4.6

Thanks for the ticket.

comment:2 Changed 11 years ago by michaelld (Michael Dickens)

What do the following return:

/usr/bin/clang++ -v
xcodebuild -version
uname -a

comment:3 Changed 11 years ago by mavaugha@…

Here's what I get:

Michelles-MacBook-Pro:~ Michelle$ /usr/bin/clang++ -v 
Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.2.0
Thread model: posix
Michelles-MacBook-Pro:~ Michelle$ xcodebuild -version
Xcode 4.6
Build version 4H127
Michelles-MacBook-Pro:~ Michelle$ uname -a
Darwin Michelles-MacBook-Pro.local 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64

comment:4 Changed 11 years ago by michaelld (Michael Dickens)

I'm compiling qt4-mac right now with (I think) the same OS, compiler, and variants as yours; hopefully it will break in the same way and I can figure a way around it quickly. The error is:

:info:build In file included from kernel/qcursor_mac.mm:52:
:info:build In file included from ../../include/QtGui/private/qt_cocoa_helpers_mac_p.h:1:
:info:build ../../include/QtGui/private/../../../src/gui/kernel/qt_cocoa_helpers_mac_p.h:158:10: error: extra qualification on member 'TabletProximityRec'
:info:build struct ::TabletProximityRec;
:info:build        ~~^

which is odd. It seems like the new CLANG is not liking the syntax that the prior CLANG was OK with. This struct is defined in CarbonEvents.h:14277, which is part of the HIToolbox, which is part of Carbon. There's nothing special about the way this struct is defined, in either header. I'll post back once I know more.

comment:5 Changed 11 years ago by michaelld (Michael Dickens)

I have replicated this error; yay! Now, trying to fix it ...

comment:6 Changed 11 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

Fixed in r102396. You'll need to do a "sudo port selfupdate" or whatever command you do to get updates.

Note: See TracTickets for help on using tickets.