How can I get usable debugsource packages?

[Dave Plater]

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>
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?
Thanks
Dave P

Apologies for possible double posting but I have had a nightmare with emails to the list for the last couple of weeks.
Regards
Dave P

[Andreas Jaeger]

Post by Dave Plater
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
<debuginfo>
<enable/>
</debuginfo>
|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"?

Andreas

[Hans-Peter Jansen]

Post by Andreas Jaeger

Post by Dave Plater
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
<debuginfo>
<enable/>
</debuginfo>

I think, adding %debug_package to the spec file is enough.

Post by Andreas Jaeger

Post by Dave Plater
|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

[Dave Plater]

Post by Hans-Peter Jansen

Post by Andreas Jaeger

Post by Dave Plater
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
<debuginfo>
<enable/>
</debuginfo>

I think, adding %debug_package to the spec file is enough.

Post by Andreas Jaeger

Post by Dave Plater
|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,
%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

The culprit turned out to be configure.ac. I made a patch to modify the
build flags, it was overriding everything. I also had to add
--enable-debug to %configure as well.
Thanks
Dave P