[Fwd: Re: [patch] More gcc 4.2.3 compilation fixes]

[Andreas Köhler]

Hi Jerry,

Am Sonntag, den 30.12.2007, 20:21 -0500 schrieb Jerry Quinn:
> Sorry, didn't cc the list before
> 
> -------- Original Message --------
> From: - Sun Dec 30 20:01:42 2007
> X-Mozilla-Status: 0001
> X-Mozilla-Status2: 00800000
> X-Mozilla-Keys:
> Message-ID: <47783F76.5000804 at optonline.net>
> Date: Sun, 30 Dec 2007 20:01:42 -0500
> From: Jerry Quinn <jlquinn at optonline.net>
> User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20071228)
> MIME-Version: 1.0
> To: Andreas Köhler <andi5.py at gmx.net>
> Subject: Re: [patch] More gcc 4.2.3 compilation fixes
> References: <4777E528.4050708 at optonline.net> 
> <1199042673.5193.7.camel at ubuntu> <4777F70D.8040104 at optonline.net> 
> <1199046088.5193.12.camel at ubuntu>
> In-Reply-To: <1199046088.5193.12.camel at ubuntu>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: 8bit
> 
> Andreas Köhler wrote:
> > The attached patch disables the warning for all source files in
> > src/business/business-core.  For even finer granularity one would have
> > to do one of
> > 
> > http://www.gnu.org/software/automake/manual/automake.html#Per_002dObject-Flags
> > 
> > I am not sure that is necessary.  But maybe there is a better answer out
> > there.
> 
> OK, here's another spin.  I also looked at changing
> QOF_LOOKUP_BOOK_ENTRY to be an inline function, but that would be
> GCC-specific.  I gather there's no such requirement now, right?
> 
> This uses GCC pragmas to turn off the flag in the affected files.  It's
> a little less intrusive than the original I posted, and keeps the flag
> on for all other files.

I applied this patch and it will also be available in GnuCash 2.2.3.
For upcoming patches, please attach them (mime-wise).

Thanks a lot!

-- andi5