#5049 closed Bugs (fixed)
compilation error under ia64 HP-UX11i with gcc-4.4.0
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | program_options |
| Version: | Boost 1.45.0 | Severity: | Problem |
| Keywords: | HP-UX | Cc: |
Description
The error is:
« /utf8_codecvt_facet.cpp:255:7: error: missing binary operator before token "(" »
I solved the problem with the attached patch
Attachments (1)
Change History (6)
by , 12 years ago
| Attachment: | boost_1_45_program_options_gcc_hpux_patch added |
|---|
follow-up: 3 comment:1 by , 12 years ago
Thanks for the report. I have checked in a slightly modified patch (in particular, using target-os as opposed to host-os), in r67770.
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
follow-up: 4 comment:3 by , 12 years ago
Replying to vladimir_prus:
Thanks for the report. I have checked in a slightly modified patch (in particular, using target-os as opposed to host-os), in r67770.
I have reported the same issue in filesystem library (see ticket 5048). Beman commented that the change in the jam file is not the best thing to do, as not everyone uses bjam to compile. Please see the comments in that ticket for more information.
follow-up: 5 comment:4 by , 12 years ago
Replying to anonymous:
Replying to vladimir_prus:
Thanks for the report. I have checked in a slightly modified patch (in particular, using target-os as opposed to host-os), in r67770.
I have reported the same issue in filesystem library (see ticket 5048). Beman commented that the change in the jam file is not the best thing to do, as not everyone uses bjam to compile. Please see the comments in that ticket for more information.
As I understand, the problem arises when compiling Boost, not when compiling user code. Therefore, I don't really care about other build systems. Should Boost.Config be modified so that this Jamfile change is no longer necessary, let me know.
comment:5 by , 12 years ago
Replying to vladimir_prus:
Replying to anonymous:
Replying to vladimir_prus:
Thanks for the report. I have checked in a slightly modified patch (in particular, using target-os as opposed to host-os), in r67770.
I have reported the same issue in filesystem library (see ticket 5048). Beman commented that the change in the jam file is not the best thing to do, as not everyone uses bjam to compile. Please see the comments in that ticket for more information.
As I understand, the problem arises when compiling Boost, not when compiling user code. Therefore, I don't really care about other build systems. Should Boost.Config be modified so that this Jamfile change is no longer necessary, let me know.
Yes, I think that would be better considering that the same problem may affect other libraries (I did not compile all boost libraries in HP-UX).
patch