[MacPorts] #14991: gnucash --disable-debug and --disable profile configure options turn ON debugging and profiling

[MacPorts]

#14991: gnucash --disable-debug and --disable profile configure options turn ON
debugging and profiling
-----------------------------+----------------------------------------------
 Reporter:  mp at dpj.sent.com  |       Owner:  macports-tickets at lists.macosforge.org
     Type:  defect           |      Status:  new                                  
 Priority:  Normal           |   Milestone:  Port Bugs                            
Component:  ports            |     Version:  1.6.0                                
 Keywords:                   |  
-----------------------------+----------------------------------------------
 gnucash kept leaving "gmon.out" files strewn over my drive (it took me a
 while to figure out that it gnucash was the culprit!) It turns out that
 the current Portfile passes the --disable-debug and --disable profile
 configure options which seem to have the opposite effect: see the below
 output from "port -v configure gnucash +without_hbci" (note "-g" and "-pg"
 in CFLAGS and LDFLAGS)

 {{{
   Options detected/selected
   -------------------------
   gnucash version ...... : 2.2.4
   Build for host ....... : i386-apple-darwin9.2.2
   Optional components....: ofx
   Extra Warnings ....... :  -Wdeclaration-after-statement -Wno-pointer-
 sign -D_FORTIFY_SOURCE=2
   CPPFLAGS ............. : -I/opt/local/include
   CFLAGS ............... :  -Wdeclaration-after-statement -Wno-pointer-
 sign -D_FORTIFY_SOURCE=2  -g  -O2 -pg -Wall -Wunused -Wmissing-prototypes
 -Wmissing-declarations  -Wno-unused
   LDFLAGS .............. : -L/opt/local/lib -g -pg
   prefix.................: /opt/local
   QOF support ...........: internal
   QOF location ..........: internal
   QOF library dir .......:
   QOF backend config ....: /opt/local/gnucash/xml/qsf
 }}}

 Once these two configure options are removed, gnucash no longer compiles
 with debugging and profiling, and gmon.out files are a thing of the past.

 I'll attach a Portfile patch, but this assumes that the patch on ticket
 #14893 has already been applied. Sorry, but I wasn't sure what to do about
 two unrelated patches for the one file...

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14991>
MacPorts </projects/macports>
Ports system for Mac OS