On Fri, Oct 21, 2005 at 06:26:32PM -0500, Troy Benjegerdes wrote:
> On Fri, Oct 21, 2005 at 04:12:05PM -0500, Andrew Friedley wrote:
> > I just committed a fix to the trunk to fix your original segfault down
> > in opal_show_help() - this is the same problem Ken posted. This fix
> > should make i
On Fri, Oct 21, 2005 at 04:12:05PM -0500, Andrew Friedley wrote:
> I just committed a fix to the trunk to fix your original segfault down
> in opal_show_help() - this is the same problem Ken posted. This fix
> should make it into the v1.0 branch eventually. Even so, you are going
> to run into
Yeah, this was (in my opinion) a very poorly named configure option.
--disable-cxx does not disable the need for a C++ compiler, only the
building of the MPI-2 C++ bindings. Some of our utilities are in C+
+, so a C++ compiler is always required.
Brian
On Oct 21, 2005, at 11:47 AM, Troy B
Ken,
What C compiler are you using ? We never get this compile error and
we are using a bunch of compilers on different architectures.
Thanks,
george.
On Oct 21, 2005, at 5:12 PM, Andrew Friedley wrote:
I just committed a fix to the trunk to fix your original segfault down
in opal_sh
I just committed a fix to the trunk to fix your original segfault down
in opal_show_help() - this is the same problem Ken posted. This fix
should make it into the v1.0 branch eventually. Even so, you are going
to run into the real problem you were handling - this fix is just for
proper error h
The debian is a 32 bits Intel p4-M processor (it's my laptop). The
AMD machine has a Red Hat Enterprise Linux AS release 4 (Nahant
Update 2).
Arg, it's a 64 bits machine where everything is compiled in 32
bits mode ... the default compiler picked up by ompi configure is a
32 bits comp
Debian amd64, or 32 bit?
On Fri, Oct 21, 2005 at 02:46:42PM -0400, George Bosilca wrote:
> I do. I'm using gcc4.0.1 on my debian unstable version and a custom
> build from the latest gcc CVS on MAC OS X. I run some tests yesterday
> on a AMD Opteron(tm) Processor 246 machine (we just have one
On Fri, Oct 21, 2005 at 08:04:56AM -0500, Andrew Friedley wrote:
> I've managed to reproduce the segfault, but haven't yet figured out the
> problem. I've got some distractions to attend to this afternoon, so it
> might be a while before I get a fix.
>
> Andrew
I rebuilt without a vpath build
I do. I'm using gcc4.0.1 on my debian unstable version and a custom
build from the latest gcc CVS on MAC OS X. I run some tests yesterday
on a AMD Opteron(tm) Processor 246 machine (we just have one of them
so I just test fork pls and shared memory BTL) and it worked.
Otherwise most of the
I've managed to reproduce the segfault, but haven't yet figured out the
problem. I've got some distractions to attend to this afternoon, so it
might be a while before I get a fix.
Andrew
Troy Benjegerdes wrote:
I just did a fresh build from the v1.0 branch. I just ran this from the
command
$ ./configure --disable-cxx --prefix /scratch/troy/ompi
*** C++ compiler and preprocessor
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
> > fall apart.. I tried a build on my debian-ppc desktop with gcc-4.0.2,
> > and it died with bogus assembler messages.
> >
> > What systems/distros/compilers are people using for development? Is
> > anyone using gcc-4.X ?
>
> We mainly use x84/x86_64 Linux and OS X (PPC) for development. I
>
On Oct 21, 2005, at 11:12 AM, Troy Benjegerdes wrote:
On Fri, Oct 21, 2005 at 09:51:36AM -0500, Troy Benjegerdes wrote:
I just did a fresh build from the v1.0 branch. I just ran this
from the
command line.. I guess I was hopeing it was going to default to
ssh to
start things up.
I also bu
On Fri, Oct 21, 2005 at 09:51:36AM -0500, Troy Benjegerdes wrote:
> I just did a fresh build from the v1.0 branch. I just ran this from the
> command line.. I guess I was hopeing it was going to default to ssh to
> start things up.
>
> I also built this as a vpath build Does anyone else regula
I just did a fresh build from the v1.0 branch. I just ran this from the
command line.. I guess I was hopeing it was going to default to ssh to
start things up.
I also built this as a vpath build Does anyone else regularly build
like that? It seems to at least confuse paths in gdb.
More to com
Blah -- this is a segv when trying to print a help message. The help
message you should have gotten was:
-
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due
Developers --
*** YOU NEED TO TELL TIM OR ME if you want a commit brought over from
the trunk to the v1.0 branch ***
I notice a bunch of commits on the trunk that seem to have to deal with
bug fixes and/or stabilization issues. Although I read all the commit
messages, I do not know what should b
17 matches
Mail list logo
