> On Dec 21, 2019, at 2:04 AM, Mirco Pazzaglia <mirco.pazzag...@inim.biz> wrote: > > I'll have a look into it, thank you. If opting-out of the SO_REUSEPORT is not > a breaking change in any manner (is it?), the solution may just be as simple > as patching said cpp file to ifndef on the __ANDROID__ (or similar) define.
But wouldn’t that mean that systems that run an up-to-date version of Android won’t get to call "setsockopt(SO_REUSEPORT)” at all? We don’t want that. > Wouldn't it be better though to add a runtime check for compatibility in the > cpp code What would that look like?? Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
