Re: [Boost-build] [EXTERNAL] Re: Testing Cray

Subject: Re: [Boost-build] [EXTERNAL] Re: Testing Cray
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2012-05-01 22:08:51

On May 1, 2012, at 4:47 PM, Belcourt, Kenneth wrote:

> On May 1, 2012, at 4:16 PM, Steven Watanabe wrote:
> 
>> On 05/01/2012 11:58 AM, Belcourt, Kenneth wrote:
>>> 
>>> On the cray, I need to run compiled / linked targets using a special command (aprun).  I'm looking for a way to modify execunix.c to identify built targets from all other targets that are run so I can invoke built targets correctly on this machine using aprun, rather than /bin/sh as we do by default.
>>> 
>>> Is there some information in the state structure or someplace else I can use to identify when a target is built as opposed to a mkdir, cp, or similar non-built command?
>> 
>> Does <testing.laucher>aprun work?

If I knew how to force it for every test it might work, but I don't.  This patch seems to work okay, note that I intentionally quoted the launcher and removed the quotes on $(>) as otherwise it fails.

Index: testing.jam
===================================================================
--- testing.jam	(revision 78234)
+++ testing.jam	(working copy)
@@ -492,7 +492,7 @@
 actions capture-output bind INPUT_FILES output-file
 {
     $(PATH_SETUP)
-    $(LAUNCHER) "$(>)" $(ARGS) "$(INPUT_FILES)" > "$(output-file)" 2>&1
+    "/usr/bin/aprun" $(>) $(ARGS) "$(INPUT_FILES)" > "$(output-file)" 2>&1
     $(.SET_STATUS)
     $(.RUN_OUTPUT_NL) >> "$(output-file)"
     echo EXIT STATUS: $(.STATUS) >> "$(output-file)"

Clearly I can't check this in but perhaps someone more knowledgable could figure out how to enable this patch when --toolset=cray.

Thanks for the help Steven!

-- Noel