Re: syslog-ng update please?
- 1. Native build is no longer very well supported because it takes
extra effort. It is recommended to use cross compilation for most
optware packages, . Although we don't oppose to anyone take the
effort to make packages both cross and native.
2. I've upgraded syslog-ng from 2.0.4 to 2.0.8, and to 2.0.9. The
original maintainer probably no longer maintains the package. There
was a small compilation problem got fixed in between. Autobuilder is
3. You can subscribe to http://cia.navi.cx/stats/project/nslu2-linux/.rss
for nslu2-linux svn commits. This will keep you more up-to-date.
4. We *need* more active package maintainers. If you can build optware
ipk's , and actively use any package without maintainer, you're
more than welcome to step up and become the maintainer of that package.
--- In firstname.lastname@example.org, "tlhackque" <tlhackque@...> wrote:
> Thought I'd take a stab at a manual build.
> Didn't have luck with the git repo, but found tar files for 2.0.9 at
> eventlog-0.2.7 (a dependency) is also there.
> I was able to (native) build eventlog.
> Didn't succed with syslog-ng. syslog-ng's configure doesn't
> find 'libnet-config', yet the tcpwrappers package 7.6-4 is installed.
> It also wants glib version >=2.2; yet IPKG says glib 2.9.6.-1 is
> installed. /opt/lib, /opt/share & /opt/include only contain glib-2.0
> file/directory names.
> So I'm confused. Perhaps it's my build environment, or perhaps the
> tcpwrappers & glib packages aren't built properly...
> If the syslog-ng maintainer could take a stab at the upgrade, I'd
> appreciate it.
I think I'm at the bottom of the syslog-ng issue. One more update
seems to be needed. Bottom line: it works with glib 2.12.12, but not
the current ipkg'd glib (184.108.40.206).
I installed your syslog-ng & eventlog. Better, but killall -HUP still
closes the socket and starts the I/O errors. Interesting that it does
NOT log the expected message:
Configuration reload request received, reloading configuration;
However, on systems where I'd done some manual work, I'd built a newer
glib. And syslog-ng behaved there!
Here's how I rebuilt glib:
glib from http://directory.fsf.org/project/glib/
tar -xf glib-2.12.12.tar
make && make DESTDIR=/tmp/stage install
I made a tar file of just a few of the files, moved it to a failing
system & they fixed the syslog-ng problems. At least the one's I've
seen so far.
Here's that subset of glib (nothing magic, just /opt/lib/libg*):
-rwxr-xr-x 0/0 14816 2008-03-26 12:35:13 opt/lib/libgthread-
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgthread-
2.0.so.0 -> libgthread-2.0.so.0.1200.12
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgthread-2.0.so -
> libgthread-2.0.so.0.1200.12-rwxr-xr-x 0/0 886 2008-03-26 12:35:13 opt/lib/libgthread-2.0.la
-rwxr-xr-x 0/0 233056 2008-03-26 12:34:55 opt/lib/libgobject-
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgobject-
2.0.so.0 -> libgobject-2.0.so.0.1200.12
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgobject-2.0.so -
> libgobject-2.0.so.0.1200.12-rwxr-xr-x 0/0 871 2008-03-26 12:34:55 opt/lib/libgobject-2.0.la
-rwxr-xr-x 0/0 10488 2008-03-26 12:35:07 opt/lib/libgmodule-
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgmodule-
2.0.so.0 -> libgmodule-2.0.so.0.1200.12
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libgmodule-2.0.so -
> libgmodule-2.0.so.0.1200.12-rwxr-xr-x 0/0 876 2008-03-26 12:35:07 opt/lib/libgmodule-2.0.la
-rwxr-xr-x 0/0 631164 2008-03-26 12:34:39 opt/lib/libglib-
lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libglib-2.0.so.0 -
> libglib-2.0.so.0.1200.12lrwxrwxrwx 0/0 0 2008-03-27 12:50:54 opt/lib/libglib-2.0.so ->
-rwxr-xr-x 0/0 829 2008-03-26 12:34:39 opt/lib/libglib-2.0.la
Of course for release, the whole glib ipkg should be updated.
I used to have a cross-build environment (I did the original port of
bind & updated a few other packages). However, when we switched from
cvs on sourceforge, I never was able to get subversion working &
couldn't commit anything. Afraid I gave up. So mostly I post useful
scripts on the wiki.
I'd certainly be happy to do the routine updates of packages that I
use -- if I could get back to where I was before the 'upgrade'.
I do have a new server on hand, so perhaps it's a good time to try
again. I run fedora core.