On 12/13/19 4:32 PM, Hans Verkuil wrote: >>> I am unable to test with musl since v4l2-ctl and v4l2-compliance are C++ programs, >>> and there doesn't appear to be an easy way to compile a C++ program with musl. >>> >>> If you happen to have a test environment where you can compile C++ with musl, >>> then let me know and I can give instructions on how to run the compliance tests. >>> >>> If you can't test that, then I can merge this regardless, and hope for the best >>> once the Y2038 fixes end up in glibc. But ideally I'd like to have this tested. >> >> I've heard good things about the prebuilt toolchains from http://musl.cc/. >> These seems to come with a libstdc++, but I have not tried that myself. > > I'll see if I can give those a spin, but if I can't get it to work quickly, > then I don't plan on spending much time on it. I managed to build v4l2-ctl/compliance with those toolchains, but they seem to be still using a 32-bit time_t. Do I need to get a specific version or do something special? Regards, Hans
