Jump to content
Read the Funtoo Newsletter: Summer 2023 ×
  • 0

C compiler is not working.


kris

Question

Hi
For several days now, When upgrading to "next release" and KDE -plasma, I have failed to compile any package. Probably C compiler is not working. It is possible to repair it or reinstall the system.

Emerging (1 of 158) sys-apps/iproute2-5.1.0::core-kit
 * iproute2-5.1.0.tar.xz BLAKE2B SHA512 size ;-) ...                       [ ok ]
>>> Unpacking source...
>>> Unpacking iproute2-5.1.0.tar.xz to /var/tmp/portage/sys-apps/iproute2-5.1.0/work
>>> Source unpacked in /var/tmp/portage/sys-apps/iproute2-5.1.0/work
>>> Preparing source in /var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0 ...
 * Applying iproute2-3.1.0-mtu.patch ...
patching file tc/tc_core.c
Hunk #1 succeeded at 173 (offset 18 lines).
patching file tc/tc_stab.c
Hunk #1 succeeded at 32 with fuzz 2.                                       [ ok ]
 * Applying iproute2-4.20.0-configure-nomagic.patch ...
patching file bridge/Makefile
patching file config.include
patching file configure
patching file devlink/Makefile
patching file genl/Makefile
patching file ip/Makefile
patching file lib/Makefile
patching file misc/Makefile
patching file netem/Makefile
patching file rdma/Makefile
Hunk #1 succeeded at 1 with fuzz 2.
patching file tc/Makefile
patching file tipc/Makefile                                                [ ok ]
 * Applying iproute2-5.1.0-portability.patch ...                           [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0 ...
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --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
TC schedulers
 ATM    no
 IPT    using iptables
 IPSET  no

iptables modules directory: /usr/lib64/xtables
libc has setns: no
SELinux support: no
ELF support: yes
libmnl support: yes
Berkeley DB: no
need for strlcpy: no
libcap support: yes
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0 ...
make -j4 V=1 

lib
make[1]: warning: -jN forced in submake: disabling jobserver mode.
make[1]: Entering directory '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0/lib'
x86_64-pc-linux-gnu-gcc -Wall -Wstrict-prototypes  -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wformat=2 -mtune=generic -O2 -pipe  -I../include -I../include/uapi -DRESOLVE_HOSTNAMES -DLIBDIR=\"/lib64\" -DCONFDIR=\"/etc/iproute2\" -DNETNS_RUN_DIR=\"/var/run/netns\" -DNETNS_ETC_DIR=\"/etc/netns\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mtune=generic -O2 -pipe -DHAVE_LIBBSD -DHAVE_LIBMNL -fPIC   -c -o libgenl.o libgenl.c
x86_64-pc-linux-gnu-gcc -Wall -Wstrict-prototypes  -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wformat=2 -mtune=generic -O2 -pipe  -I../include -I../include/uapi -DRESOLVE_HOSTNAMES -DLIBDIR=\"/lib64\" -DCONFDIR=\"/etc/iproute2\" -DNETNS_RUN_DIR=\"/var/run/netns\" -DNETNS_ETC_DIR=\"/etc/netns\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mtune=generic -O2 -pipe -DHAVE_LIBBSD -DHAVE_LIBMNL -fPIC   -c -o libnetlink.o libnetlink.c
x86_64-pc-linux-gnu-gcc -Wall -Wstrict-prototypes  -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wformat=2 -mtune=generic -O2 -pipe  -I../include -I../include/uapi -DRESOLVE_HOSTNAMES -DLIBDIR=\"/lib64\" -DCONFDIR=\"/etc/iproute2\" -DNETNS_RUN_DIR=\"/var/run/netns\" -DNETNS_ETC_DIR=\"/etc/netns\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mtune=generic -O2 -pipe -DHAVE_LIBBSD -DHAVE_LIBMNL -fPIC   -c -o utils.o utils.c
x86_64-pc-linux-gnu-gcc -Wall -Wstrict-prototypes  -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wformat=2 -mtune=generic -O2 -pipe  -I../include -I../include/uapi -DRESOLVE_HOSTNAMES -DLIBDIR=\"/lib64\" -DCONFDIR=\"/etc/iproute2\" -DNETNS_RUN_DIR=\"/var/run/netns\" -DNETNS_ETC_DIR=\"/etc/netns\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mtune=generic -O2 -pipe -DHAVE_LIBBSD -DHAVE_LIBMNL -fPIC   -c -o rt_names.o rt_names.c
x86_64-pc-linux-gnu-gcc: fatal error: cannot execute ‘as’: execvp: No such file or directory
compilation terminated.
make[1]: *** [../config.include:24: libgenl.o] Error 1
make[1]: *** Waiting for unfinished jobs....
x86_64-pc-linux-gnu-gcc: fatal error: cannot execute ‘as’: execvp: No such file or directory
compilation terminated.
make[1]: *** [../config.include:24: utils.o] Error 1
x86_64-pc-linux-gnu-gcc: fatal error: cannot execute ‘as’: execvp: No such file or directory
compilation terminated.
make[1]: *** [../config.include:24: libnetlink.o] Error 1
x86_64-pc-linux-gnu-gcc: fatal error: cannot execute ‘as’: execvp: No such file or directory
compilation terminated.
make[1]: *** [../config.include:24: rt_names.o] Error 1
make[1]: Leaving directory '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0/lib'
make: *** [Makefile:63: all] Error 2
In file included from utils.c:41:
../include/namespace.h:41:19: error: static declaration of ‘setns’ follows non-static declaration
   41 | static inline int setns(int fd, int nstype)
      |                   ^~~~~
In file included from /usr/include/sched.h:43,
                 from ../include/namespace.h:5,
                 from utils.c:41:
/usr/include/bits/sched.h:95:12: note: previous declaration of ‘setns’ was here
   95 | extern int setns (int __fd, int __nstype) __THROW;
      |            ^~~~~
 * ERROR: sys-apps/iproute2-5.1.0::core-kit failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/iproute2-5.1.0::core-kit'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/iproute2-5.1.0::core-kit'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/iproute2-5.1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/iproute2-5.1.0/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0'
 * S: '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0'

>>> Failed to emerge sys-apps/iproute2-5.1.0, Log file:

>>>  '/var/tmp/portage/sys-apps/iproute2-5.1.0/temp/build.log'

 * Messages for package sys-apps/iproute2-5.1.0:

 * ERROR: sys-apps/iproute2-5.1.0::core-kit failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-apps/iproute2-5.1.0::core-kit'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/iproute2-5.1.0::core-kit'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/iproute2-5.1.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/iproute2-5.1.0/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0'
 * S: '/var/tmp/portage/sys-apps/iproute2-5.1.0/work/iproute2-5.1.0'

https://dpaste.com/BYGMBC36U

Compilation of every package ends with the same error

Link to comment
Share on other sites

1 answer to this question

Recommended Posts

  • 0
Quote

x86_64-pc-linux-gnu-gcc: fatal error: cannot execute ‘as’: execvp: No such file or directory compilation terminated.

From @drobbins 'next' release announcement:

PLEASE NOTE: When you do this, unless you have a very very minimal system, I can almost guarantee that doing an emptytree rebuild WILL result in some packages not building. So be prepared for this and don't do this on production systems of course! Feel free to open bugs for any build failures, particularly for any DE or server packages that need gcc10 fixes.

ALSO PLEASE NOTE: We reserve the right to break or make disruptive changes in next-release AT ANY TIME! While I am going to try to do things as cleanly as possible, and ensure that the stage3 continues to build, you should be prepared for potential dep issues and other problems that may be annoying to deal with. This is part of the whole process of updating Funtoo that you are embarking upon!

'next' release currently includes gcc-11.2.0 and an updated unified binutils (binutils and binutils-libs have been combined, and binutils-config has been removed.) It also has a small handful of updated packages.

# ln -sf /usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/as /usr/bin

There are 18 binutils, everyone may require a symlink to /usr/bin:

/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/addr2line
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/ar
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/as
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/c++filt
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/dwp
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/elfedit
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/gprof
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/ld
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/ld.bfd
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/ld.gold
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/nm
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/objcopy
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/objdump
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/ranlib
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/readelf
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/size
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/strings
/usr/x86_64-pc-linux-gnu/binutils-bin/2.36.1/strip

If the binutils are missing download the "next" stage 3 tarball and extract them.

 

 

Edited by cardinal
New info.
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...