qgis @1.8.0: error: 'connectNotify' is a private member of 'QgsMapLayerRegistry'

[EJFielding (Eric Fielding)]

I was running "port upgrade outdated", and it found broken files and ports. It decided to rebuild qgis:

--->  Found 43 broken file(s), matching files to ports
--->  Found 2 broken port(s), determining rebuild order
--->  Rebuilding in order
     qgis @1.8.0 +postgis2+postgresql91+python27
     py27-matplotlib-basemap @1.0.6 

It tried twice, but it failed both times. I attach the main.log file

[ryandesign (Ryan Carsten Schmidt)]

The first error I see in the log is:

:info:build [ 70%] [ 70%] /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis/qgis/work/qgis-1.8.0/build/python/core/sipcorepart2.cpp:33967:30: error: 'connectNotify' is a private member of 'QgsMapLayerRegistry'
:info:build         QgsMapLayerRegistry::connectNotify(a0);
:info:build                              ^
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_qgis/qgis/work/qgis-1.8.0/python/../src/core/qgsmaplayerregistry.h:176:10: note: declared private here
:info:build     void connectNotify( const char * signal );
:info:build          ^

[Veence (Vincent)]

Yes, I know something was wrong, because I stumbled on the same error, but thought it has to do with my own installation. I don’t understand what caused the compilation to suddenly fail, since the reported error is not tied in any way to some extern library. Strange. I’ll dive into it and try to fix it ASAP.

[Veence (Vincent)]

Should be fixed in r110754. Please try again.

[EJFielding (Eric Fielding)]

Replying to vince@…:

Should be fixed in r110754. Please try again.

Great! It works now for me.

[Veence (Vincent)]

Excellent. Enjoy!

[denis.rouzaud@…]

This error can be avoided by using SIP 4.14.6. Versions 4.14.7 and 4.15.1 produce this error.

See ​http://www.qgis.org/api/INSTALL.html at the SIP section.

[Veence (Vincent)]

There is still something wrong with QGis 2.0