[Difx-users] difx 2.4.1 compile error in Mark5B+ "configure: error: C++ compiler cannot create executables"

[Jongsoo Kim]

Dear Walter and Jay,

The compile issue was now sorted out.  I would like to ask the following question.

Is there any body who tried the native correlation with Mark5B+, whose OS is the 64bit one?  If any, please tell me your successful (or unsuccessful) story.

Best regards,
Jongsoo


On Jul 11, 2017, at 9:47 AM, Walter Brisken <wbrisken at lbo.us<mailto:wbrisken at lbo.us>> wrote:


Good call on the compiler being an issue.

It could be g++ itself, or the MPI software (e.g., openmpi, with compiler called mpicxx) was not found.  openmpi is the most commonly used MPI package with DiFX.

-W

On Tue, 11 Jul 2017, Jay Blanchard wrote:

Are you sure you have g++ installed?
I think it's in package build-essential in debian...

On 10 July 2017 at 13:30, Jongsoo Kim <jskim at kasi.re.kr<mailto:jskim at kasi.re.kr>> wrote:

Dear DIFX users,

I am trying to install DiFX 2.4.1 in a MarkB+ in order to do remote
distributed correlation using the native mode of Mark5 for the KVN
observations.   The installation options are as follows,

./install-difx --noipp --nodoc --mk5daemon

The above commend compiles packages of "difxio", "difxmessages", and
"mark5access" without any problems.  But it generates the attached error
message when it comes to the mpifxcorr package.

The Mark5B+ system has Debian Wheezy 32bit OS.  The output of "uname -a"
is as follows.

2.6.32-5-686 #1 SMP Mon Sep 23 23:00:18 UTC 2013 i686 GNU/Linux

Most of the Debian packages required for the difx described in the difx
web site were installed except openmpi.

  - pkg-config
  - bison
  - flex
  - libexpat1-dev
  - fftw3-dev
  - autoconf
  - automake
  - libtool
  - gfortran

The openmpi 1.10.2 was manually installed with --enable-heterogeneous.
Do you have any idea to sort out the problem that I have?

I have the other question. Is there any body who tried the native
correlation with Mark5B+, whose OS is the 64bit one?  If any, please tell
me your successful (or unsuccessful) story to me.

Best regards,

Jongsoo
------------------------------

Making mpifxcorr


Reconfiguring mpifxcorr

configure.ac:1: warning: AC_INIT: not a literal: Adam Deller <
adeller at astro.swin.edu.au<mailto:adeller at astro.swin.edu.au>>

configure.ac:1: warning: AC_INIT: not a literal: Adam Deller <
adeller at astro.swin.edu.au<mailto:adeller at astro.swin.edu.au>>

configure.ac:1: warning: AC_INIT: not a literal: Adam Deller <
adeller at astro.swin.edu.au<mailto:adeller at astro.swin.edu.au>>

configure.ac:1: warning: AC_INIT: not a literal: Adam Deller <
adeller at astro.swin.edu.au<mailto:adeller at astro.swin.edu.au>>

configure.ac:5: installing `./install-sh'

configure.ac:5: installing `./missing'

src/Makefile.am: installing `./depcomp'

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking whether the C++ compiler works... no

configure: error: in `/root/DiFX-2.4.1/mpifxcorr':

configure: error: C++ compiler cannot create executables

See `config.log' for more details

Traceback (most recent call last):

 File "./install-difx", line 667, in <module>

   run(configstring)

 File "./install-difx", line 353, in run

   raise RuntimeError, "Error running " + cmd + " in " + os.getcwd()

RuntimeError: Error running ./configure CXX=/opt/openmpi-1.10.2
--prefix=/opt/difx/2.4.1 in /root/DiFX-2.4.1/mpifxcorr

_______________________________________________
Difx-users mailing list
Difx-users at listmgr.nrao.edu<mailto:Difx-users at listmgr.nrao.edu>
https://listmgr.nrao.edu/mailman/listinfo/difx-users




--
-------------------------
Walter Brisken
Director
Long Baseline Observatory
(575)-835-7133 (office)
(505)-234-5912 (cell)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/difx-users/attachments/20170711/73f008a1/attachment-0001.html>