My apologies. I installed libevent-devel which fixed this
Now I have to install mxm.. But that is a different matter.
On Mon, 12 Apr 2021, 17:52 Jeff Squyres (jsquyres),
wrote:
> It's not really a problem, per se -- it's that Open MPI needs a lib event
> with thread support enabled. The lib ev
It's not really a problem, per se -- it's that Open MPI needs a lib event with
thread support enabled. The lib event that configure found / tried to use did
not have thread support enabled.
What was the command line you used to invoke configure?
> On Apr 11, 2021, at 1:52 PM, John Hearns via
On Apr 27, 2015, at 5:02 PM, Walt Brainerd wrote:
>
> CC constants.lo
> In file included from ../../../../opal/include/opal_config_bottom.h:256:0,
> from ../../../../opal/include/opal_config.h:2797,
> from ../../../../ompi/include/ompi_config.h:27,
>
This is the end of "make all install". I understand this "all-recursive"
thing
is a problem with a GNU compiler. Is there a way around this? I can save
the whole response to the make script and submit it if you want it, but I
assume this is something known.
PPFC profile/pfile_write_shared_f0
On 4/27/2015 8:54 PM, Jeff Squyres (jsquyres) wrote:
Marco --
Have you run into this?
The m4 line in question that seems to be the problem is:
[AS_VAR_SET(type_var, [`cat conftestval`])]
Does `cat foo` in cygwin result in a ^M in the resulting shell string? If so,
is there a standard w
I think I had some Mingw compilers ahead of cygwin
in my path when I did that configure. I tried it again and
it appears to have run to the end, even though I got quite a
few lines with "error" and it says "couldn't remove
conftest.exe ... busy". I'll send config.log if you want.
I am running make
Marco --
Have you run into this?
The m4 line in question that seems to be the problem is:
[AS_VAR_SET(type_var, [`cat conftestval`])]
Does `cat foo` in cygwin result in a ^M in the resulting shell string? If so,
is there a standard way to get rid of it?
> On Apr 27, 2015, at 2:17 PM, W
On Feb 24, 2006, at 12:17 PM, Pierre Valiron wrote:
*** Fortran 90/95 compiler
checking whether we are using the GNU Fortran compiler... no
checking whether f95 accepts -g... yes
checking for Fortran flag to compile .f files... none
checking for Fortran flag to compile .f90 files... none
checkin
Thanks, I have configured also for f77 as you suggest.
The configure now completes, however it outputs a strange error message:
*** Fortran 90/95 compiler
checking whether we are using the GNU Fortran compiler... no
checking whether f95 accepts -g... yes
checking for Fortran flag to compile .f f
On Feb 24, 2006, at 5:25 AM, Pierre Valiron wrote:
I have tried to build the 1.0.2a8 version on Solaris Opteron with
Sun Studio 11.
The configure fails on attempting to guess the largest fortran
integer. I attach my build script, and output from configure.
Hopefully there is a simple fix.
10 matches
Mail list logo
