Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 597 of 808  Not logged in ELOG logo
    icon2.gif   Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:20:11 2018 
I don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps on get or sourceforge?




Stefan
    icon2.gif   Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:25:07 2018 
I would like to try the new code, I don't see it on elog/download/tar/.
Do you keep updates elsewhere like on get or sourceforge?




Stefan
    icon2.gif   Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:57:31 2018 
A quick test suggests I can't just replace sprintf with snprintf.
Original error:
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256 [-Wformat-overflow=]
    icon2.gif   Re: Compile issues on Fedora withe current elog source, posted by Andreas Luedeke on Wed Sep 12 20:52:22 2018 
Stefan said "code is commited": that means you can download the latest version from https://bitbucket.org/ritt/elog, as described in https://elog.psi.ch/elog/download.html,
and then compile it. Clear now?




Stefan
    icon2.gif   Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Thu Sep 13 06:12:59 2018 
Latest compile effort on Fedora 28 using the bitbucket source downloaded at 21:12 PDT:

make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Imxml -DHAVE_SSL -c -o mxml.o mxml/mxml.c
    icon2.gif   Re: Compilation flag/file question, posted by Stefan Ritt on Tue Mar 8 17:34:05 2005 
> If I want to go to the latest CVS release, what files do I have to compile
> along with the elogd.c file?  Also, do I need to use any special gcc flags
> for the compilation?  Thanks.
    icon2.gif   Re: Compilation flag/file question, posted by Benjamin Brown on Tue Mar 8 19:23:14 2005 
> > If I want to go to the latest CVS release, what files do I have to compile
> > along with the elogd.c file?  Also, do I need to use any special gcc flags
> > for the compilation?  Thanks.
    icon2.gif   Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Wed Nov 6 09:04:32 2013 


    
        
            A.G. Schubert wrote:
        
        
            
            When compiling elog on OSX 10.9 (Mavericks), I get the error below.
ELOG V3.1.5-3fb85fa6