Mailing List Archive: C compiler cannot create executables

C compiler cannot create executables

Mar 31, 2005, 11:09 AM

Post #1 of 15 (607 views)

First excuse my english. But nobody on the Scandinavian forum know what is wrong.
(norwegian version at http://forums.gentoo.org/viewtopic-t-316515.html)

I get the error after updating the system to 2005.0 using this guide http://www.gentoo.org/proj/en/base/amd64/2005.0-upgrade-amd64.xml#doc_chap2 (The scripted way) I received no error under the install of 2005.0.

[maybe important or maybe not important at all]
The day before the upgrade i fix a bug I had with gcc. I was unable to oppgrade (or downgrade) gcc. but this bug report fixed it. http://bugs.gentoo.org/show_bug.cgi?id=86123

The advice was:
rm -f /usr/lib32
ln -s ../../emul/linux/x86/usr/lib /usr/lib32
FEATURES=-sandbox emerge gcc

This fix the update off gcc problem. (but i am wondering it may break somting else?)

Tings I have tested:
1) fix_libtool_files.sh 3.4.2
2) gcc-config 1
3) Edit /etc/ld.so.conf all gcc paths point to 3.4.3-20050110 and not 3.4.2
4) Dubble checked make.conf for errors/typos
5) Compile with out any CFLAGS and CXXFLAGS

I am aware of Bug 73435 ( http://bugs.gentoo.org/show_bug.cgi?id=73435 ) But I can't see how to fix my system with the answers given in this bug-report.

ikaro point out "20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory" as the error line but I don't now how to use this info :-(

System info:

spetznaz@Mjolne ~ $ gcc-config -l
[1] x86_64-pc-linux-gnu-3.4.2
[2] x86_64-pc-linux-gnu-3.4.2-hardened
[3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
[4] x86_64-pc-linux-gnu-3.4.3-20050110 *
[5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
[6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
[7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp

spetznaz@Mjolne ~ $ emerge --info
Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.2 0050125-r1, 2.6.11-gentoo-r4 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.6.10
Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 29 2005, 02:30:26)]
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disab led]
dev-lang/python: 2.3.5
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.9.5, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.8.5-r3
sys-devel/binutils: 2.15.92.0.2-r7
sys-devel/libtool: 1.5.14
virtual/os-headers: 2.6.8.1-r4
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-march=k8 -O3 -pipe -frename-registers -fweb"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share /config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/shar e/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O3 -pipe -frename-registers -fweb"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="ftp://ftp.linux.ee/pub/gentoo/distfiles/ ftp://mirror.pudas.net/ gentoo ftp://trumpetti.atm.tut.fi/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X acpi alsa amd64 avi berkdb bidi bitmap-fonts cdr crypt dba directfb dvd d vdr dvdread encode fam fbcon ffmpeg flac font-server fortran freetype gd ggi gif gimp gpm gtk gtk2 imlib ipv6 jp2 jpeg kde libcaca lzw lzw-tiff mad motif mp3 mp eg mysql ncurses nls ogg oggvorbis opengl oss pam perl png python qt readline sd l spell ssl svg tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userloca les wxwindows xml2 xmms xpm xrandr xv xvid zlib"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

Error report:
I get this type of error for anyting i try to emerge. irssi as an exampel

>>> Source unpacked.
* econf: updating irssi-0.8.10-rc5/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating irssi-0.8.10-rc5/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-glib2 --without-servertest --with-proxy --with-ncurses --enable-nls --with-perl --enable-ipv6 --without-socks --with-openssl-include=/usr --with-openssl-libs=/usr
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... found
checking for working autoconf... found
checking for working automake-1.4... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/irssi-0.8.10_rc5-r1/work/irssi-0.8.10-rc5/config.log

!!! ERROR: net-irc/irssi-0.8.10_rc5-r1 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.

The config.log file

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.59. Invocation command line was

$ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-glib2 --without-servertest --with-proxy --with-ncurses --enable-nls --with-perl --enable-ipv6 --without-socks --with-openssl-include=/usr --with-openssl-libs=/usr

## --------- ##
## Platform. ##
## --------- ##

hostname = Mjolne
uname -m = x86_64
uname -r = 2.6.11-gentoo-r4
uname -s = Linux
uname -v = #1 Wed Mar 23 19:42:54 CET 2005

/usr/bin/uname -p = AMD Athlon(tm) 64 Processor 3000+
/bin/uname -X = unknown

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

PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib/portage/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110
PATH: /opt/ati/bin
PATH: /usr/X11R6/bin
PATH: /usr/qt/3/bin
PATH: /usr/kde/3.4/sbin
PATH: /usr/kde/3.4/bin
PATH: /opt/vmware/bin

## ----------- ## ## Core tests. ## ## ----------- ## configure:1576: checking for a BSD-compatible install configure:1631: result: /bin/install -c configure:1642: checking whether build environment is sane
configure:1685: result: yes
configure:1700: checking whether make sets $(MAKE)
configure:1720: result: yes
configure:1752: checking for working aclocal-1.4
configure:1759: result: found
configure:1767: checking for working autoconf
configure:1774: result: found
configure:1782: checking for working automake-1.4
configure:1789: result: found configure:1797: checking for working autoheader
configure:1804: result: found
configure:1812: checking for working makeinfo
configure:1819: result: found
configure:1829: checking whether to enable maintainer-specific portions of Makefiles
configure:1838: result: no
configure:1861: checking for x86_64-pc-linux-gnu-gcc
configure:1877: found /usr/bin/x86_64-pc-linux-gnu-gcc
configure:1887: result: x86_64-pc-linux-gnu-gcc
configure:2169: checking for C compiler version
configure:2172: x86_64-pc-linux-gnu-gcc --version </dev/null >&5
x86_64-pc-linux-gnu-gcc (GCC) 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r1, ssp-3.4.3.20050110-0, pie-8.7.7)
Copyright (C) 2004 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:2175: $? = 0
configure:2177: x86_64-pc-linux-gnu-gcc -v </dev/null >&5
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/specs Configured with: /var/tmp/portage/gcc-3.4.3.20050110-r1/work/gcc-3.4.3/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include/g++-v3 --host=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --enable-multilib --disable-libgcj --enable-languages=c,c++,f77 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r1, ssp-3.4.3.20050110-0, pie-8.7.7)
configure:2180: $? = 0
configure:2182: x86_64-pc-linux-gnu-gcc -V </dev/null >&5
x86_64-pc-linux-gnu-gcc: `-V' must come at the start of the command line
configure:2185: $? = 1
configure:2208: checking for C compiler default output file name
configure:2211: x86_64-pc-linux-gnu-gcc -march=k8 -O3 -pipe -frename-registers -fweb conftest.c >&5 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:2214: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "irssi"
| #define VERSION "0.8.10-rc5"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2253: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-march=k8 -O3 -pipe -frename-registers -fweb'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=set
ac_cv_env_CXXFLAGS_value='-march=k8 -O3 -pipe -frename-registers -fweb'
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=x86_64-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/bin/install -c'
ac_cv_prog_CC=x86_64-pc-linux-gnu-gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='aclocal-1.4'
AR=''
AUTOCONF='autoconf'
AUTOHEADER='autoheader'
AUTOMAKE='automake-1.4'
BUILD_IRSSIBOT_FALSE=''
BUILD_IRSSIBOT_TRUE=''
BUILD_IRSSIPROXY_FALSE=''
BUILD_IRSSIPROXY_TRUE=''
BUILD_PLUGINS_FALSE=''
BUILD_PLUGINS_TRUE=''
BUILD_TEXTUI_FALSE=''
BUILD_TEXTUI_TRUE=''
CC='x86_64-pc-linux-gnu-gcc'
CFLAGS='-march=k8 -O3 -pipe -frename-registers -fweb'
CHAT_MODULES=''
COMMON_LIBS=''
COMMON_NOUI_LIBS=''
CPP=''
CPPFLAGS=''
CURSES_INCLUDEDIR=''
CURSES_LIBS=''
CXX=''
CXXCPP=''
CXXFLAGS='-march=k8 -O3 -pipe -frename-registers -fweb'
DEFS=''
DYNALOADER_A=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
GLIB_CFLAGS=''
GLIB_CONFIG=''
GLIB_GENMARSHAL=''
GLIB_LIBS=''
GLIB_MKENUMS=''
GOBJECT_QUERY=''
HAVE_PERL_FALSE=''
HAVE_PERL_TRUE=''
HAVE_STATIC_PERL_FALSE=''
HAVE_STATIC_PERL_TRUE=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
LDFLAGS=''
LIBOBJS=''
LIBPERL_A=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='makeinfo'
NEED_TPARM_FALSE=''
NEED_TPARM_TRUE=''
OBJEXT=''
PACKAGE='irssi'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
PERL_CFLAGS=''
PERL_EXTRA_OPTS=''
PERL_FE_LINK_LIBS=''
PERL_LDFLAGS=''
PERL_LIBTOOL=''
PERL_LINK_FLAGS=''
PERL_LINK_LIBS=''
PERL_MM_PARAMS=''
PERL_STATIC_LIBS=''
PERL_USE_LIB=''
PKG_CONFIG=''
PROG_LIBS=''
RANLIB=''
SET_MAKE=''
SHELL='/bin/sh'
SSL_CFLAGS=''
SSL_LIBS=''
STRIP=''
TEXTUI_LIBS=''
USE_CURSES_FALSE=''
USE_CURSES_TRUE=''
VERSION='0.8.10-rc5'
VERSION_DATE=''
VERSION_TIME=''
ac_ct_AR=''
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='/usr/share'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias='x86_64-pc-linux-gnu'
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='/usr/share/info'
irc_MODULES=''
libdir='/usr/lib64'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
oldincludedir='/usr/include'
perl_module_fe_lib=''
perl_module_lib=''
perl_static_fe_lib=''
perl_static_lib=''
perlpath=''
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sedpath=''
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE "irssi"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define VERSION "0.8.10-rc5"

configure: exit 77
--
gentoo-user@gentoo.org mailing list

RE: C compiler cannot create executables [ In reply to ]

dnebinger at joat

Mar 31, 2005, 11:31 AM

Post #2 of 15 (589 views)

Permalink

> The advice was:
> rm -f /usr/lib32
> ln -s ../../emul/linux/x86/usr/lib /usr/lib32
> FEATURES=-sandbox emerge gcc
>
> This fix the update off gcc problem. (but i am wondering it may break
> somting else?)

Well probably you lost your /usr/lib32's file crt1.o file. Bummer.

If you remember what the old /usr/lib32 link was you might be able to copy
it back to /usr/lib32.

To properly repair your system you should probably re-emerge glibc now that
gcc is functioning again, but you'll need to get by the missing crt1.o file
before you'll be able to do that.

--
gentoo-user@gentoo.org mailing list

Re: C compiler cannot create executables [ In reply to ]

spetznaz at internettledelsen

Mar 31, 2005, 12:25 PM

Post #3 of 15 (592 views)

Permalink

On Thu, 31 Mar 2005 13:31:19 -0500
"Dave Nebinger" <dnebinger@joat.com> wrote:

> > The advice was:
> > rm -f /usr/lib32
> > ln -s ../../emul/linux/x86/usr/lib /usr/lib32
> > FEATURES=-sandbox emerge gcc
> >
> > This fix the update off gcc problem. (but i am wondering it may break
> > somting else?)
>
> Well probably you lost your /usr/lib32's file crt1.o file. Bummer.
>
> If you remember what the old /usr/lib32 link was you might be able to copy
> it back to /usr/lib32.
>
> To properly repair your system you should probably re-emerge glibc now that
> gcc is functioning again, but you'll need to get by the missing crt1.o file
> before you'll be able to do that.
>
>
> --
> gentoo-user@gentoo.org mailing list
>

Well after I updated gcc I run the updatescript and this script merges some pacage (portage gcc-config distcc linux-headers etc..) so gcc was working when i updated the system to 2005.0 else I will received an error.. (at least i suppose so :-)

locate output this:
Mjolne spetznaz # locate crt1.o
/usr/lib32/Mcrt1.o
/usr/lib32/Scrt1.o
/usr/lib32/crt1.o
/usr/lib32/gcrt1.o
/usr/lib64/crt1.o
/usr/lib64/gcrt1.o
/usr/lib64/Mcrt1.o
/usr/lib64/Scrt1.o

so i don't think crt1.o is the issue.

When it fail to compile with no flags at all i can't see how my CFLAGS can be the issue.
--
gentoo-user@gentoo.org mailing list

RE: C compiler cannot create executables [ In reply to ]

dnebinger at joat

Mar 31, 2005, 2:02 PM

Post #4 of 15 (590 views)

Permalink

> Well after I updated gcc I run the updatescript and this script merges
> some pacage (portage gcc-config distcc linux-headers etc..) so gcc was
> working when i updated the system to 2005.0 else I will received an
> error.. (at least i suppose so :-)
>
> locate output this:
> Mjolne spetznaz # locate crt1.o
> /usr/lib32/Mcrt1.o
> /usr/lib32/Scrt1.o
> /usr/lib32/crt1.o
> /usr/lib32/gcrt1.o
> /usr/lib64/crt1.o
> /usr/lib64/gcrt1.o
> /usr/lib64/Mcrt1.o
> /usr/lib64/Scrt1.o
>
> so i don't think crt1.o is the issue.

Well, ld is the one complaining, perhaps it's the issue...

--
gentoo-user@gentoo.org mailing list

Re: C compiler cannot create executables [ In reply to ]

ivan at yosifov

Mar 31, 2005, 2:54 PM

Post #5 of 15 (594 views)

Permalink

http://forums.gentoo.org/viewtopic-t-294109.html
This may help.

On Thu, 2005-03-31 at 20:09 +0200, spetznaz@internettledelsen.com wrote:
> First excuse my english. But nobody on the Scandinavian forum know what is wrong.
> (norwegian version at http://forums.gentoo.org/viewtopic-t-316515.html)
>
> I get the error after updating the system to 2005.0 using this guide http://www.gentoo.org/proj/en/base/amd64/2005.0-upgrade-amd64.xml#doc_chap2 (The scripted way) I received no error under the install of 2005.0.
>
> [maybe important or maybe not important at all]
> The day before the upgrade i fix a bug I had with gcc. I was unable to oppgrade (or downgrade) gcc. but this bug report fixed it. http://bugs.gentoo.org/show_bug.cgi?id=86123
>
> The advice was:
> rm -f /usr/lib32
> ln -s ../../emul/linux/x86/usr/lib /usr/lib32
> FEATURES=-sandbox emerge gcc
>
> This fix the update off gcc problem. (but i am wondering it may break somting else?)
>
> Tings I have tested:
> 1) fix_libtool_files.sh 3.4.2
> 2) gcc-config 1
> 3) Edit /etc/ld.so.conf all gcc paths point to 3.4.3-20050110 and not 3.4.2
> 4) Dubble checked make.conf for errors/typos
> 5) Compile with out any CFLAGS and CXXFLAGS
>
> I am aware of Bug 73435 ( http://bugs.gentoo.org/show_bug.cgi?id=73435 ) But I can't see how to fix my system with the answers given in this bug-report.
>
> ikaro point out "20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory" as the error line but I don't now how to use this info :-(
>
> System info:
>
> spetznaz@Mjolne ~ $ gcc-config -l
> [1] x86_64-pc-linux-gnu-3.4.2
> [2] x86_64-pc-linux-gnu-3.4.2-hardened
> [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
> [4] x86_64-pc-linux-gnu-3.4.3-20050110 *
> [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
> [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
> [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
>
> spetznaz@Mjolne ~ $ emerge --info
> Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.2 0050125-r1, 2.6.11-gentoo-r4 x86_64)
> =================================================================
> System uname: 2.6.11-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+
> Gentoo Base System version 1.6.10
> Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 29 2005, 02:30:26)]
> distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disab led]
> dev-lang/python: 2.3.5
> sys-devel/autoconf: 2.13, 2.59-r6
> sys-devel/automake: 1.9.5, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.8.5-r3
> sys-devel/binutils: 2.15.92.0.2-r7
> sys-devel/libtool: 1.5.14
> virtual/os-headers: 2.6.8.1-r4
> ACCEPT_KEYWORDS="amd64 ~amd64"
> AUTOCLEAN="yes"
> CFLAGS="-march=k8 -O3 -pipe -frename-registers -fweb"
> CHOST="x86_64-pc-linux-gnu"
> CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share /config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/shar e/config /var/qmail/control"
> CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
> CXXFLAGS="-march=k8 -O3 -pipe -frename-registers -fweb"
> DISTDIR="/usr/portage/distfiles"
> FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
> GENTOO_MIRRORS="ftp://ftp.linux.ee/pub/gentoo/distfiles/ ftp://mirror.pudas.net/ gentoo ftp://trumpetti.atm.tut.fi/gentoo/"
> MAKEOPTS="-j2"
> PKGDIR="/usr/portage/packages"
> PORTAGE_TMPDIR="/var/tmp"
> PORTDIR="/usr/portage"
> PORTDIR_OVERLAY="/usr/local/portage"
> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
> USE="X acpi alsa amd64 avi berkdb bidi bitmap-fonts cdr crypt dba directfb dvd d vdr dvdread encode fam fbcon ffmpeg flac font-server fortran freetype gd ggi gif gimp gpm gtk gtk2 imlib ipv6 jp2 jpeg kde libcaca lzw lzw-tiff mad motif mp3 mp eg mysql ncurses nls ogg oggvorbis opengl oss pam perl png python qt readline sd l spell ssl svg tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userloca les wxwindows xml2 xmms xpm xrandr xv xvid zlib"
> Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
>
> Error report:
> I get this type of error for anyting i try to emerge. irssi as an exampel
>
> >>> Source unpacked.
> * econf: updating irssi-0.8.10-rc5/config.guess with /usr/share/gnuconfig/config.guess
> * econf: updating irssi-0.8.10-rc5/config.sub with /usr/share/gnuconfig/config.sub
> ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-glib2 --without-servertest --with-proxy --with-ncurses --enable-nls --with-perl --enable-ipv6 --without-socks --with-openssl-include=/usr --with-openssl-libs=/usr
> configure: WARNING: If you wanted to set the --build type, don't use --host.
> If a cross compiler is detected then cross compile mode will be used.
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets $(MAKE)... yes
> checking for working aclocal-1.4... found
> checking for working autoconf... found
> checking for working automake-1.4... found
> checking for working autoheader... found
> checking for working makeinfo... found
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking for C compiler default output file name... configure: error: C compiler cannot create executables
> See `config.log' for more details.
>
> !!! Please attach the config.log to your bug report:
> !!! /var/tmp/portage/irssi-0.8.10_rc5-r1/work/irssi-0.8.10-rc5/config.log
>
> !!! ERROR: net-irc/irssi-0.8.10_rc5-r1 failed.
> !!! Function econf, Line 485, Exitcode 0
> !!! econf failed
> !!! If you need support, post the topmost build error, NOT this status message.
>
> The config.log file
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by configure, which was
> generated by GNU Autoconf 2.59. Invocation command line was
>
> $ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-glib2 --without-servertest --with-proxy --with-ncurses --enable-nls --with-perl --enable-ipv6 --without-socks --with-openssl-include=/usr --with-openssl-libs=/usr
>
> ## --------- ##
> ## Platform. ##
> ## --------- ##
>
> hostname = Mjolne
> uname -m = x86_64
> uname -r = 2.6.11-gentoo-r4
> uname -s = Linux
> uname -v = #1 Wed Mar 23 19:42:54 CET 2005
>
> /usr/bin/uname -p = AMD Athlon(tm) 64 Processor 3000+
> /bin/uname -X = unknown
>
> /bin/arch = x86_64
> /usr/bin/arch -k = unknown
> /usr/convex/getsysinfo = unknown
> hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /sbin
> PATH: /usr/sbin
> PATH: /usr/lib/portage/bin
> PATH: /bin
> PATH: /usr/bin
> PATH: /opt/bin
> PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110
> PATH: /opt/ati/bin
> PATH: /usr/X11R6/bin
> PATH: /usr/qt/3/bin
> PATH: /usr/kde/3.4/sbin
> PATH: /usr/kde/3.4/bin
> PATH: /opt/vmware/bin
>
>
> ## ----------- ## ## Core tests. ## ## ----------- ## configure:1576: checking for a BSD-compatible install configure:1631: result: /bin/install -c configure:1642: checking whether build environment is sane
> configure:1685: result: yes
> configure:1700: checking whether make sets $(MAKE)
> configure:1720: result: yes
> configure:1752: checking for working aclocal-1.4
> configure:1759: result: found
> configure:1767: checking for working autoconf
> configure:1774: result: found
> configure:1782: checking for working automake-1.4
> configure:1789: result: found configure:1797: checking for working autoheader
> configure:1804: result: found
> configure:1812: checking for working makeinfo
> configure:1819: result: found
> configure:1829: checking whether to enable maintainer-specific portions of Makefiles
> configure:1838: result: no
> configure:1861: checking for x86_64-pc-linux-gnu-gcc
> configure:1877: found /usr/bin/x86_64-pc-linux-gnu-gcc
> configure:1887: result: x86_64-pc-linux-gnu-gcc
> configure:2169: checking for C compiler version
> configure:2172: x86_64-pc-linux-gnu-gcc --version </dev/null >&5
> x86_64-pc-linux-gnu-gcc (GCC) 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r1, ssp-3.4.3.20050110-0, pie-8.7.7)
> Copyright (C) 2004 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:2175: $? = 0
> configure:2177: x86_64-pc-linux-gnu-gcc -v </dev/null >&5
> Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/specs Configured with: /var/tmp/portage/gcc-3.4.3.20050110-r1/work/gcc-3.4.3/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include/g++-v3 --host=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --enable-multilib --disable-libgcj --enable-languages=c,c++,f77 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
> Thread model: posix
> gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r1, ssp-3.4.3.20050110-0, pie-8.7.7)
> configure:2180: $? = 0
> configure:2182: x86_64-pc-linux-gnu-gcc -V </dev/null >&5
> x86_64-pc-linux-gnu-gcc: `-V' must come at the start of the command line
> configure:2185: $? = 1
> configure:2208: checking for C compiler default output file name
> configure:2211: x86_64-pc-linux-gnu-gcc -march=k8 -O3 -pipe -frename-registers -fweb conftest.c >&5 /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory
> collect2: ld returned 1 exit status
> configure:2214: $? = 1
> configure: failed program was:
> | /* confdefs.h. */
> |
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE "irssi"
> | #define VERSION "0.8.10-rc5"
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:2253: error: C compiler cannot create executables
> See `config.log' for more details.
>
> ## ---------------- ##
> ## Cache variables. ##
> ## ---------------- ##
>
> ac_cv_env_CC_set=
> ac_cv_env_CC_value=
> ac_cv_env_CFLAGS_set=set
> ac_cv_env_CFLAGS_value='-march=k8 -O3 -pipe -frename-registers -fweb'
> ac_cv_env_CPPFLAGS_set=
> ac_cv_env_CPPFLAGS_value=
> ac_cv_env_CPP_set=
> ac_cv_env_CPP_value=
> ac_cv_env_CXXCPP_set=
> ac_cv_env_CXXCPP_value=
> ac_cv_env_CXXFLAGS_set=set
> ac_cv_env_CXXFLAGS_value='-march=k8 -O3 -pipe -frename-registers -fweb'
> ac_cv_env_CXX_set=
> ac_cv_env_CXX_value=
> ac_cv_env_F77_set=
> ac_cv_env_F77_value=
> ac_cv_env_FFLAGS_set=
> ac_cv_env_FFLAGS_value=
> ac_cv_env_LDFLAGS_set=
> ac_cv_env_LDFLAGS_value=
> ac_cv_env_build_alias_set=
> ac_cv_env_build_alias_value=
> ac_cv_env_host_alias_set=set
> ac_cv_env_host_alias_value=x86_64-pc-linux-gnu
> ac_cv_env_target_alias_set=
> ac_cv_env_target_alias_value=
> ac_cv_path_install='/bin/install -c'
> ac_cv_prog_CC=x86_64-pc-linux-gnu-gcc
> ac_cv_prog_make_make_set=yes
>
> ## ----------------- ##
> ## Output variables. ##
> ## ----------------- ##
>
> ACLOCAL='aclocal-1.4'
> AR=''
> AUTOCONF='autoconf'
> AUTOHEADER='autoheader'
> AUTOMAKE='automake-1.4'
> BUILD_IRSSIBOT_FALSE=''
> BUILD_IRSSIBOT_TRUE=''
> BUILD_IRSSIPROXY_FALSE=''
> BUILD_IRSSIPROXY_TRUE=''
> BUILD_PLUGINS_FALSE=''
> BUILD_PLUGINS_TRUE=''
> BUILD_TEXTUI_FALSE=''
> BUILD_TEXTUI_TRUE=''
> CC='x86_64-pc-linux-gnu-gcc'
> CFLAGS='-march=k8 -O3 -pipe -frename-registers -fweb'
> CHAT_MODULES=''
> COMMON_LIBS=''
> COMMON_NOUI_LIBS=''
> CPP=''
> CPPFLAGS=''
> CURSES_INCLUDEDIR=''
> CURSES_LIBS=''
> CXX=''
> CXXCPP=''
> CXXFLAGS='-march=k8 -O3 -pipe -frename-registers -fweb'
> DEFS=''
> DYNALOADER_A=''
> ECHO='echo'
> ECHO_C=''
> ECHO_N='-n'
> ECHO_T=''
> EGREP=''
> EXEEXT=''
> F77=''
> FFLAGS=''
> GLIB_CFLAGS=''
> GLIB_CONFIG=''
> GLIB_GENMARSHAL=''
> GLIB_LIBS=''
> GLIB_MKENUMS=''
> GOBJECT_QUERY=''
> HAVE_PERL_FALSE=''
> HAVE_PERL_TRUE=''
> HAVE_STATIC_PERL_FALSE=''
> HAVE_STATIC_PERL_TRUE=''
> INSTALL_DATA='${INSTALL} -m 644'
> INSTALL_PROGRAM='${INSTALL}'
> INSTALL_SCRIPT='${INSTALL}'
> LDFLAGS=''
> LIBOBJS=''
> LIBPERL_A=''
> LIBS=''
> LIBTOOL=''
> LN_S=''
> LTLIBOBJS=''
> MAINT='#'
> MAINTAINER_MODE_FALSE=''
> MAINTAINER_MODE_TRUE='#'
> MAKEINFO='makeinfo'
> NEED_TPARM_FALSE=''
> NEED_TPARM_TRUE=''
> OBJEXT=''
> PACKAGE='irssi'
> PACKAGE_BUGREPORT=''
> PACKAGE_NAME=''
> PACKAGE_STRING=''
> PACKAGE_TARNAME=''
> PACKAGE_VERSION=''
> PATH_SEPARATOR=':'
> PERL_CFLAGS=''
> PERL_EXTRA_OPTS=''
> PERL_FE_LINK_LIBS=''
> PERL_LDFLAGS=''
> PERL_LIBTOOL=''
> PERL_LINK_FLAGS=''
> PERL_LINK_LIBS=''
> PERL_MM_PARAMS=''
> PERL_STATIC_LIBS=''
> PERL_USE_LIB=''
> PKG_CONFIG=''
> PROG_LIBS=''
> RANLIB=''
> SET_MAKE=''
> SHELL='/bin/sh'
> SSL_CFLAGS=''
> SSL_LIBS=''
> STRIP=''
> TEXTUI_LIBS=''
> USE_CURSES_FALSE=''
> USE_CURSES_TRUE=''
> VERSION='0.8.10-rc5'
> VERSION_DATE=''
> VERSION_TIME=''
> ac_ct_AR=''
> ac_ct_CC=''
> ac_ct_CXX=''
> ac_ct_F77=''
> ac_ct_RANLIB=''
> ac_ct_STRIP=''
> bindir='${exec_prefix}/bin'
> build=''
> build_alias=''
> build_cpu=''
> build_os=''
> build_vendor=''
> datadir='/usr/share'
> exec_prefix='NONE'
> host='x86_64-pc-linux-gnu'
> host_alias='x86_64-pc-linux-gnu'
> host_cpu=''
> host_os=''
> host_vendor=''
> includedir='${prefix}/include'
> infodir='/usr/share/info'
> irc_MODULES=''
> libdir='/usr/lib64'
> libexecdir='${exec_prefix}/libexec'
> localstatedir='/var/lib'
> mandir='/usr/share/man'
> oldincludedir='/usr/include'
> perl_module_fe_lib=''
> perl_module_lib=''
> perl_static_fe_lib=''
> perl_static_lib=''
> perlpath=''
> prefix='/usr'
> program_transform_name='s,x,x,'
> sbindir='${exec_prefix}/sbin'
> sedpath=''
> sharedstatedir='${prefix}/com'
> sysconfdir='/etc'
> target_alias=''
>
> ## ----------- ##
> ## confdefs.h. ##
> ## ----------- ##
>
> #define PACKAGE "irssi"
> #define PACKAGE_BUGREPORT ""
> #define PACKAGE_NAME ""
> #define PACKAGE_STRING ""
> #define PACKAGE_TARNAME ""
> #define PACKAGE_VERSION ""
> #define VERSION "0.8.10-rc5"
>
> configure: exit 77
> --
> gentoo-user@gentoo.org mailing list
>
>
--
Ivan Yosifov.

--
gentoo-user@gentoo.org mailing list

Re: C compiler cannot create executables [ In reply to ]

security at 303Underground

Mar 31, 2005, 4:07 PM

Post #6 of 15 (589 views)

Permalink

On Thu, 2005-03-31 at 20:09 +0200, spetznaz@internettledelsen.com wrote:
> spetznaz@Mjolne ~ $ gcc-config -l
> [1] x86_64-pc-linux-gnu-3.4.2
> [2] x86_64-pc-linux-gnu-3.4.2-hardened
> [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
> [4] x86_64-pc-linux-gnu-3.4.3-20050110 *
> [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
> [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
> [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
Whenever I get the cannot create executables message, it is usually
related to the following two files, which if they exist should be
deleted as they are messing with (due to being applied after) the proper
ones that do not end with a hyphen:
/etc/env.d/05gcc-
/etc/env.d/gcc/config-
Delete those two, run env-update and source /etc/profile, then try the
emerge again. Something else that happens to me around the same time is
a complaint about a lib(something).la which cannot be found because its
looking for it in a path without the datestamp. Adding the two symlinks
below helped me with that:

Green# ll /usr/lib/gcc/i686-pc-linux-gnu/
lrwxrwxrwx 1 root root 14 Feb 21 14:03 3.3.5 -> 3.3.5-20050130
drwxr-xr-x 4 root root 4096 Mar 30 00:44 3.3.5-20050130
lrwxrwxrwx 1 root root 14 Feb 21 14:02 3.4.3 -> 3.4.3-20050110
drwxr-xr-x 4 root root 4096 Mar 31 09:14 3.4.3-20050110

--
Scott Taylor - <security@303underground.com>

BOFH Excuse #216:

What office are you in? Oh, that one. Did you know that your building
was built over the universities first nuclear research site? And wow,
aren't you the lucky one, your office is right over where the core is
buried!

--
gentoo-user@gentoo.org mailing list

Re: C compiler cannot create executables [ In reply to ]

thompson.eric at gmail

Mar 31, 2005, 4:51 PM

Post #7 of 15 (590 views)

Permalink

On Thu, 31 Mar 2005 16:07:10 -0700, Scott Taylor
<security@303underground.com> wrote:
> On Thu, 2005-03-31 at 20:09 +0200, spetznaz@internettledelsen.com wrote:
> > spetznaz@Mjolne ~ $ gcc-config -l
> > [1] x86_64-pc-linux-gnu-3.4.2
> > [2] x86_64-pc-linux-gnu-3.4.2-hardened
> > [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
> > [4] x86_64-pc-linux-gnu-3.4.3-20050110 *
> > [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
> > [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
> > [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
> Whenever I get the cannot create executables message, it is usually
> related to the following two files, which if they exist should be
> deleted as they are messing with (due to being applied after) the proper
> ones that do not end with a hyphen:
> /etc/env.d/05gcc-
> /etc/env.d/gcc/config-
> Delete those two, run env-update and source /etc/profile, then try the
> emerge again. Something else that happens to me around the same time is
> a complaint about a lib(something).la which cannot be found because its
> looking for it in a path without the datestamp. Adding the two symlinks
> below helped me with that:
>
> Green# ll /usr/lib/gcc/i686-pc-linux-gnu/
> lrwxrwxrwx 1 root root 14 Feb 21 14:03 3.3.5 -> 3.3.5-20050130
> drwxr-xr-x 4 root root 4096 Mar 30 00:44 3.3.5-20050130
> lrwxrwxrwx 1 root root 14 Feb 21 14:02 3.4.3 -> 3.4.3-20050110
> drwxr-xr-x 4 root root 4096 Mar 31 09:14 3.4.3-20050110
>
> --
> Scott Taylor - <security@303underground.com>
>
> BOFH Excuse #216:
>
> What office are you in? Oh, that one. Did you know that your building
> was built over the universities first nuclear research site? And wow,
> aren't you the lucky one, your office is right over where the core is
> buried!
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>

Every time I get the cannot create executables error, it has been a
bad binutils. I noticed in you emerge info that you are using
binutils-2.15.92.0.2-r7 and every version above -r2 has been bad for
me, so I just masked the versions above -r4, and used -r2. There are
binary packages at http://dev.gentoo.org/~avenj/bins/ if you need them
to get your system back up and running.

Hope this helps

--
Eric Thompson
thompson.eric@gmail.com
--
gentoo-user@gentoo.org mailing list

Re: C compiler cannot create executables [ In reply to ]

ostroffjh at users

Sep 10, 2022, 8:41 AM

Post #8 of 15 (249 views)

Permalink

Re: C compiler cannot create executables [ In reply to ]

arve.barsnes at gmail

Sep 10, 2022, 8:42 AM

Post #9 of 15 (249 views)

Permalink

On Sat, 10 Sept 2022 at 17:28, Jack <ostroffjh@users.sourceforge.net> wrote:
> Any thoughts or suggestions?

I feel like this is an error that tends to pop up when your toolchain
is broken. Are you able to re-emerge gcc?

Regards,
Arve

Re: C compiler cannot create executables [ In reply to ]

ostroffjh at users

Sep 10, 2022, 10:27 AM

Post #10 of 15 (248 views)

Permalink

On 9/10/22 11:42, Arve Barsnes wrote:
> On Sat, 10 Sept 2022 at 17:28, Jack<ostroffjh@users.sourceforge.net> wrote:
>> Any thoughts or suggestions?
> I feel like this is an error that tends to pop up when your toolchain
> is broken. Are you able to re-emerge gcc?

gcc11.3.0 re-emerge with no errors, bug the problem remains.

I note that in configure, line 2977 is 'ac_files="a.out conftest.exe
conftest a.exe a_out.exe b.out conftest.*"' but the test compilation
creates the output file "g" so configure seems to think that the compile
didn't produce any executable. Using the same compile line but
switching x86_64-pc-linux-gnu-gcc to gcc produces a.out. Further
searching makes me wonder if the configure itself for these two packages
is just based on some starting point too old for gcc11, but that line
is the same in every package I currently still have present in
/var/tmp/portage.

This leaves me wondering why gcc and x86_64-pc-linux-gnu-gcc use
different default output file names.

Re: C compiler cannot create executables [ In reply to ]

gentoo at dhaller

Sep 10, 2022, 10:56 AM

Post #11 of 15 (248 views)

Permalink

Hello,

On Sat, 10 Sep 2022, Jack wrote:
>I now get this error trying to emerge two different packages: libofx-0.10.7
>and gnupg (both 2.2.39 and 2.3.6).? It might also be the same problem for a
>few bugs on b.g.o found by searching on "cannot create exectuables."
>
>The relevant lines from build.log are
>
>checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
>checking whether the C compiler works... no
>configure: error: in
>`/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>configure: error: C compiler cannot create executables
>See `config.log' for more details
>
>and from config.log:
>
>configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
>x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
>x86_64-pc-linux-gnu-gcc: fatal error: no input files
>compilation terminated.
>configure:2952: $? = 1
>configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
>x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-qversion';
>did you mean '--version'?
>x86_64-pc-linux-gnu-gcc: fatal error: no input files
>compilation terminated.
>configure:2952: $? = 1

These tests are normal fails with gcc, they are version checks for
other compilers.

>configure:2972: checking whether the C compiler works
>configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og -ggdb?
>-Wl,-O1 -Wl,--as-needed conftest.c? >&5
>configure:2998: $? = 0
>configure:3036: result: no
>configure: failed program was:
[..boilerplate..]
>configure:3041: error: in
>`/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>configure:3043: error: C compiler cannot create executables
>See `config.log' for more details
>
>The thing I find curious is that it appears to me that the output of the test
>compile is a file called "g" which I don't recall ever seeing, and so I
>wonder if the problem is that something has changed with gcc defaults and
>configure does not yet recognize that change.? I also don't know the?
>significance of the two "fatal error: no input files".
>
>The fact that this happens with two unrelated packages suggests that it's?
>not specific to either of them, but something in my system or configuration.

And it's a standard autoconf macro, namely AC_PROG_CC that results in
the error and the stuff before that is also standard. And as no
autoreconf is called, autotools versions should not matter.

>Any thoughts or suggestions?

I use gcc 11.3.0 here as well, and have no problem. Check for the
variables CC, CFLAGS, CPPFLAGS, LDFLAGS and LIBS in
/var/tmp/portage/dev-libs/libofx-0.10.7/temp/environment.

Somehow, that '-og' must have crept in there.

HTH,
-dnh

--
printk("%s: Boo!\n", dev->name);
linux-2.6.19/drivers/net/depca.c

Re: C compiler cannot create executables [ In reply to ]

ostroffjh at users

Sep 10, 2022, 11:47 AM

Post #12 of 15 (248 views)

Permalink

On 9/10/22 14:49, Dale wrote:
> Jack wrote:
>> I now get this error trying to emerge two different packages:
>> libofx-0.10.7 and gnupg (both 2.2.39 and 2.3.6). It might also be the
>> same problem for a few bugs on b.g.o found by searching on "cannot
>> create exectuables."
>>
>> The relevant lines from build.log are
>>
>> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
>> checking whether the C compiler works... no
>> configure: error: in
>> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details
>>
>> and from config.log:
>>
>> Thread model: posix
>> Supported LTO compression algorithms: zlib
>> gcc version 11.3.0 (Gentoo 11.3.0 p4)
>> configure:2952: $? = 0
>> configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
>> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
>> x86_64-pc-linux-gnu-gcc: fatal error: no input files
>> compilation terminated.
>> configure:2952: $? = 1
>> configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
>> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option
>> '-qversion'; did you mean '--version'?
>> x86_64-pc-linux-gnu-gcc: fatal error: no input files
>> compilation terminated.
>> configure:2952: $? = 1
>> configure:2972: checking whether the C compiler works
>> configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og
>> -ggdb -Wl,-O1 -Wl,--as-needed conftest.c >&5
>> configure:2998: $? = 0
>> configure:3036: result: no
>> configure: failed program was:
>> | /* confdefs.h */
>> | #define PACKAGE_NAME "libofx"
>> | #define PACKAGE_TARNAME "libofx"
>> | #define PACKAGE_VERSION "0.10.7"
>> | #define PACKAGE_STRING "libofx 0.10.7"
>> | #define PACKAGE_BUGREPORT ""
>> | #define PACKAGE_URL ""
>> | /* end confdefs.h. */
>> |
>> | int
>> | main ()
>> | {
>> |
>> | ;
>> | return 0;
>> | }
>> configure:3041: error: in
>> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>> configure:3043: error: C compiler cannot create executables
>> See `config.log' for more details
>>
>> The thing I find curious is that it appears to me that the output of
>> the test compile is a file called "g" which I don't recall ever
>> seeing, and so I wonder if the problem is that something has changed
>> with gcc defaults and configure does not yet recognize that change. I
>> also don't know the significance of the two "fatal error: no input
>> files".
>>
>> The fact that this happens with two unrelated packages suggests that
>> it's not specific to either of them, but something in my system or
>> configuration.
>>
>> Any thoughts or suggestions?
>>
>> Jack
>>
>>
>>
>
> I ran into this ages ago. I think the fix was to reset which compiler
> it is set to use. I used to keep two installed, in case one would fail
> or some package couldn't build with a newer version yet. If I recall
> correctly, I would list the available options with gcc-config -l and
> then if two are available, set to older one and then change back or if
> only one is installed, just set it to the one you have. It's been a
> good while and it could be that the cause of the problem has changed but
> I don't think it will hurt anything to try this. I think some settings
> gets messed up and resetting it fixes it.
>
> Hope that helps. If not, clueless. :/

Thanks Dale, but I only have one version of gcc installed and both
gcc-config and binutils-config show only one option.

I do believe that David Haller pegged the problem, and I'll respond to
his post after confirming.

Jack

Re: C compiler cannot create executables [ In reply to ]

rdalek1967 at gmail

Sep 10, 2022, 11:49 AM

Post #13 of 15 (248 views)

Permalink

Jack wrote:
> I now get this error trying to emerge two different packages:
> libofx-0.10.7 and gnupg (both 2.2.39 and 2.3.6). It might also be the
> same problem for a few bugs on b.g.o found by searching on "cannot
> create exectuables."
>
> The relevant lines from build.log are
>
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking whether the C compiler works... no
> configure: error: in
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
>
> and from config.log:
>
> Thread model: posix
> Supported LTO compression algorithms: zlib
> gcc version 11.3.0 (Gentoo 11.3.0 p4)
> configure:2952: $? = 0
> configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:2952: $? = 1
> configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option
> '-qversion'; did you mean '--version'?
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:2952: $? = 1
> configure:2972: checking whether the C compiler works
> configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og
> -ggdb -Wl,-O1 -Wl,--as-needed conftest.c >&5
> configure:2998: $? = 0
> configure:3036: result: no
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "libofx"
> | #define PACKAGE_TARNAME "libofx"
> | #define PACKAGE_VERSION "0.10.7"
> | #define PACKAGE_STRING "libofx 0.10.7"
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:3041: error: in
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> configure:3043: error: C compiler cannot create executables
> See `config.log' for more details
>
> The thing I find curious is that it appears to me that the output of
> the test compile is a file called "g" which I don't recall ever
> seeing, and so I wonder if the problem is that something has changed
> with gcc defaults and configure does not yet recognize that change. I
> also don't know the significance of the two "fatal error: no input
> files".
>
> The fact that this happens with two unrelated packages suggests that
> it's not specific to either of them, but something in my system or
> configuration.
>
> Any thoughts or suggestions?
>
> Jack
>
>
>

I ran into this ages ago. I think the fix was to reset which compiler
it is set to use. I used to keep two installed, in case one would fail
or some package couldn't build with a newer version yet. If I recall
correctly, I would list the available options with gcc-config -l and
then if two are available, set to older one and then change back or if
only one is installed, just set it to the one you have. It's been a
good while and it could be that the cause of the problem has changed but
I don't think it will hurt anything to try this. I think some settings
gets messed up and resetting it fixes it.

Hope that helps. If not, clueless. :/

Dale

:-) :-)

Re: C compiler cannot create executables [ In reply to ]

rdalek1967 at gmail

Sep 10, 2022, 11:55 AM

Post #14 of 15 (248 views)

Permalink

Jack wrote:
> On 9/10/22 14:49, Dale wrote:
>> Jack wrote:
>>> I now get this error trying to emerge two different packages:
>>> libofx-0.10.7 and gnupg (both 2.2.39 and 2.3.6). It might also be the
>>> same problem for a few bugs on b.g.o found by searching on "cannot
>>> create exectuables."
>>>
>>> The relevant lines from build.log are
>>>
>>> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
>>> checking whether the C compiler works... no
>>> configure: error: in
>>> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details
>>>
>>> and from config.log:
>>>
>>> Thread model: posix
>>> Supported LTO compression algorithms: zlib
>>> gcc version 11.3.0 (Gentoo 11.3.0 p4)
>>> configure:2952: $? = 0
>>> configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
>>> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
>>> x86_64-pc-linux-gnu-gcc: fatal error: no input files
>>> compilation terminated.
>>> configure:2952: $? = 1
>>> configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
>>> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option
>>> '-qversion'; did you mean '--version'?
>>> x86_64-pc-linux-gnu-gcc: fatal error: no input files
>>> compilation terminated.
>>> configure:2952: $? = 1
>>> configure:2972: checking whether the C compiler works
>>> configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og
>>> -ggdb -Wl,-O1 -Wl,--as-needed conftest.c >&5
>>> configure:2998: $? = 0
>>> configure:3036: result: no
>>> configure: failed program was:
>>> | /* confdefs.h */
>>> | #define PACKAGE_NAME "libofx"
>>> | #define PACKAGE_TARNAME "libofx"
>>> | #define PACKAGE_VERSION "0.10.7"
>>> | #define PACKAGE_STRING "libofx 0.10.7"
>>> | #define PACKAGE_BUGREPORT ""
>>> | #define PACKAGE_URL ""
>>> | /* end confdefs.h. */
>>> |
>>> | int
>>> | main ()
>>> | {
>>> |
>>> |   ;
>>> |   return 0;
>>> | }
>>> configure:3041: error: in
>>> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
>>> configure:3043: error: C compiler cannot create executables
>>> See `config.log' for more details
>>>
>>> The thing I find curious is that it appears to me that the output of
>>> the test compile is a file called "g" which I don't recall ever
>>> seeing, and so I wonder if the problem is that something has changed
>>> with gcc defaults and configure does not yet recognize that change. I
>>> also don't know the significance of the two "fatal error: no input
>>> files".
>>>
>>> The fact that this happens with two unrelated packages suggests that
>>> it's not specific to either of them, but something in my system or
>>> configuration.
>>>
>>> Any thoughts or suggestions?
>>>
>>> Jack
>>>
>>>
>>>
>>
>> I ran into this ages ago. I think the fix was to reset which compiler
>> it is set to use. I used to keep two installed, in case one would fail
>> or some package couldn't build with a newer version yet. If I recall
>> correctly, I would list the available options with gcc-config -l and
>> then if two are available, set to older one and then change back or if
>> only one is installed, just set it to the one you have. It's been a
>> good while and it could be that the cause of the problem has changed but
>> I don't think it will hurt anything to try this. I think some settings
>> gets messed up and resetting it fixes it.
>>
>> Hope that helps. If not, clueless. :/
>
> Thanks Dale, but I only have one version of gcc installed and both
> gcc-config and binutils-config show only one option.
>
> I do believe that David Haller pegged the problem, and I'll respond to
> his post after confirming.
>
> Jack
>
>
>

If your other option fails, just gcc-config 1 and see if it helps. If
you have only one installed, it still resets when you do it. This is
what it looks like on mine just now.

root@fireball / # gcc-config -l
[1] x86_64-pc-linux-gnu-11.3.0 *
root@fireball / # gcc-config 1
* Switching native-compiler to x86_64-pc-linux-gnu-11.3.0 ...
* Backing up '//usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/libgcc_s.so.1'
to '/lib64
[ ok ]
root@fireball / #

Just another option. May help, may not. :-D I meant to include before
where I did it but forgot. I remembered this time. lol

Dale

:-) :-)

Re: C compiler cannot create executables [ In reply to ]

ostroffjh at users

Sep 10, 2022, 12:44 PM

Post #15 of 15 (248 views)

Permalink

On 2022.09.10 13:56, David Haller wrote:
> Hello,
>
> On Sat, 10 Sep 2022, Jack wrote:
> >I now get this error trying to emerge two different packages:
> libofx-0.10.7
> >and gnupg (both 2.2.39 and 2.3.6).? It might also be the same
> problem for a
> >few bugs on b.g.o found by searching on "cannot create exectuables."
> >
> >The relevant lines from build.log are
> >
> >checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> >checking whether the C compiler works... no
> >configure: error: in
> >`/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> >configure: error: C compiler cannot create executables
> >See `config.log' for more details
> >
> >and from config.log:
> >
> >configure:2941: x86_64-pc-linux-gnu-gcc -V >&5
> >x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V'
> >x86_64-pc-linux-gnu-gcc: fatal error: no input files
> >compilation terminated.
> >configure:2952: $? = 1
> >configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5
> >x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option
> '-qversion';
> >did you mean '--version'?
> >x86_64-pc-linux-gnu-gcc: fatal error: no input files
> >compilation terminated.
> >configure:2952: $? = 1
>
> These tests are normal fails with gcc, they are version checks for
> other compilers.
>
> >configure:2972: checking whether the C compiler works
> >configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og
> -ggdb?
> >-Wl,-O1 -Wl,--as-needed conftest.c? >&5
> >configure:2998: $? = 0
> >configure:3036: result: no
> >configure: failed program was:
> [..boilerplate..]
> >configure:3041: error: in
> >`/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7':
> >configure:3043: error: C compiler cannot create executables
> >See `config.log' for more details
> >
> >The thing I find curious is that it appears to me that the output of
> the test
> >compile is a file called "g" which I don't recall ever seeing, and
> so I
> >wonder if the problem is that something has changed with gcc
> defaults and
> >configure does not yet recognize that change.? I also don't know the?
> >significance of the two "fatal error: no input files".
> >
> >The fact that this happens with two unrelated packages suggests that
> it's?
> >not specific to either of them, but something in my system or
> configuration.
>
> And it's a standard autoconf macro, namely AC_PROG_CC that results in
> the error and the stuff before that is also standard. And as no
> autoreconf is called, autotools versions should not matter.
>
> >Any thoughts or suggestions?
>
> I use gcc 11.3.0 here as well, and have no problem. Check for the
> variables CC, CFLAGS, CPPFLAGS, LDFLAGS and LIBS in
> /var/tmp/portage/dev-libs/libofx-0.10.7/temp/environment.
>
> Somehow, that '-og' must have crept in there.
David - thank you, thank you, thank you.

No wonder my recent debugging wasn't doing what I expected. That stray
"-og" was supposed to be "-Og" (upper instead of lower case) and it is
in /etc/portage/env/debug.conf, which is referenced in
/etc/portage/package.env for those packages I wish to compile with
various debugging related compiler settings, as well as not deleting
the build dir, even on success.

It shows what a fresh pair of eyes can do. When looking at the various
error related files, I really just saw -Og, and when you pointed that
out, my first thought was why any debugging setting would possible
cause this type of failure. Of course in hindsight, it now all makes
sense.

Thanks again to the list for all sorts of ongoing assistance.

Jack