how long does it take to build gcc45?

Ryan Schmidt ryandesign at macports.org
Wed Dec 8 12:18:16 PST 2010


On Dec 8, 2010, at 14:15, Gabriele Kahlout wrote:

> On 8 December 2010 15:10, Ryan Schmidt wrote:
> 
>> The answer provided on your Stack Overflow question is correct. No FSF release of gcc (e.g. the ports gcc46, gcc45, gcc44, gcc43, gcc42, gcc41, gcc40) recognizes the -arch switch. Only Apple's specially modified versions of gcc supplied with Xcode support that option.
>> 
> 
> It's not a port but qt. Or actually I see there is a port: qt4-mac @4.7.1 (aqua), which is the same version I have.
> 
> Omitting the -wall option from the makefile I get (on this qt demo project):
> torrent-build simpatico$ make
> g++ -c -pipe -g -gdwarf-2  -Wall -W -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/local/Qt4.7/mkspecs/macx-g++ -I../torrent -I/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/usr/include/QtCore -I/Library/Frameworks/QtNetwork.framework/Versions/4/Headers -I/usr/include/QtNetwork -I/Library/Frameworks/QtGui.framework/Versions/4/Headers -I/usr/include/QtGui -I/usr/include -I. -I. -I../torrent -I. -F/Library/Frameworks -o main.o ../torrent/main.cpp
> In file included from /Library/Frameworks/QtCore.framework/Headers/qnamespace.h:45:0,
>                  from /Library/Frameworks/QtCore.framework/Headers/qobjectdefs.h:45,
>                  from /Library/Frameworks/QtCore.framework/Headers/qobject.h:47,
>                  from /Library/Frameworks/QtCore.framework/Headers/qcoreapplication.h:45,
>                  from /Library/Frameworks/QtGui.framework/Versions/4/Headers/qapplication.h:45,
>                  from /Library/Frameworks/QtGui.framework/Versions/4/Headers/QApplication:1,
>                  from ../torrent/main.cpp:40:
> /Library/Frameworks/QtCore.framework/Headers/qglobal.h:288:2: error: #error "You are building a 64-bit application, but using a 32-bit version of Qt. Check your build configuration."

You were probably adding "-arch i386" to try to overcome this error? If so, use "-m32" instead.


>>  If you are getting that error when building a port, it's still likely a bug in that port, so a ticket should be filed.
> 
> What should I do?

I see "/usr/local" in your output above. Be aware that it is not supported to have things installed in /usr/local when using MacPorts as it can interfere, so I recommend you uninstall whatever you have in /usr/local and use MacPorts equivalents, i.e. use the qt4-mac port.



More information about the macports-users mailing list