Great; thanks!
On Jan 26, 2009, at 4:11 AM, Andrea Iob wrote:
Could you confirm that changing the last 3 files to
use OMPI_PATH_MAX
instead of PATH_MAX (without adding the #include)
also fixes the
problem?
Yes, with OMPI_PATH_MAX the problem is also fixed.
Andrea
_
> Could you confirm that changing the last 3 files to
> use OMPI_PATH_MAX
> instead of PATH_MAX (without adding the #include)
> also fixes the
> problem?
>
Yes, with OMPI_PATH_MAX the problem is also fixed.
Andrea
On Jan 23, 2009, at 7:19 AM, Andrea Iob wrote:
What files did you change?
The files I changed are:
openmpi-1.3/ompi/contrib/vt/vt/vtlib/vt_otf_gen.c
openmpi-1.3/ompi/contrib/vt/vt/vtlib/vt_thrd.c
openmpi-1.3/opal/util/path.c
openmpi-1.3/orte/mca/plm/rsh/plm_rsh_component.c
openmpi-1.3/orte/to
>
> What files did you change?
>
The files I changed are:
openmpi-1.3/ompi/contrib/vt/vt/vtlib/vt_otf_gen.c
openmpi-1.3/ompi/contrib/vt/vt/vtlib/vt_thrd.c
openmpi-1.3/opal/util/path.c
openmpi-1.3/orte/mca/plm/rsh/plm_rsh_component.c
openmpi-1.3/orte/tools/orterun/debuggers.c
I've attached a p
On Jan 23, 2009, at 4:54 AM, Andrea Iob wrote:
It looks like icc 10.1.021 does not define PATH_MAX
(version 10.1.013 works without problems).
Well that's fun; gotta love when compilers change their behavior. :-)
As a
workaround I've included in those files
where PATH_MAX is used.
What f
It looks like icc 10.1.021 does not define PATH_MAX
(version 10.1.013 works without problems). As a
workaround I've included in those files
where PATH_MAX is used.
Hope it helps.
Andrea
