Boost C++ Libraries: Ticket #5049: compilation error under ia64 HP-UX11i with gcc-4.4.0

attachment set

ruipfernandes@… — Fri, 07 Jan 2011 15:35:33 GMT

attachment → boost_1_45_program_options_gcc_hpux_patch

patch

Vladimir Prus — Sat, 08 Jan 2011 10:25:17 GMT

Thanks for the report. I have checked in a slightly modified patch (in particular, using target-os as opposed to host-os), in r67770.

status changed; resolution set

Vladimir Prus — Sun, 09 Jan 2011 18:27:28 GMT

status new → closed
resolution → fixed

anonymous — Mon, 10 Jan 2011 12:05:32 GMT

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.

Vladimir Prus — Mon, 10 Jan 2011 12:10:58 GMT

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.

Mon, 10 Jan 2011 12:16:36 GMT

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).