RE: Bug#651529: rsyslog: FTBFS on hurd-i386
On Fri, 2011-12-16 at 12:18 +0100, Rainer Gerhards wrote:
> > While that could be the easy way out, it would definitely be wrong.
> > Such limits can be OS or filesystem specific, if at all. They do not even
> > represent reality on GNU/Linux! Try this:
>
> I try to stay out of these politics, but I found it beneficial to remove the
> dependency on MAX_PATH. It actually solved two error conditions that
> otherwise could occur (not sure if the dlopen call will fail in these cases,
> though). At least the code got smaller.
>
> I have enhanced v5-devel, patch is available here:
>
> http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=01c7c9ffc6771f73df9ee0bc
> 18e30534d6c6974c
>
> I would appreciate if you could have a look at it; the pointer arithmetic is
> obviously easy to get wrong.
Good that you took the time to change the code, I'm currently working on
completing the dynamic allocation solution. I'll take a look at your
changes, thank you. If Guillem is happy with your changes, let's settle
with your solution.
I have some more issues now when the package is building on GNU/Hurd,
one is the configuration file. Is it OK to submit another bug report to
the Debian bug data base? Or do you want me to contact the development
list (if it exists) or you directly?
Reply to: