Massimo, one thing perhaps you can change before the next release... In lib/rivet/init.tcl there are two instances of "apache_log_error" that are problematic for us when we use rivet in non-embedded (outside of Apache) environments, so we currently have to create a stub proc for that to suppress those calls. Could you make those two calls to "apache_log_error" resilient to non-existence?
On Tue, Sep 17, 2013 at 4:15 PM, Massimo Manghi <[email protected]> wrote: > thanks Harald > > > On 09/17/2013 09:14 AM, Harald Oehlmann wrote: > >> Dear Massimo, >> >> thank you for the great action. >> My "requests" are the maximum and there is no need to comply to them. >> >> About the text: which exactly happens is: "fileevents do never fire". >> The event loop works, as "after 10 {set a 1};vwait a"" works. >> >> How to detect "atfork" ? >> Here is what Jan did in tcl8.5.14: >> http://core.tcl.tk/tcl/info/**02909e227f<http://core.tcl.tk/tcl/info/02909e227f> >> > > > yes, thats for the tests etc, but I would like something that could be > checked when I build. Otherwise we should write it in the release notes and > warn people the notifier will not be working on OS that don't support > atfork. As we gathered from the various sources the atfork call has entered > the POSIX specifications long ago and the support is rather wide. > > I'm going to do one more commit...I don't understand why but the > AM_CPPFLAGS are not a transparent replacement for INCLUDES in Makefile.am, > at least when placed in a subdir. We have to put the include compilation > switches in the target specific CPPFLAGS variable > > -- Massimo > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > rivet-dev-unsubscribe@tcl.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
