Hi Koen,
I've updated to the new version:
ii openmpi-bin1.1-2.5ubuntu1
high performance message passing library
ii openmpi-common 1.1-2.5ubuntu1
high performance message passing library
ii openmpi-dbg1.1
Hoi Koen,
Here's the output:
~ $dpkg -l | grep openmpi
ii openmpi-bin1.1-2.5
high performance message passing library
ii openmpi-common 1.1-2.5
high performance message passing library
ii openmpi-dbg1.1
Hi Koen,
This simple executable produces the error below:
--
#include
int main(int argc, char *argv[])
{
MPI_Status stat;
MPI_Init(&argc,&argv);
MPI_Finalize();
return 0;
}
-
Error when building the executable:
In file includ
Public bug reported:
Basically, when i login into kde, the 'initializing services' screen
appears, but it stops after the 2nd icon (i think the 3rd is the
printer). Then it takes me back to the login screen.
I installed 64 bit hardy, alpha 4 with all the latest updates as off feb
15th. (I had the
Switched to Hardy, and it works perfectly now.
In Gutsy I had the problem with CMake even with the mpic++ compiler
specified, e.g.
SET( CMAKE_CXX_COMPILER "mpic++" )
In Hardy the problem is solved.
Thanks guys!
Iman
P.S. Sorry for the late response, I had some serious computer issues and
was
Public bug reported:
/usr/include/mpi.h line 1757:#include "ompi/mpi/cxx/mpicxx.h"
It looks inside "/usr/include/" for the "ompi" directory that is not there. The
file it is looking for is inside "/usr/include/openmpi"
So when you try to compile a c++ file including mpi.h it ends up with a
Great, it is fixed!
I'm not sure which update fixed it, i think it must have been an update in
the last 7 days or so.
Thanks,
Iman
On Tue, Mar 11, 2008 at 12:13 AM, Greg Grossmeier <[EMAIL PROTECTED]>
wrote:
> Iman,
>
> Is this issue still a problem for you in an up-to-date Hardy install?
>
>
Public bug reported:
Binary package hint: update-manager
When doing the automatic upgrade i got the following error:
"Could not install 'tex-common'
The uprade will continue but the 'tex-common' package may not be in a working
state. Please consider submitting a bug report about it.
subprocess
