, if you have the network configuration files from the
previous builds still around, I would compare them to the new ones to see
what might have changed.
- Ben
From: Brendan Sheridan
To: x10-users@lists.sourceforge.net
Date: 02/27/2016 07:37 AM
Subject:[X10-users] trouble with c
Hi,
We recently had to rebuild all our cluster nodes and went from RHEL 6->7.2.
Theoretically, nothing package wise was drastically changed (and X10 was
working fine before), but I'm having a lot of trouble getting X10 running
again on more than one node and running out of ideas if anyone can sugg
The problem was with the HOSTNAME in /etc/hostconfig. Removed this line from
the file and runx10 works now.
Thanks!
On 2 Dec 2009, at 4:40 PM, Igor Peshansky wrote:
> Jim LaGrone wrote on 12/02/2009 04:15:10 PM:
>
>> I'm having trouble with the c++ backend on Mac OS X 10.6. I thought
>> thi
On 2 Dec 2009, at 4:40 PM, Igor Peshansky wrote:
> Something must've changed in your mac configuration. Can you run
> OpenMPI (mpirun -np 1 /bin/date)? Can you try to use mpirun -np 1
> instead of runx10 to run your program?
delta:src-par$ mpirun -np 1 date
Wed Dec 2 16:41:12 CST 2009
delta
Jim LaGrone wrote on 12/02/2009 04:15:10 PM:
> I'm having trouble with the c++ backend on Mac OS X 10.6. I thought
> this was working the other day, but maybe I changed something
> inadvertently. I searched the user list to no avail.
>
>
> delta:src-par$ x10c -version
> x10c version 1.7.7
> P
I'm having trouble with the c++ backend on Mac OS X 10.6. I thought this was
working the other day, but maybe I changed something inadvertently. I searched
the user list to no avail.
delta:src-par$ x10c -version
x10c version 1.7.7
Polyglot compiler toolkit version 3.1.1 (2009-10-22 12:00:56)
de
hi,
We'll be putting out a 1.7.6 by the end of the week. The X10 bits
arent't quite packaged up yet, but I did put the pgas binaries out
yesterday afternoon. You can grab them from
http://dist.codehaus.org/x10/binaryReleases/1.7.6/
--dave
-
I'm still having problems with C++ backend. I get this error for (it
looks like) every file of source code.
from ./BitmapHeader.h:4,
from BitmapHeader.cc:1:
/home/jlagrone/x10-1.7/x10.dist/../x10.runtime.17/src-cpp/x10aux/
pgas.h: In function ‘void x10aux::barrier()’:
/h
Jim LaGrone wrote on 08/26/2009 11:18:07 AM:
> I'm receiving the following when building the C++ backend, but I get
> no errors with Java backend.
>
> > x10c++ -d ../bin -commandlineonly *.x10 -
> MAIN_CLASS=RUN_knowledgeFormation
> x10c++: /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86
I'm receiving the following when building the C++ backend, but I get
no errors with Java backend.
> x10c++ -d ../bin -commandlineonly *.x10 -
MAIN_CLASS=RUN_knowledgeFormation
x10c++: /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-
linux/bin/ld: cannot find -lupcrts_sockets
Igor Peshansky/Watson/i...@ibmus wrote on 08/24/2009 08:25:47 PM:
> ...please see the recent discussion on the x10-core list...
Apologies. I just realized that the x10-core list is restricted
to the X10 core team members.
We will be posting the X10 2.0-related spec changes on the external
web p
Yes.
If you are going to build from svn head, it may be best to track changes
being made to svn head (i.e. get on the commits mailing list so you get
mail with each commit.. the commit typically contains comments that
describe what this commit is about).
In this case, we have added support for
Jim LaGrone wrote on 08/24/2009 08:03:15 PM:
> After doing "svn up" I am getting this message with code that compiled
> before:
>
> State.x10:12: method public State.getUserParameters(x10.lang.String):
> x10.lang.Void must be declared as a proto method since it is called on
> a receiver State
After doing "svn up" I am getting this message with code that compiled
before:
State.x10:12: method public State.getUserParameters(x10.lang.String):
x10.lang.Void must be declared as a proto method since it is called on
a receiver State{self==State#this}.this with a proto type.
1 error.
Th
14 matches
Mail list logo
