Error c compiler cannot create executables centos

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 Version :6

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)

GCC 4

/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.

configure:2669: $? = 0
configure:2658: gcc -v >&5
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)
configure:2669: $? = 0
configure:2658: gcc -V >&5
gcc: error: unrecognized command line option ‘-V’
gcc: fatal error: no input files
compilation terminated.
configure:2669: $? = 1
configure:2658: gcc -qversion >&5
gcc: error: unrecognized command line option ‘-qversion’; did you mean ‘—version’?
gcc: fatal error: no input files
compilation terminated.
configure:2669: $? = 1
configure:2689: checking whether the C compiler works
configure:2711: gcc conftest.c >&5
/usr/bin/ld: crtbegin.o: No such file: No such file or directory
collect2: error: ld returned 1 exit status
configure:2715: $? = 1
configure:2753: result: no
configure: failed program was:
| /* 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 «»
| / end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2758: error: in /usr/local': configure:2760: error: C compiler cannot create executables See config.log’ for more details

—————-

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=’${exec_prefix}/bin’
build=’x86_64-unknown-linux-gnu’
build_alias=»
build_cpu=’x86_64′
build_os=’linux-gnu’
build_vendor=’unknown’
datadir=’${datarootdir}’
datarootdir=’${prefix}/share’
docdir=’${datarootdir}/doc/${PACKAGE_TARNAME}’
dvidir=’${docdir}’
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=’${docdir}’
includedir=’${prefix}/include’
infodir=’${datarootdir}/info’
libdir=’${exec_prefix}/lib’
libexecdir=’${exec_prefix}/libexec’
localedir=’${datarootdir}/locale’
localstatedir=’${prefix}/var’
mandir=’${datarootdir}/man’
oldincludedir=’/usr/include’
pdfdir=’${docdir}’
prefix=’/usr/bin/riscv’
program_transform_name=’s,x,x,’
psdir=’${docdir}’
sbindir=’${exec_prefix}/sbin’
sharedstatedir=’${prefix}/com’
subprojects=»
subprojects_enabled=»
sysconfdir=’${prefix}/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]#
`

From the output you’ve given, you are trying to compile a 32-bit build of apache on a 64 bit system. This is from the intput to configure here:

--host=x86_32-unknown-linux-gnu host_alias=x86_32-unknown-linux-gnu CFLAGS=-m32 LDFLAGS=-m32

Also see the output lines confirming this:

configure:3629: checking build system type
configure:3643: result: x86_64-unknown-linux-gnu
configure:3663: checking host system type
configure:3676: result: x86_32-unknown-linux-gnu
configure:3696: checking target system type
configure:3709: result: x86_32-unknown-linux-gnu

Here it is using a 64 bit build system but a 32 bit host/target. Further down we see:

ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value=-m32

This flag tells gcc to produce 32 bit objects. Your error that the C compiler cannot produce executable is likely caused by not having a 32 bit toolchain present.

Testing your ability to compile 32 bit objects

You can test this by compiling a small C example with the -m32 flag.

// Minimal C example
#include <stdio.h>
int main()
{
   printf("This worksn");
   return 0;
}

Compiling:

gcc -m32 -o m32test m32test.c

If this command fails, then you have a problem with your compiler being able to build 32 bit objects. The error messages emitted from the compiler may be helpful in remedying this.

Remedies

1. Build for a 64 bit target (by removing the configure options forcing a 32 bit build), or
2. Install a 32 bit compiler toolchain

The problem seems to be happening in a header file called «confdefs.h»

confdefs.h is produced by the configure script for use in its tests. It is not your problem.

and the config.log file says that the program failed.

More specifically, it tells you exactly what command was run, and it echos the error messages that were produced and the exit status. Specifically, the command was

/usr/local/hdf-4.2.12-linux-centos7-x86_64/bin/h4cc conftest.c >&5

That’s attempting to use the compiler you designated by setting the CC environment variable when you ran configure, which it earlier identified as GCC based on the output when run with the --version option.

And these errors were emitted in the failing compilation:

gcc: error: /mnt/scr1/pre-release/hdf4/v4.2.12/thg-builds/moohan-stati/lib/libmfhdf.a: No such file or directory

gcc: error: /mnt/scr1/pre-release/hdf4/v4.2.12/thg-builds/moohan-static/lib/libdf.a: No such file or directory

Those seem to be emitted every time the designated compiler is run. They are worrisome in part because diagnostics marked as errors are always worrisome, but also specifically because they suggest that the HDF4 package in which the h4cc script resides is probably incorrectly installed or incorrectly configured.

Moreover, the compiler script exited with exit status 1 (not 0) and, apparently, did not produce a compiled output file. Other outputs suggest that although it is probably a wrapper around gcc, it has its own set of options that it honors exclusively, rejecting all others, so that it is not a viable general-purpose subtitute for gcc.

I’m uncertain why you are trying to substitute the h4cc script for the system’s default compiler, and the most obvious thing to try would be to not do so. If you run the configure script without defining the CC environment variable, or defining it as the path to the bare gcc binary, then the configure script should be a lot happier.

Also consult the installation instructions for the package you are trying to build. They very likely have instructions for how to point it to your HDF installation, which is likely one of the intended purposes of h4cc. Any other purposes, such as providing installation-specific compile options, should be subsumed by the build system of the package you are trying to build.

Модератор: Модераторы разделов

echo "#include<stdio.h>" > proba.c
echo "int main() {printf("Hello Worldn");}" >> proba.c
gcc proba.c
./a.out

root@pentium02-desktop:/# echo "#include<stdio.h>" > proba.c
root@pentium02-desktop:/# echo "int main() {printf("Hello Worldn");}" >> proba.c
root@pentium02-desktop:/# gcc proba.c
proba.c:1:19: error: stdio.h: No such file or directory
proba.c: В функции ‘main’
proba.c:2: предупреждение: incompatible implicit declaration of built-in function ‘printf’
root@pentium02-desktop:/# ./a.out
-bash: ./a.out: No such file or directory
root@pentium02-desktop:/#