Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: Justin Bronder (jsbronder_at_[hidden])
Date: 2006-05-28 10:48:18

Brian Barrett wrote:
> On May 27, 2006, at 10:01 AM, Justin Bronder wrote:
>> I've attached the required logs. Essentially the problem seems to
>> be that the XL Compilers fail to recognize "__asm__ __volatile__" in
>> opal/include/sys/powerpc/atomic.h when building 64-bit.
>> I've tried using various xlc wrappers such as gxlc and xlc_r to
>> no avail. The current log uses xlc_r_64 which is just a one line
>> shell script forcing the -q64 option.
>> The same works flawlessly with gcc-4.1.0. I'm using the nightly
>> build in order to link with Torque's new shared libraries.
>> Any help would be greatly appreciated. For reference here are
>> a few other things that may provide more information.
> Can you send the config.log file generated by configure? What else
> is in the xlc_r_64 shell script, other than the -q64 option?
I've attached the config.log, and here's what all of the *_64 scripts
look like.

node42 openmpi-1.0.3a1r10002 # cat /opt/ibmcmp/vac/8.0/bin/xlc_r_64
xlc_r -q64 "$@"


Justin Bronder
University of Maine, Orono
Advanced Computing Research Lab
20 Godfrey Dr
Orono, ME 04473
Mathematics Department
425 Neville Hall
Orono, ME 04469

WARNING: The virus scanner was unable to scan the next
attachment. This attachment could possibly contain viruses
or other malicious programs. The attachment could not be
scanned for the following reasons:

The file was corrupt

You are advised NOT to open this attachment unless you are
completely sure of its contents. If in doubt, please
contact your system administrator.

The identifier for this message is 'k4SEmG3W018957'.

The Management
PureMessage Admin <sysadm_at_[hidden]>