Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Compilation failure on Mac OSX 10.9, posted by A.G. Schubert on Tue Nov 5 23:21:52 2013 
    icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Wed Nov 6 09:04:32 2013 
       icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by A.G. Schubert on Thu Nov 7 02:18:17 2013 
          icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Thu Nov 7 08:08:12 2013 
             icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by Ed McNichol on Tue Jan 14 05:19:47 2014 
                icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Tue Jan 14 08:15:19 2014 
Message ID: 67605     Entry time: Thu Nov 7 02:18:17 2013     In reply to: 67603     Reply to this: 67606
Icon: Reply  Author: A.G. Schubert  Author Email: alexis4@stanford.edu 
Category: Bug report  OS: Mac OSX  ELOG Version: 2.9.2-2494 
Subject: Re: Compilation failure on Mac OSX 10.9 

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

ELOG V3.1.5-fe60aaf