I'm forwarding this comment from Terry Dontje, of the HPC CT team (he
isn't on hpcdev-discuss):
> One thing you may want to try and compiling and executing one of the
> example codes in CT 8.2.1. That will at least give you the sanity
> test that things can work.
>
> Can you tell us what th
That's very strange. Could you use dtrace to get a trace of the MPI
calls? That might give us a clue. You can find instructions on how
to do that in the user guide:
http://dlc.sun.com/pdf/821-0225-10/821-0225-10.pdf
Iain
On Jul 17, 2008, at 4:17 AM, Manal Helal wrote:
> 5) Do you know where I can get "Sun HPC ClusterTools Software
> Administrator?s Guide"?
Have you looked on docs.sun.com?
Iain
On Jul 17, 2008, at 4:17 AM, Manal Helal wrote:
> 1) making sure that studio is installed properly:
>
> a)
> $ pkginfo |grep -i studio
> gave me a long list of packages containing the word studio (not sure
> if it helps to paste it here), but sure it is installed and running
Here's what I get
On Jul 15, 2008, at 7:00 AM, Gerard Henry wrote:
>>
>> I installed the studio from a DVD sent to me by Sun
>> Support in Sydney. It is Sun Studio 12, Solaris x86,
>> the command was ./installer, and it started something
>> like a graphical interface, but was basically a
>> console, and it install
On Jul 15, 2008, at 1:57 AM, Manal Helal wrote:
> Sorry the make file is as included in the first message, I changed
> the project name from mmDst to myProj just to make it general,
>
> SO the make file is:
> ***
> myProj : main.o
> mpicc -g -Wall -lmpe
On Jul 13, 2008, at 11:22 PM, Manal Helal wrote:
>
> make: Fatal error in reader: makedebug, line 4: Unexpected end of
> line seen
> Current working directory /export/home/me/myProj
This is a problem with the makefile. What are the first four lines
of /export/home/me/myProj/makedebug?
> I
I asked the Studio C++ team, and here's what they said:
> The main problem lies with compiler options. Boost doesn't work (and
> is not supposed to) with old pre-standard STL implementation, which
> is still the default, but it should build and work with STLport.
>
> I tried that example with
