Tomas
Tomas
> Yes, it is. They need to be generated on the actual platform you're using. Thank you for your answer. What do I need to do if I have to...
Hi Miguel, Thank you for your detailed explanation. What I'm concerning about is if `container_node_sizes_impl.hpp` is platform related. If this file is platform related, which means I need to generate...
libusb hotplug for Windows is really important. I have a program running on Linux/Window/MacOS, but Windows doesn't have hotplug support, I have to write my own device detection code for...
I tried that before, I even tried to merge the change into libusb 1.0.19, but I failed to merge it to newer code. I still need to use latest branch,...
This is a great news!
I just checked the latest code, it seems that windows hotplug hasn't been implemented. Windows libusb hotplug definitely is my first 2018 new year wish.
Now, this Hotplug has become my 2019 new year wish.
After 5 days investigation on this issue, I have finally found the root cause. on line 816 of file /usr/libexec/mock/mock `816: unshare_namespace(config_opts)` in this function, `util.CLONE_NEWNS` is used to unshare...
> Mock intentionally uses a separate namespace for mountpoints. This is expected. > > I fail to see what is happening with the the /var/lib/mock folders in mock, though. >...
> Mock intentionally uses a separate namespace for mountpoints. This is expected. > > I fail to see what is happening with the the /var/lib/mock folders in mock, though. >...