Opened 12 years ago
Last modified 12 years ago
#5277 new Bugs
QNX 6.5.0 compilation
Reported by: | Owned by: | ||
---|---|---|---|
Milestone: | To Be Determined | Component: | Building Boost |
Version: | Boost 1.46.0 | Severity: | Problem |
Keywords: | Cc: |
Description
Hi,
I am compiling boost on QNX 6.5.0 and there are some changes necessary to the source in order to successfully complete the build.
Regarding ticket #3133 https://svn.boost.org/trac/boost/ticket/3133 it seems that va_list is now in std namespace so this workaround actually causes an error.
In order to fix this on my machine I commented out the test for QNXNTO in boost/serialization/factory.hpp as follows
namespace std{ #if defined(__LIBCOMO__) //|| defined(__QNXNTO__) using ::va_list; #endif } // namespace std
In addition there is an issue with the rename function included from cstdio. By adding <stdio.h> to the includes in libs/filesystem/v3/src/operations.cpp I was able to get it to work. e.g.,
#include <cstdio> // for remove, rename #include <cerrno> #include <cassert> // #include <iostream> // for debugging only; comment out when not in use #if defined(__QNXNTO__) #include <stdio.h> #endif
finally, I added std::va_list to boost/test/impl/execution_monitor.ipp
#if defined(__QNXNTO__) # include <stdio.h> using std::va_list; #endif
These changes allow the build to complete successfully, however I don't know if this means the library has been built problem, and I'm sure there is a better way to integrate these changes.
Attachments (3)
Change History (5)
by , 12 years ago
Attachment: | execution_monitor.ipp added |
---|
by , 12 years ago
Attachment: | factory.hpp added |
---|
by , 12 years ago
Attachment: | operations.cpp added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Hi, Thanks for the reply. I'm not too sure what that you mean. I consider this to be a solution that the boost developers, or anyone else who is trying to compile on QNX 6.5.0 would be interested in. I'm not really reporting a problem since I have the library working on my system. Please feel free to disregard.
This ticket is unlikely to be addressed because no one is responsible for it. It's generally better to split things up by library.