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.

$ make

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -w -c -o crypt.o src/crypt.c

cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall  -I../mxml  -DHAVE_SSL -o elog src/elog.c crypt.o -lssl

src/elog.c:125:8: error: expected parameter declarator

size_t strlcpy(char *dst, const char *src, size_t size)

       ^

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: error: expected ')'

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:62: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                             ^

/usr/include/secure/_common.h:30:32: note: expanded from macro '_USE_FORTIFY_LEVEL'

#    define _USE_FORTIFY_LEVEL 2

                               ^

src/elog.c:125:8: note: to match this '('

/usr/include/secure/_string.h:105:44: note: expanded from macro 'strlcpy'

  __builtin___strlcpy_chk (dest, src, len, __darwin_obsz (dest))

                                           ^

/usr/include/secure/_common.h:39:53: note: expanded from macro '__darwin_obsz'

#define __darwin_obsz(object) __builtin_object_size (object, _USE_FORTIFY_LEVEL > 1 ? 1 : 0)

                                                    ^

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!

SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. 

Using Elog 2.9.2

Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.

I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies.  On the 10th reply the application crashed, this is repeatable 100% of the time.  Without the propagate option everything works fine.

Attached is my config file parsed down.

Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option?

Hi Stephen,

I see that you don't allow branching in your threads.  Why do you need to propagate the Status throughtout the thread?  Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'

I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature.  I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting).  OK, I know if it is historic, it cannot easily be changed because of other users.  Or if some users will primarily be responding to emails rather viewing the logbook via a browser.  I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.

 Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing.  Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case.  Even with branches the system will crash once there are 10 replies in the note with propagate on.

As for use case, with  a few users I needed a way to represent a note as open so that the next person knew work still needed to be done.  Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max).  I will experiment with the collapse to last to see how it looks.  Any other suggestions would be helpful.