[PyQt] Non-compiliable PyQt on Mac

[Phil Thompson]

On Fri, 16 Jul 2010 10:13:47 +0200, Oleksandr Iakovliev
<yshurik at gmail.com>
wrote:
> Hi,
> 
> I have installed SIP successfully, but configure of PyQt4 fails:
> 
> PyQt-mac-gpl-4.7.4
> 
> # python configure.py 
> Determining the layout of your Qt installation...
> This is the GPL version of PyQt 4.7.4 (licensed under the GNU General
> Public
> License) for Python 2.6.1 on darwin.
> 
> Type '2' to view the GPL v2 license.
> Type '3' to view the GPL v3 license.
> Type 'yes' to accept the terms of the license.
> Type 'no' to decline the terms of the license.
> 
> Do you accept the terms of the license? yes
> Checking to see if the QtGui module should be built...
> An internal error occured.  Please report all the output from the
program,
> including the following traceback, to support at riverbankcomputing.com.
> Traceback (most recent call last):
>  File "configure.py", line 2138, in <module>
>    main()
>  File "configure.py", line 2088, in main
>    pyqt.check_modules()
>  File "configure.py", line 352, in check_modules
>    check_module("QtGui", "qwidget.h", "new QWidget()")
>  File "configure.py", line 1344, in check_module
>    if check_api(incfile, test, mname,
>    extra_include_dirs=extra_include_dirs, extra_lib_dirs=extra_lib_dirs,
>    extra_libs=extra_libs):
>  File "configure.py", line 1376, in check_api
>    extra_lib_dirs=extra_lib_dirs, extra_libs=extra_libs)
>  File "configure.py", line 1189, in compile_qt_program
>    exe, build = makefile.build_command(name)
>  File "/Library/Python/2.6/site-packages/sipconfig.py", line 1820, in
>  build_command
>    build.append(self.required_string("CXX"))
>  File "/Library/Python/2.6/site-packages/sipconfig.py", line 914, in
>  required_string
>    raise ValueError("\"%s\" must have a non-empty value" % name)
> ValueError: "CXX" must have a non-empty value
> 
> Additonaly:
> # qmake -v
> QMake version 2.01a
> Using Qt version 4.6.3 in /Library/Frameworks
> 
> Any Qt programs can be built without any problem
> 
> ps: update of SIP to new one 4.10.4 did not help.
> 
> Any clue?

No. I can't reproduce the problem and haven't had any other bug reports.

Phil