ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
89
|
Sat Aug 3 17:35:39 2002 |
| Joe Nall | joe.nall@inet.com | Request | | | Re: Compiling elog 2.0.4 on Solaris |
> > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > >
> > > gcc -o elog elog.c -lsocket -lnsl
> > > gcc -o elogd elogd.c -lsocket -lnsl
> > > elogd.c: In function `ss_file_find':
> > > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > > elogd.c:1372: (Each undeclared identifier is reported only once
> > > elogd.c:1372: for each function it appears in.)
> > > make: *** [elogd] Error 1
> > >
> > > because alphasort is an ucb'ism which does not exist under SYSV
> > >
> > > ... not very portable :-(
> >
> > I was not aware of this. Actually, I don't need 'alphasort' so I removed
it
> > from the source. The update is at
> >
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> >
> > Please give it a try.
>
> ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
> (scandir) that does not work under SYSV:
>
> $ make
> gcc -g -o elogd elogd.c -lsocket -lnsl
> Undefined first referenced
> symbol in file
> scandir /tmp/ccy0Z3iV.o
> ld: fatal: Symbol referencing errors. No output written to elogd
> collect2: ld returned 1 exit status
> make: *** [elogd] Error 1
> $ egrep scandir elogd.c
> n = scandir(path, &namelist, NULL, NULL);
> $
I am having the same experience with ELOG 2.0.5 and Solaris 8. Any work
around woud be appreciated. |
91
|
Tue Aug 6 16:14:42 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: Compiling elog 2.0.4 on Solaris |
> > > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > > >
> > > > gcc -o elog elog.c -lsocket -lnsl
> > > > gcc -o elogd elogd.c -lsocket -lnsl
> > > > elogd.c: In function `ss_file_find':
> > > > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > > > elogd.c:1372: (Each undeclared identifier is reported only once
> > > > elogd.c:1372: for each function it appears in.)
> > > > make: *** [elogd] Error 1
> > > >
> > > > because alphasort is an ucb'ism which does not exist under SYSV
> > > >
> > > > ... not very portable :-(
> > >
> > > I was not aware of this. Actually, I don't need 'alphasort' so I
removed
> it
> > > from the source. The update is at
> > >
> > > http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> > >
> > > Please give it a try.
> >
> > ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
> > (scandir) that does not work under SYSV:
> >
> > $ make
> > gcc -g -o elogd elogd.c -lsocket -lnsl
> > Undefined first referenced
> > symbol in file
> > scandir /tmp/ccy0Z3iV.o
> > ld: fatal: Symbol referencing errors. No output written to elogd
> > collect2: ld returned 1 exit status
> > make: *** [elogd] Error 1
> > $ egrep scandir elogd.c
> > n = scandir(path, &namelist, NULL, NULL);
> > $
> I am having the same experience with ELOG 2.0.5 and Solaris 8. Any work
> around woud be appreciated.
I removed also scandir() in the current version (right now only in CVS). The
official release of 2.1.0 is planned for next week. |
67258
|
Tue May 1 17:03:37 2012 |
| Per Eriksson | pelle@sm4xiu.eu | Info | Linux | Any | Re: Compiling Elog for QNAP NAS x86 |
Per Eriksson wrote: |
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per
|
I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)
Per |
67294
|
Sun Jul 1 19:55:38 2012 |
| Per Eriksson | pelle@sm4xiu.eu | Info | Linux | Any | Re: Compiling Elog for QNAP NAS x86 |
Per Eriksson wrote: |
Per Eriksson wrote: |
Hi All,
I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?
Regards,
Per
|
I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)
Per
|
I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.
This is for x86 based QNAP NAS only.
Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser
BR,
Per |
1563
|
Thu Dec 22 08:53:43 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.6.0 | Re: Compile on Windows? |
Mike wrote: | 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? |
Right now I'm using VS.Net 2003, but you should be able to compile it with 6.0, except that you have to redo the project file, which might not be backwards compatible. An alternative is to use gcc under cygwin, which is a free alternative for windows. |
758
|
Mon Nov 1 10:32:57 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | 2.5.4-6 | Re: Compile of Elog |
> If I make changes to the elog source, How do I re-compile it and not
> distrupt the program??????
There ist only a problem if you replace the currently running executable. You
sould first stop elogd, then replace the executable, then restart it. This ist
true both for Windows and Linux. |
759
|
Mon Nov 1 13:45:47 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.5.4-6 | Re: Compile of Elog |
> If I make changes to the elog source, How do I re-compile it and not
> distrupt the program??????
You first have to stop the running elogd server, then replace the executable,
then restart the server. |
68840
|
Wed Sep 12 11:10:18 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.3 | Re: Compile issues on Fedora withe current elog source |
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.
Stefan |