Re: Compiling elog 2.0.4 on Solaris, posted by Joe Nall on Sat Aug 3 17:35:39 2002
|
> > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > >
> > > gcc -o elog elog.c -lsocket -lnsl
|
|
Re: Compiling elog 2.0.4 on Solaris, posted by Stefan Ritt on Tue Aug 6 16:14:42 2002
|
> > > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > > >
> > > > gcc -o elog elog.c -lsocket -lnsl
|
Re: Compiling Elog for QNAP NAS x86, posted by Per Eriksson on Tue May 1 17:03:37 2012
|
Per Eriksson wrote:
Hi All, |
Re: Compiling Elog for QNAP NAS x86, posted by Per Eriksson on Sun Jul 1 19:55:38 2012 
|
Per Eriksson wrote:
|
|
Re: Compile on Windows?, posted by Stefan Ritt on Thu Dec 22 08:53:43 2005
|
[quote="Mike"]What version of Visual Studio do you use for compile Elog on windows.
I have downloaded the Tar from svn and am having some errors, but then I've go VS.Net 2003. I wondering if this was done with 6.0?[/quote]
|
Re: Compile of Elog , posted by Stefan Ritt on Mon Nov 1 10:32:57 2004
|
> If I make changes to the elog source, How do I re-compile it and not
> distrupt the program??????
|
|
Re: Compile of Elog , posted by Stefan Ritt on Mon Nov 1 13:45:47 2004
|
> If I make changes to the elog source, How do I re-compile it and not
> distrupt the program??????
|
|
Re: Compile issues on Fedora withe current elog source, posted by Stefan Ritt on Wed Sep 12 11:10:18 2018
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(),
which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please
post the full warning list here. |