Problem compiling mod_mono (2.4)

[José María Ruiz]

On Tue, 17 Mar 2009 10:15:01 -0000, Romain Tartière <romain at blogreen.org>  
wrote:

> Hi José!
>
> On Tue, Mar 17, 2009 at 10:50:27AM -0000, José María Ruiz wrote:
>> I've to notice that when I was trying to compile mod_mono the checksums
>> didn't matched
>> so I suppose that the sources where different from expected.
>
> Yes, I did not have time to update to RC3... We are still at RC1.  I got
> annoying regressions with 2.4 and downgraded to 2.2 a few weeks ago, and
> am quite busy right now, so 2.4-RC1 stalled.
>
>
>
> Regarding the SIGPWR problem, it is defined like this on the GNU/Linux
> machine of a friend (/usr/include/bits/signum.h):
> #define SIGPWR    30  /* Power failure restart (System V).  */
>
> In our /usr/include/sys/signal.h, signal 30 is:
> #define SIGUSR1         30      /* user defined signal 1 */
>
> Which in turn is defined as this on GNU/Linux:
> #define SIGUSR1   10  /* User-defined signal 1 (POSIX).  */
>
> So I guess the Mono guys had quite the same problem to make the program
> run on MacOs so maybe you can find some "#if defined(__APPLE__)" that
> can be completed with "|| defined(__FreeBSD__)" somewhere in the code
> that fixes the problem.
>
> I would like to promise to have a look at it in the week but really
> can't be sure of anything right now :-(
>
>
> Please tell us about any success / failure with your experiments!
>
> Kind regards,
> Romain
>

I've downgrade to 2.2 too so I can continue my work.

I will tell you about 2.4 as soon as I have time to experiment with it.

Cheers.

-- 
José María Ruiz Aguilera

Simple Option S.L.
   Tel: (+34) 951 930 122
   Fax: (+34) 951 930 122
   pedidos at simpleoption.es
   http://www.simpleoption.es