id summary reporter owner description type status milestone component version severity resolution keywords cc 2531 Workaround for broken remove() broken Niklas Angare Beman Dawes "operations_test fails on QNX 6.4.0 with:[[BR]] Warning: line 820 exception reports default_error_condition().value() 1, should be 93 Line 821 also fails with boost::filesystem::remove: Operation not permitted. The problem is that a workaround for QNX and other OSes in posix_remove() compares the return value of unlink() against EPERM instead of comparing errno against EPERM. Could it ever have worked? EPERM is typically 1 while the return value from unlink() in case of failure is typically -1. The attached patch resolves the issue and the operations_test test now passes. As a side note, the test also passes fully with the workaround disabled on QNX 6.4.0." Patches closed Boost 1.38.0 filesystem Boost Development Trunk Problem fixed