|
Boost : |
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2021-06-04 16:36:30
On 6/4/21 7:20 PM, Peter Dimov via Boost wrote:
> Andrey Semashev wrote:
>> On 6/4/21 6:34 PM, Peter Dimov via Boost wrote:
>>> As Niall mentioned, it might be that Docker just doesn't support the
>>> syscalls, even when running on the same kernel.
>>
>> This is a different case, and for that I added compile-time options to disable
>> some syscalls in Boost.Filesystem.
>
> That's not going to be of help in general. Many users have no control
> over how the library is built. They get it from the system, or from a package
> manager.
That's a fair point. Damn, it looks like I'll have to make a runtime
check after all...
> If this check is unreliable, it should be off by default and opt-in. It does more
> harm than good.
Stuff like this never gets enabled. And besides, I do need statx
unconditionally for some of the operations.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk