C compiler cannot create executables linux

C++ compiler cannot create executables #738

Comments

thw1021 commented Jul 22, 2019

Dear developers,
I am trying to install SU2 in docker ubuntu 18.04 container so that I can easily share with partner. But I failed to compile the code with following errors:

I am sure that I have installed gcc/g++ successfully. You can see

I have uploaded the config.log file. Could you give me some suggestions, please?
config.log

The text was updated successfully, but these errors were encountered:

18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (base) root@a5502eb:/home# g++ -o hello hello.cc (base) root@a5502eb:/home# ./hello Hello, World! I have uploaded the config.log file. Could you give me some suggestions, please? config.log — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or mute the thread .

thw1021 commented Jul 22, 2019

Yes. I did have installed g++.

vdweide commented Jul 22, 2019

What about mpicc and mpicxx? You are trying to build a parallel executable, so is MPI installed?

thw1021 commented Jul 22, 2019

I install OpenMPI following the instructions with commands:

and I can see the version

vdweide commented Jul 22, 2019

Are the compiler wrappers, mpicc and mpicxx, also installed? When I look in your log file it mentions
./configure: line 3362: /usr/bin/mpicxx: No such file or directory

talbring commented Jul 22, 2019

Below you can find the steps I used to build a singularity container using ubuntu 19.04. For pure docker and ubuntu 18.04 the steps should be the same I guess.

thw1021 commented Jul 22, 2019

Sorry. Do you mean that although I have installed OpenMPI, I still have to install mpicc and mpicxx ? I am not familiar with such problems.
When I run which mpicc and which mpicxx in the container, there is no outputs. But on the host machine, I can see /usr/bin/mpicc and /usr/bin/mpicxx . Maybe this the reason.

talbring commented Jul 22, 2019

And btw in case you want to really use MPI with containers, you should use singularity (https://sylabs.io/) as it is exactly designed for this.

thw1021 commented Jul 22, 2019 •

Yes. Thank you all. I installed libopenmpi-dev and openmpi-common. I don’t know which one is the key but I can see SU2_RUN and SU2_HOME environment variables displayed at the conclusion of configure.

thw1021 commented Jul 22, 2019

Thank you. I will close this issue after I make sure that I have installed successfully.

thw1021 commented Jul 22, 2019

@talbring
Could you give me more instructions about parallel computing in docker container, please ? I can commit the container to an image, so is there any difference ?

thw1021 commented Jul 22, 2019 •

Thank you all.
When I run the tutorial case with mpirun , there are some warnings:

Should I directly ignore such warnings ? Any suggestion would be grateful.

talbring commented Jul 22, 2019

OpenMPI is not officially supported when using a docker container. See my comment above and open-mpi/ompi#3625 (comment)

talbring commented Jul 22, 2019

Here is the full definition file for singularity:

Store it in file called su2.def and run

You can then run it like that:

The only thing to note is that the OpenMPI version you use inside the container and on the machine you want to run it should be similar. I tried it with OpenMPI v3 in the container and OpenMPI v4 outside and it worked.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

C compiler cannot create executables

C compiler cannot create executables

Post by Crojav » Thu Feb 14, 2019 7:05 pm

I tried to install https://github.com/mansr/sox a Sox Audio Tool Fork on my LinuxMint 19, but got this error.

configure:3617: error: in `/home/crojav/sox’:
configure:3619: error: C compiler cannot create executables
See `config.log’ for more details

Should I include the «config.log»?

Re: C compiler cannot create executables

Post by ajgringo619 » Thu Feb 14, 2019 7:42 pm

Re: C compiler cannot create executables

Post by Crojav » Fri Feb 15, 2019 12:09 pm

Re: C compiler cannot create executables

Post by Hoser Rob » Fri Feb 15, 2019 12:52 pm

Re: C compiler cannot create executables

Post by Crojav » Fri Feb 15, 2019 1:36 pm

Re: C compiler cannot create executables

Post by Crojav » Sat Feb 16, 2019 4:07 pm

I have send the config.log to the maintainer of the program.

Re: C compiler cannot create executables

Post by Crojav » Sat Feb 16, 2019 6:01 pm

This is the answer of the maintainer of the program:

This is the relevant part of the log:

It is clear from this that your compiler is broken. Is it the official
distribution package? You need to take this to whoever provided the
compiler. I’m sorry, but there is nothing I can do to help here.

Any help would be welcom

Re: C compiler cannot create executables

Post by ajgringo619 » Sat Feb 16, 2019 6:08 pm

Re: C compiler cannot create executables

Post by Crojav » Sun Feb 17, 2019 3:07 am

/sox$ sudo apt install build-essential
[sudo] wachtwoord voor crojav:
Pakketlijsten worden ingelezen. Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen. Klaar
De volgende extra pakketten zullen geïnstalleerd worden:
g++ g++-7 libc-dev-bin libc6-dev libstdc++-7-dev
Voorgestelde pakketten:
g++-multilib g++-7-multilib gcc-7-doc libstdc++6-7-dbg glibc-doc libstdc++-7-doc
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
build-essential g++ g++-7 libc-dev-bin libc6-dev libstdc++-7-dev
0 opgewaardeerd, 6 nieuw geïnstalleerd, 0 te verwijderen en 75 niet opgewaardeerd.
Er moeten 11,7 MB aan archieven opgehaald worden.
Na deze bewerking zal er 60,4 MB extra schijfruimte gebruikt worden.
Wilt u doorgaan? [J/n] j
Ophalen:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc-dev-bin amd64 2.27-3ubuntu1 [71,8 kB]
Ophalen:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc6-dev amd64 2.27-3ubuntu1 [2587 kB]
Ophalen:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libstdc++-7-dev amd64 7.3.0-27ubuntu1

18.04 [1463 kB]
Ophalen:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 g++-7 amd64 7.3.0-27ubuntu1

18.04 [7570 kB]
Ophalen:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 g++ amd64 4:7.3.0-3ubuntu2.1 [1572 B]
Ophalen:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 build-essential amd64 12.4ubuntu1 [4758 B]
11,7 MB opgehaald in 2s (4710 kB/s)
debconf: kan het frontend niet initialiseren: Dialog
debconf: (Het dialoog-frontend vereist een scherm dat tenminste 13 regels hoog en 31 kolommen breed is.)
debconf: er wordt teruggevallen op frontend: Readline
Voorheen niet geselecteerd pakket libc-dev-bin wordt geselecteerd.
(Database wordt ingelezen . 262858 bestanden en mappen momenteel geïnstalleerd.)
Uitpakken van . /0-libc-dev-bin_2.27-3ubuntu1_amd64.deb wordt voorbereid.
Bezig met uitpakken van libc-dev-bin (2.27-3ubuntu1) .
Voorheen niet geselecteerd pakket libc6-dev:amd64 wordt geselecteerd.
Uitpakken van . /1-libc6-dev_2.27-3ubuntu1_amd64.deb wordt voorbereid.
Bezig met uitpakken van libc6-dev:amd64 (2.27-3ubuntu1) .
Voorheen niet geselecteerd pakket libstdc++-7-dev:amd64 wordt geselecteerd.
Uitpakken van . /2-libstdc++-7-dev_7.3.0-27ubuntu1

18.04_amd64.deb wordt voorbereid.
Bezig met uitpakken van libstdc++-7-dev:amd64 (7.3.0-27ubuntu1

18.04) .
Voorheen niet geselecteerd pakket g++-7 wordt geselecteerd.
Uitpakken van . /3-g++-7_7.3.0-27ubuntu1

18.04_amd64.deb wordt voorbereid.
Bezig met uitpakken van g++-7 (7.3.0-27ubuntu1

18.04) .
Voorheen niet geselecteerd pakket g++ wordt geselecteerd.
Uitpakken van . /4-g++_4%3a7.3.0-3ubuntu2.1_amd64.deb wordt voorbereid.
Bezig met uitpakken van g++ (4:7.3.0-3ubuntu2.1) .
Voorheen niet geselecteerd pakket build-essential wordt geselecteerd.
Uitpakken van . /5-build-essential_12.4ubuntu1_amd64.deb wordt voorbereid.
Bezig met uitpakken van build-essential (12.4ubuntu1) .
Bezig met afhandelen van triggers voor man-db (2.8.3-2ubuntu0.1) .
Instellen van libc-dev-bin (2.27-3ubuntu1) .
Instellen van libc6-dev:amd64 (2.27-3ubuntu1) .
Instellen van libstdc++-7-dev:amd64 (7.3.0-27ubuntu1

18.04) .
Instellen van g++-7 (7.3.0-27ubuntu1

18.04) .
Instellen van g++ (4:7.3.0-3ubuntu2.1) .
update-alternatives: /usr/bin/g++ wordt gebruikt om in de automatische modus in /usr/bin/c++ (c++) te voorzien.
Instellen van build-essential (12.4ubuntu1) .
crojav@crojav-hp:

Источник

Arch Linux

You are not logged in.

#1 2010-02-03 16:13:19

[SOLVED] configure: error: C compiler cannot create executables

I have tried to build three AUR packages, but the builds always fail with the following output:

I could not find the indicated config.log file.

I installed all the dependencies indicated in the wiki, but I have a feeling I must be missing basic in my configuration. Both gcc and base-devel are installed. I’ve also run makepkg as root. What amI doing wrong?

Last edited by intelligo (2010-02-04 00:33:14)

#2 2010-02-03 16:54:53

Re: [SOLVED] configure: error: C compiler cannot create executables

Well, post the `config.log’ from the failed build (should be at /home/learner/builds/tuxmath/src/tuxmath_w_fonts-1.7.2/config.log).

Also your /etc/makepkg.conf might help.

#3 2010-02-03 17:17:03

Re: [SOLVED] configure: error: C compiler cannot create executables

Here’s the config,log:

And here’s makepkg.conf:

Thanks for your help!

#4 2010-02-03 22:11:00

Re: [SOLVED] configure: error: C compiler cannot create executables

This is the offending line from config.log

It looks like your gcc package is corrupted, or has the wrong architecture (i686 instead of x86-64, for example). Try «pacman -Sf gcc».

Last edited by tavianator (2010-02-03 22:12:03)

#5 2010-02-04 00:31:57

Re: [SOLVED] configure: error: C compiler cannot create executables

Thanks, tavianator! Both my gcc and base-devel were somehow corrupted, but after forcing a reinstall my builds are going along nicely.

Источник

Getting configure: error: C compiler cannot create executables error #635

Comments

thakureie commented May 14, 2020

We have two GCC versions 4 & 6 however we could see error while installing this. Please help. «

Getting configure: error: C compiler cannot create executables error

cat /etc/redhat-release
CentOS release 6.10 (Final)

uname -a
Linux XXX 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/6.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure
Thread model: posix
gcc version 6.1.0 (GCC)

/usr/bin/gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure —prefix=/usr —mandir=/usr/share/man —infodir=/usr/share/info —with-bugurl=http://bugzilla.redhat.com/bugzilla —enable-bootstrap —enable-shared —enable-threads=posix —enable-checking=release —with-system-zlib —enable-__cxa_atexit —disable-libunwind-exceptions —enable-gnu-unique-object —enable-languages=c,c++,objc,obj-c++,java,fortran,ada —enable-java-awt=gtk —disable-dssi —with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre —enable-libgcj-multifile —enable-java-maintainer-mode —with-ecj-jar=/usr/share/java/eclipse-ecj.jar —disable-libjava-multilib —with-ppl —with-cloog —with-tune=generic —with-arch_32=i686 —build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC)

export RISCV=/usr/bin/riscv
/root/riscv-isa-sim-master/configure —prefix=$RISCV —enable-commitlog —enable-misaligned
checking build system type. x86_64-unknown-linux-gnu
checking host system type. x86_64-unknown-linux-gnu
checking for gcc. gcc
checking whether the C compiler works. no
configure: error: in /usr/local’: configure: error: C compiler cannot create executables See config.log’ for more details

`[root@asic-5 local]# cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by RISC-V ISA Simulator configure ?, which was
generated by GNU Autoconf 2.69. Invocation command line was

$ /root/riscv-isa-sim-master/configure —prefix=/usr/bin/riscv —enable-commitlog —enable-misaligned

Platform.

hostname = asic-5.enphaseenergy.com
uname -m = x86_64
uname -r = 2.6.32-754.28.1.el6.x86_64
uname -s = Linux
uname -v = #1 SMP Wed Mar 11 18:38:45 UTC 2020

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/lib64/qt-3.3/bin
PATH: /usr/share/lsf/9.1/linux2.6-glibc2.3-x86_64/etc
PATH: /usr/share/lsf/9.1/linux2.6-glibc2.3-x86_64/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /opt/dell/srvadmin/bin
PATH: /opt/dell/srvadmin/sbin
PATH: /root/bin

Core tests.

configure:2127: checking build system type
configure:2141: result: x86_64-unknown-linux-gnu
configure:2161: checking host system type
configure:2174: result: x86_64-unknown-linux-gnu
configure:2393: checking for gcc
configure:2409: found /usr/local/bin/gcc
configure:2420: result: gcc
configure:2649: checking for C compiler version
configure:2658: gcc —version >&5
gcc (GCC) 6.1.0
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Cache variables.

ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_STOW_PREFIX_set=
ac_cv_env_STOW_PREFIX_value=
ac_cv_env_STOW_ROOT_set=
ac_cv_env_STOW_ROOT_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_prog_ac_ct_CC=gcc

Output variables.

AR=»
CC=’gcc’
CFLAGS=»
CPPFLAGS=»
CXX=»
CXXCPP=»
CXXFLAGS=»
DEFS=»
DTC=»
ECHO_C=»
ECHO_N=’-n’
ECHO_T=»
EGREP=»
EXEEXT=»
GREP=»
HAVE_INT128=»
INSTALL_DATA=»
INSTALL_PROGRAM=»
INSTALL_SCRIPT=»
LDFLAGS=»
LIBOBJS=»
LIBS=»
LTLIBOBJS=»
OBJEXT=»
PACKAGE_BUGREPORT=’Andrew Waterman’
PACKAGE_NAME=’RISC-V ISA Simulator’
PACKAGE_STRING=’RISC-V ISA Simulator ?’
PACKAGE_TARNAME=’spike’
PACKAGE_URL=»
PACKAGE_VERSION=’?’
PATH_SEPARATOR=’:’
RANLIB=»
SHELL=’/bin/sh’
STOW_PREFIX=»
STOW_ROOT=»
ac_ct_CC=’gcc’
ac_ct_CXX=»
bindir=’$/bin’
build=’x86_64-unknown-linux-gnu’
build_alias=»
build_cpu=’x86_64′
build_os=’linux-gnu’
build_vendor=’unknown’
datadir=’$‘
datarootdir=’$/share’
docdir=’$/doc/$‘
dvidir=’$‘
enable_stow=»
exec_prefix=’NONE’
host=’x86_64-unknown-linux-gnu’
host_alias=»
host_cpu=’x86_64′
host_os=’linux-gnu’
host_vendor=’unknown’
htmldir=’$‘
includedir=’$/include’
infodir=’$/info’
libdir=’$/lib’
libexecdir=’$/libexec’
localedir=’$/locale’
localstatedir=’$/var’
mandir=’$/man’
oldincludedir=’/usr/include’
pdfdir=’$‘
prefix=’/usr/bin/riscv’
program_transform_name=’s,x,x,’
psdir=’$‘
sbindir=’$/sbin’
sharedstatedir=’$/com’
subprojects=»
subprojects_enabled=»
sysconfdir=’$/etc’
target_alias=»

confdefs.h.

/* confdefs.h */
#define PACKAGE_NAME «RISC-V ISA Simulator»
#define PACKAGE_TARNAME «spike»
#define PACKAGE_VERSION «?»
#define PACKAGE_STRING «RISC-V ISA Simulator ?»
#define PACKAGE_BUGREPORT «Andrew Waterman»
#define PACKAGE_URL «»

configure: exit 77
[root@asic-5 local]#
`

The text was updated successfully, but these errors were encountered:

Источник