5 Sep
2011
5 Sep
'11
3:32 a.m.
On 9/5/11 9:11 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I guess each can use the best of his resources
at a moment to make the
project work. So if somebody has one that does not compile, he can work
on fixing it. mac os x is freebsd at the core, thus compiling on it
makes it very likely to stay clean on all *bsds. Be sure when I will get
to a linux, i fix any compile issues I discover, but when out of the
office, I work on what I have at a hand. In the recent history I was
doing cross compilation on many linux flavours, to generate the rpms,
but that does not come handy always.
So, what I said in my previous email is that reverting does not solve
completely the issue introduced by the other commit on all os-es we used
to support.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
Actually this commit broke compilation on mac os
x, so just reverting
will get back to broken stage:
broken state on which os? i would put presence on
getting compilation
to work on open operating systems.