Mailinglist Archive: opensuse-buildservice (273 mails)

< Previous Next >
Re: [opensuse-buildservice] How to use %debug_package
  • From: Cristian Morales Vega <cmorve69@xxxxxxxx>
  • Date: Tue, 27 Jan 2009 09:52:50 +0100
  • Message-id: <8235e6f40901270052xe3d2609hb6bd3d651234873d@xxxxxxxxxxxxxx>
2009/1/27 Petr Uzel <petr.uzel@xxxxxxx>:
On Tue, Jan 27, 2009 at 06:28:55AM +0100, Cristian Morales Vega wrote:
Then I think you need to add "-g" to the build flags. The vorbisgain
makefile doesn't seems to add it and I'm not sure if the BS will add
it automatically when you add <debuginfo> (if doesn't, probably it should?).

If you use $RPM_OPT_FLAGS, the package is built with -g.

Sure? It's true when I build locally (because of
/usr/lib/rpm/x86_64-linux/macros, I suppose). But the Factory BS
config says:
$ osc meta prjconf openSUSE:Factory | fgrep -i Optflags
Optflags: i586 -march=i586 -mtune=i686 -fmessage-length=0
Optflags: i686 -march=i686 -mtune=i686 -fmessage-length=0
Optflags: x86_64 -fmessage-length=0
Optflags: ppc -fmessage-length=0
Optflags: ppc64 -fmessage-length=0
Optflags: ia64 -fmessage-length=0
Optflags: s390 -fmessage-length=0
Optflags: s390x -fmessage-length=0
Optflags: * -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
-funwind-tables -fasynchronous-unwind-tables

Then Matthias spec file says CFLAGS="$RPM_OPT_FLAGS" and the build log
shows it's expanded to CFLAGS='-fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
And he said that even when added %debug_package and changed the
"install-strip" rule he received the
"vorbisgain-debugsource-0.34-8.x86_64.rpm: no debug sources, deleting
package" error. Showing no debuginfo was available in the final binary.
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups