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.
On Oct 23 08:57, Jeff Squyres wrote:
> On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote:
> >> There is in the openib BTL.
> > The bug #1025 has in one the answers the following phrase:
> > "It looks like this will affect many threading issues with the
> > pathscale compiler -- the openib BTL is simply the first place we
> > tripped it."
> >> and I do not see the problems that you are seeing. :-\ Is Debian
> >> etch a supported pathscale platform?
> > Seems like it's not... And indeed the older RHEL4 is a supported
> > platform, which might explain the different results.
> You might want to ask them if Debian etch is supported.
Debian is not supported by the PathScale compiler. It might
be possible to get it to run... ;-) on the most recent "Debian
etch" but I am sure it is untested.
See Section 2: Table 2-1 Supported Linux Distributions and Platforms
Red Hat Enterprise Linux 4 (RHEL4)
Fedora Core 3, 4, 5 (FC3, FC4, FC5)
SUSE Linux Enterprise 10a
SUSE Linux Enterprise Server (SLES) 9
SUSE Linux Professional 9.3
The Pathscale compiler itself is a 32bit object.
There are two versions of Debian etch,
32bit and 64bit
which one is is being used? The new Debian etch 64bit has
minimal support for 32 bit user space programs by default. It may be
necessary to install 32 bit libs and or compatability libs to
get it to run correctly.
I do not know which gcc compiler suite Debian GCC is based on.
"gcc -v " can tell volumes. Since the PathScale compiler
uses parts of the gcc compiler suite this could be important.
In RHEL4 compare and contrast gcc4-4.1.1-53 .vs. gcc-3.4.6-8.
The Pathscale compiler is recently rebased to also work with gcc4
Do foundation Open MPI tools like .../bin/orterun
compile and run well enough to return errors? If the Usage message
fails to print then all bets are off for MPI itself. Example:
orterun (OpenRTE) YourVersion
Usage: orterun [OPTION]... [PROGRAM]...
Start the given program using Open RTE
Scan the eko man page for PathScale compiler specific options.
ompi_info does not capture compiler flags so report your
configure line, make line and environment variables.
T o m M i t c h e l l
Host Solutions Group, QLogic Corp.