Re: [liblo] [ANN] liblo version 0.28 released

Hi Felipe,

Hm, that is unexpected.  Since it is already #ifdef'd out, why is it
causing a problem?  I'm not sure I understand the mechanism behind the
build network.  Is it being built on an old kernel, but against
headers for a newer kernel?  That's the only reason I could think this
would cause a problem..

That said, perhaps it would actually be better to detect the existence
of SO_REUSEPORT at configure time instead of compile time, not sure if
that would fix the problem or not.

Yes, technically you could just take out those sections of the code,
but I was hoping you wouldn't need to repack the archive.  I don't
understand why SO_REUSEPORT is defined if it is not supported.

Steve


On Mon, Feb 3, 2014 at 6:00 PM, Felipe Sateler <fsa...@gm...> wrote:
> On Mon, Feb 3, 2014 at 11:14 AM, Felipe Sateler <fsa...@gm...> wrote:
>> On Mon, Jan 27, 2014 at 3:00 PM, Stephen Sinclair <rad...@gm...> wrote:
>>> We are pleased to present stable release 0.28 of LibLo, the
>>> lightweight, easy to use implementation of the Open Sound Control
>>> protocol.
>>
>> Hi Stephen,
>>
>> I uploaded liblo to debian, but I'm encountering failures in the test
>> suite (first time enabled in this version)[1]. Apparently SO_REUSEPORT
>> is not available in the buildd network (linux is 3.2, and REUSEPORT
>> needs 3.9).
>>
>> I think the REUSEPORT check is done at build time. Could it be done at
>> runtime? Or is there another workaround?
>
> It seems to me that I could just patch out the part that is already
> #ifdef protected. Do I risk breaking anything by doing so?
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel