Boost C++ Libraries: Ticket #12310: xlc++: lexical_cast.hpp "invalid processing token"

component, severity changed; keywords, owner set

jlost@… — Fri, 08 Jul 2016 18:33:20 GMT

keywords lexical_cast build xlc++ xlc power8 added
owner set to Antony Polukhin
component None → lexical_cast
severity Problem → Showstopper

owner, component changed

Antony Polukhin — Mon, 11 Jul 2016 18:31:54 GMT

owner changed from Antony Polukhin to Neil Groves
component lexical_cast → range

Looks like an issue in boost.Range or Boost.PP

jlost@… — Tue, 23 Aug 2016 19:22:38 GMT

FYI, a bounty has been posted for this bug ($200):

https://www.bountysource.com/issues/36097120-xlc-lexical_cast-hpp-invalid-processing-token

pitman@… — Thu, 22 Sep 2016 19:31:49 GMT

You can use the option -qnoxlcompatmacros to fix this. This is the same option that is used by b2/bjam when building all of Boost with xlcpp. Using the test you provided:

xlC -c test.cpp -I../boost_1_61_0 -qnoxlcompatmacros

jlost@… — Fri, 24 Feb 2017 15:13:50 GMT

Number1n00b, what is the nature of your proposed fix? I tested the above workaround and it works. camorton2 mentioned a patch at www-01.ibm dot com/support/docview.wss?uid=swg27006911 as well. Does your solution circumvent the need for these patches and flags?

jlost@… — Wed, 01 Mar 2017 15:53:14 GMT

@pitman, what is the feasibility of a fix that removes the need for the -qnoxlcompatmacros flag? I see that IBM already has a patch available: www-01.ibm dot com/support/docview.wss?uid=swg27047524 What would it take for a patch like this to be merged into the codebase?