On Tuesday 27 October 2009, 11:49:58 Andreas Jaeger wrote:
On Tuesday 27 October 2009 11:47:38 Dave Plater wrote:
Hi, I've googled and searched other package's spec files and build logs but I cant seem to get usable debugsource rpms for my home:plater rosegarden-qt4 package. I've written : <debuginfo> <enable/> </debuginfo>
I think, adding %debug_package to the spec file is enough.
into my project meta but I still get empty debugsource packages : |Preparing packages for installation...
rosegarden-qt4-debuginfo-10.02-60.1 rosegarden-qt4-debugsource-10.02-60.1 rosegarden-qt4-10.02-60.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ! ! rosegarden-qt4-debugsource-10.02-60.1.x86_64.rpm: no debug sources, deleting package ! rosegarden-qt4-debuginfo-10.02-60.1.x86_64.rpm: WARNING: this probably means the debug information is invalid
What am I missing?
Are you using $RPM_OPT_FLAGS which includes "-g" to produce debug output? Or do you remove the debug output somewhere using "strip"?
If rosegarden use qmake, then that's the culprit. qmake is notorious at boiling it's own kind of (letter-) soup. Here's what I do for python-qt4, which relies on qmake for _some_ parts, in order to get the full debug info: %build sed -i "s/designer plugin release warn/designer plugin debug warn/" designer/python.pro-in export CXXFLAGS="$RPM_OPT_FLAGS" export CFLAGS="$RPM_OPT_FLAGS" python configure.py --confirm-license --qsci-api --debug CFLAGS+="$RPM_OPT_FLAGS" CXXFLAGS+="$RPM_OPT_FLAGS" # fix the qmake generated Makefiles, if they exist for mf in qpy/*/Makefile designer/Makefile; do [ -f "$mf" ] && sed -i "s/^CFLAGS.*$/CFLAGS = $RPM_OPT_FLAGS \$(DEFINES)/g" $mf done make %{?jobs:-j %jobs} I hope, you get an idea.. Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org