Re: Compilation failure on Mac OSX 10.9, posted by A.G. Schubert on Thu Nov 7 02:18:17 2013
|
Stefan Ritt wrote:
|
|
Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Thu Nov 7 08:08:12 2013
|
A.G. Schubert wrote:
|
|
Re: Compilation failure on Mac OSX 10.9, posted by Ed McNichol on Tue Jan 14 05:19:47 2014
|
Stefan Ritt wrote:
|
|
Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Tue Jan 14 08:15:19 2014
|
Ed McNichol wrote:
|
|
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.
|
|
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.
|
|
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. |
|
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 |