Hello. I would like to update openSUSE qwt package. 6.1.0 builds and installs fine, but if it is packaged, postbuild check issue will be got:
[ 23s] ERROR: RPATH "/usr/local/qwt-6.1.0/lib" on /home/abuild/rpmbuild/BUILDROOT/qwt6-6.1.0-0.x86_64/usr/lib64/qt4/plugins/designer/libqwt_designer_plugin.so is not allowed
[ 23s] ERROR: RPATH "/usr/local/qwt-6.1.0/lib" on /home/abuild/rpmbuild/BUILDROOT/qwt6-6.1.0-0.x86_64/usr/lib64/qt4/plugins/designer/libqwt_designer_plugin.so is not allowed
(see attachment for full log)
We build it via:
qmake \ QWT_INSTALL_PREFIX=%{_prefix} \ CONFIG+=QwtDll CONFIG+=QwtDesigner CONFIG+=QwtExamples -after \ QMAKE_CXXFLAGS="%{optflags}" \ target.path=%{_libdir} \ headers.path=%{_includedir}/%{name} \ qwtspec.path=%{_datadir}/%{name}/features \ qwtmathmlspec.path=%{_datadir}/%{name}/features \ doc.path=%{_docdir}/%{name}-devel-doc
make %{?_smp_mflags}
mkdir -p %{buildroot}/%{_libdir}/qt4/plugins/designer
mv -v %{buildroot}/%{_libdir}/libqwt_designer_plugin.so %{buildroot}/%{_libdir}/qt4/plugins/designer/
Could you help me to fix it somehow please?
Anonymous
In Qwt 6.1 the designer plugin is already built with RPATH ( see designer.pro ). Maybe this is the difference, why the postbuild step fails.
Guess you can simply remove setting the RPATH from your postbuild steps as it seems to be obsolete.
As I understand it isn't setting but checking of RPATH. I don't really know if package with a check disabled could be accepted into the distro. Is another way to prevent it?
Last edit: DAP 2013-08-09
Then you have to remove the line with "QMAKE_RPATHDIR" from designer.pro.
QWT_INSTALL_PREFIX is set to /usr/ via qmake option and
QMAKE_RPATHDIR *= $${QWT_INSTALL_LIBS}
QWT_INSTALL_LIBS = $${QWT_INSTALL_PREFIX}/lib
And finally it is installed correctly but RPATH finds it as /usr/local
Imho it is a kind of magic.
Anyway a patch attached works fine. Great thanks!
PS There are no CHANGES file. Is it a feature? :)
Last edit: DAP 2013-08-09
For changes see: http://qwt.sourceforge.net/qwtchangelog.html
Thanks. So should it be closed?
Still relevant for 6.1.2 :(
That was me again.