Re: [Boost-bugs] [Boost C++ Libraries] #7093: Building "system" segfaults on AIX 6.1 / vacpp

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7093: Building "system" segfaults on AIX 6.1 / vacpp
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-07 17:50:04


#7093: Building "system" segfaults on AIX 6.1 / vacpp
----------------------------------------------------+-----------------------
  Reporter: Martin Baute <solar@…> | Owner: vladimir_prus
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: build
   Version: Boost 1.50.0 | Severity: Regression
Resolution: | Keywords: aix
----------------------------------------------------+-----------------------

Comment (by Martin Baute <solar@…>):

 It took me a moment to figure out what exactly the command line used by
 Jam would be, as it does not show up in bootstrap.log. Then I came up with
 the idea of putting a "GNARF" in the options in build.jam, and checking
 the error message in the log, which *did* print the command line.

 So, the two attacked assembler files were generated via:

 {{{
 xlc -o bin.aixppc/command.s -DNDEBUG -DOPT_HEADER_CACHE_EXT
 -DOPT_GRAPH_DEBUG_EXT -DOPT_SEMAPHORE -DOPT_AT_FILES -DOPT_DEBUG_PROFILE
 -DOPT_FIX_TARGET_VARIABLES_EXT -DOPT_IMPROVED_PATIENCE_EXT
 -DYYSTACKSIZE=5000 -S -O3 -qstrict -qinline -bmaxdata:0x40000000 command.c
 }}}

 (Equivalent for lists.c.)

 I don't know about a Valgrind tool for AIX, but some of the compiler
 debugging options look promising. I'll toss them at the problem as soon as
 I get around to it. However, I can only access the AIX during office
 hours, which puts me on a budget here.

 Thanks for your help, anyway.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7093#comment:9>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC