> How did you create those archives? I guess you didn't use the created > release_*-scripts, but "make dist dist-zip" again?
No, I used the release_prepare.sh to generate it, since it's my understanding that is the script that should do that. I'm not sure if the autotools still work at this point; I haven't tested with them in a while. > Everyone is free to ignore failing tests anyway. Not running many of > those and not notifying the user about that OTOH provides a wrong > feeling that everything's OK, while things might fail at runtime. I guess that's one way of thinking about it. However, if you do that it seems like you should always run all tests, while (for example) the NT Event Logger appender test is only run on Windows; this would always fail on Linux/OSX. As per Ralph's comment: > That said, I don’t see anyplace on the log4cxx web site that even states what > platforms it supports. It /should/ work wherever APR works, although for some parts of the code log4cxx relies on external applications being present(see [1] for example code, and [2] for the test). There's also support for uncommon character encodings like EBCDIC, which I have no idea if it still works. I would like to create a minimal library that depends solely on the C++ standard library, but that would probably be easier with more modern versions of C++(C++17 has filesystem library, C++20 introduces formatting[3], which is possibly libfmt[4] on the backend, I'm not sure). -Robert Middleton [1]: https://github.com/apache/logging-log4cxx/blob/229106fd7ce99452501bd8406bd653793c756f69/src/main/cpp/gzcompressaction.cpp#L110 [2]: https://github.com/apache/logging-log4cxx/blob/229106fd7ce99452501bd8406bd653793c756f69/src/test/cpp/rolling/sizebasedrollingtest.cpp#L188 [3]: https://en.cppreference.com/w/cpp/utility/format [4]: https://fmt.dev/latest/index.html
