Aren't you just missing an #include <string.h> which is needed for strdup() 
... ?

Regards,

Christian

Am Sonntag, 14. Juni 2015, 19:42:55 schrieb John Ralls:
> > On Jun 14, 2015, at 6:44 PM, Alex Aycinena <alex.aycin...@gmail.com>
> > wrote:
> > 
> > John,
> > 
> > On Sun, Jun 7, 2015 at 1:34 PM, John Ralls <jra...@ceridwen.us 
<mailto:jra...@ceridwen.us>> wrote:
> > > On Jun 7, 2015, at 12:38 PM, Derek Atkins <de...@ihtfp.com
> > > <mailto:de...@ihtfp.com>> wrote:> > 
> > > On Sun, June 7, 2015 3:02 pm, John Ralls wrote:
> > >> Alex,
> > >> 
> > >> Turns out that for some flavors of GCC -std=gnu99 is required for
> > >> strdup
> > >> to be provided. I’d made the default c99, which in those cases doesn’t
> > >> support it, hence the error.
> > >> 
> > >> Fixed and pushed.
> > > 
> > > Why are we using strdup() and not g_strdup()?
> > 
> > Oversight? It’s used in several places. The earliest I found was a5d4c7cf
> > from 2004.
> > 
> > Regards,
> > John Ralls
> > 
> > 
> > I upgraded My Fedora 20 machine to Fedora 22, which came out a few weeks
> > ago, and got the same problem again. In order to make sure it was not my
> > new build environment, I cloned a new gnucash, checked out maint, and was
> > able to make, make-clean, and make-install OK. So the new F22 build
> > environment is OK. But when I checked out master on the new clone and
> > wiped out my build directory and tried make again, I got the same error,
> > as follows:
> > 
> > /home/gnucash-dev/gitcheckouts/gnucash-new/src/app-utils/gfec.c: In
> > function 'gfec_catcher':
> > /home/gnucash-dev/gitcheckouts/gnucash-new/src/app-utils/gfec.c:60:25:
> > error: implicit declaration of function 'strdup'
> > [-Werror=implicit-function-declaration]> 
> >          *(char**)data = strdup("Guile error: Too many recursions in error
> >          catch handler.");>          
> >                          ^


_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to