On Monday 11 June 2012 13:17:35 Gerfried Fuchs wrote: --cut-- > > A possibly annoying detail for the debug package (pgadmin3-dbg)would be > > that a single build is used for both debug and non-debug variants and > > build with -O2 (-ggdb -O2) which may lead to unexpected results for the > > debugging variant [1]. Of course, this could be dealt with by > > unconditionally building the source package with -O0. > > I wonder how that is any different to any other -dbg package. From > what I understand, -O2 is the default to compile with unless > DEB_BUILD_OPTIONS does include "noopt". See debian-policy 4.9.1 > "debian/rules and DEB_BUILD_OPTIONS".
Yeah, I know... I only mentioned that because pgadmin3's --enable-debug uses "-g -O0" for building for some reason, thus in some rare cases -O0 vs. -02 might make a difference for -g (although I don't have any hard data to back up such a claim for pgadmin3 sources), while on the vast majority of packages -O2 combined with -g would be just fine. Thus handling it on per package basis is not entirely baseless. Whatever, I guess that "punishing" the -dbg package with -g -O2 instead of "punishing" the non-dbg package with -O0, is an appropriate course of action. Users can always fetch the source and rebuild with "noopt" if they want to skip -O2 optimizations while debugging. -- pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
