Opened 8 years ago
Last modified 8 years ago
#10374 new Support Requests
Build error on cross compiling for QNX 6.6.0 x86
Reported by: | Owned by: | ||
---|---|---|---|
Milestone: | To Be Determined | Component: | Building Boost |
Version: | Boost 1.56.0 | Severity: | Problem |
Keywords: | Cc: | hkjin81@… |
Description
Hello, I'm trying to build Boost for QNX. When cross compiling Boost 1.56 for QNX 6.6.0 x86 target, errors occured. I found similar issue(http://svn.boost.org/trac/boost/ticket/9811) and its state is fixed in 1.56 but errors of that issue and more errors still exist. Is this issue still exist or something I did is wrong? I'm working on Ubuntu 12.04 32bit x86 with QNX 6.6.0 SDP installed and for QNX 6.6.0 x86.
QNX uses Dinkum standard libraries(libcpp). If I compile with option cxxflags=-Vgcc_ntox86_gpp for using gnu standard libraries(libstdc++) then it compiled successfully but that's not a solution for me because other libraries are provided built with QNX's default Dinkum libraries.
bootstrap and b2 log file attached.
Thanks.
Attachments (2)
Change History (5)
by , 8 years ago
Attachment: | bootstrap.log added |
---|
comment:1 by , 8 years ago
Commands used for build:
./bootstrap.sh --prefix=/home/user/boost-build
./b2 -j3 toolset=qcc target-os=qnx --with-system --with-atomic --with-chrono --with-timer --with-date_time --with-thread --link=static install
comment:2 by , 8 years ago
Hi,
I think this issue is the same as https://svn.boost.org/trac/boost/ticket/8349 which has been closed as won't fix.
According to GNU about Complex Numbers, we can safely undefine the macro I. So, I did a workaround by commenting out the macro I from the complex.h, but I would like to know if simply removing the macro from the header file is also okay.
Best regards, Anton
comment:3 by , 8 years ago
Hi,
There is a header file patch from the QNX community site. It seems an external link is rejected. Anyway, you can google "foundry27 complex.h 4.7.2"
Best regards, Anton
Bootstrap log