Opened 14 years ago

Closed 14 years ago

#2400 closed bug (fixed)

FTBFS: sipcorepart0 on Debian/Lenny

Reported by: hamish Owned by: nobody
Priority: major: does not work as expected Milestone: Version 1.5.0
Component: Build/Install Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: Debian
Platform Version: Debian/Lenny Awaiting user input: no

Description

Hi,

I'm trying to compile trunk on Debian/Lenny using the supplied debian/control.lenny + debuild.

I'm getting this error. no idea what it means. 

...
[ 63%] Building CXX object python/CMakeFiles/python_module_qgis_core.dir/core/sipcorepart0.cpp.o
/usr/local/src/qgis/svn/trunk/python/../src/core/symbology-ng/qgssymbolv2.h: In member function 'QgsSymbolV2RenderContext& QgsSymbolV2RenderContext::operator=(const QgsSymbolV2RenderContext&)':
/usr/local/src/qgis/svn/trunk/python/../src/core/symbology-ng/qgssymbolv2.h:104: error: non-static reference member 'QgsRenderContext& QgsSymbolV2RenderContext::mRenderContext', can't use default assignment operator
sipcorepart0.cpp: In function 'void assign_QgsSymbolV2RenderContext(void*, const void*)':
sipcorepart0.cpp:13600: note: synthesized method 'QgsSymbolV2RenderContext& QgsSymbolV2RenderContext::operator=(const QgsSymbolV2RenderContext&)' first required here 
make[3]: *** [python/CMakeFiles/python_module_qgis_core.dir/core/sipcorepart0.cpp.o] Error 1
make[3]: Leaving directory `/usr/local/src/qgis/svn/trunk/debian/build'
make[2]: *** [python/CMakeFiles/python_module_qgis_core.dir/all] Error 2
make[2]: Leaving directory `/usr/local/src/qgis/svn/trunk/debian/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/local/src/qgis/svn/trunk/debian/build'
make: *** [build-stamp] Error 2
debuild: fatal error at line 1301:

?

thanks, Hamish

Change History (2)

comment:1 by hamish, 14 years ago

Summary: FTBFS: sipcorepart0 on Debian/Lennt → FTBFS: sipcorepart0 on Debian/Lenny

comment:2 by wonder, 14 years ago

Resolution: → fixed
Status: new → closed

This should have been fixed in r12848.

Note: See TracTickets for help on using tickets.