@EndruK: you are right. <sys/ustat.h>
was removed in glibc 2.28. I'm looking for a fix.
@TheEbolaDoc: you are experiencing the same issue.
Git Clone URL: | https://aur.archlinux.org/gcc6.git (read-only, click to copy) |
---|---|
Package Base: | gcc6 |
Description: | The GNU Compiler Collection - C and C++ frontends (6.x.x) |
Upstream URL: | https://gcc.gnu.org/gcc-6/ |
Licenses: | GPL, custom, LGPL, FDL |
Submitter: | svenstaro |
Maintainer: | valandil |
Last Packager: | valandil |
Votes: | 20 |
Popularity: | 0.000150 |
First Submitted: | 2018-05-17 20:56 (UTC) |
Last Updated: | 2023-06-03 19:08 (UTC) |
@EndruK: you are right. <sys/ustat.h>
was removed in glibc 2.28. I'm looking for a fix.
@TheEbolaDoc: you are experiencing the same issue.
The build fails for me:
/home/andre/.cache/pikaur/build/gcc6/src/gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:153:23: fatal error: sys/ustat.h: No such file or directory
#include <sys/ustat.h>
^
compilation terminated.
make[4]: *** [Makefile:477: sanitizer_platform_limits_posix.lo] Error 1
make[4]: Leaving directory '/home/andre/.cache/pikaur/build/gcc6/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common'
make[3]: *** [Makefile:466: all-recursive] Error 1
make[3]: Leaving directory '/home/andre/.cache/pikaur/build/gcc6/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer'
make[2]: *** [Makefile:336: all] Error 2
make[2]: Leaving directory '/home/andre/.cache/pikaur/build/gcc6/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer'
make[1]: *** [Makefile:14292: all-target-libsanitizer] Error 2
make[1]: Leaving directory '/home/andre/.cache/pikaur/build/gcc6/src/gcc-build'
make: *** [Makefile:917: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I cannot find ustat.h in my filesystem. Does this come with another dependency?
Hey guys! The build fails for me (due to unknown reasons):
libtool: link: ranlib .libs/libquadmath.a
libtool: link: ( cd ".libs" && rm -f "libquadmath.la" && ln -s "../libquadmath.la" "libquadmath.la" )
make[3]: Leaving directory '/home/chris/.cache/yay/gcc6/src/gcc-build/x86_64-pc-linux-gnu/libquadmath'
make[2]: Leaving directory '/home/chris/.cache/yay/gcc6/src/gcc-build/x86_64-pc-linux-gnu/libquadmath'
make[1]: Leaving directory '/home/chris/.cache/yay/gcc6/src/gcc-build'
make: *** [Makefile:917: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Error making: gcc6-libs
The source in the PKGBUILD http://isl.gforge.inria.fr/isl-${_islver}.tar.bz2 is down
there is a mirror at https://mirror.sobukus.de/files/src/isl/isl-${_islver}.tar.bz2
@snarfies that's a pacman bug: https://bugs.archlinux.org/task/58820
Trying to install this via pacaur yields the following:
:: Building gcc6,gcc6-libs package(s)...
==> Making package: gcc6 6.4.1-7 (Fri 27 Jul 2018 02:27:32 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
/usr/bin/pacman: unrecognized option '--color never'
==> ERROR: 'pacman' failed to install missing dependencies.
:: failed to build gcc6,gcc6-libs package(s)
@ector jdk is needed for gcc6-gcj (a Java compiler). I might split it into a separate package so we can skip the dependencies and speed up the build.
@momoe @marty @anoki: yes, 8 GB is about the space you will need. If your tmpfs is not that big, don't build it there. Try to use plain makepkg
to build the package if your AUR helper uses /tmp
.
You can improve compile times by using all of your CPU cores. For example, for a quad-core CPU, set MAKEFLAGS="-j4"
in /etc/makepkg.conf
. The build takes less than an hour on my 2013 quad-core CPU.
@momoe:@marty I have the same problem, except I'm using manjaro. I tried several times, and each time the build fails because "No space left on device".
Pinned Comments
valandil commented on 2020-08-24 15:06 (UTC)
I highly recommend building this package in a clean chroot. This avoids the use of a AUR helper, which sometimes uses
/tmp
as the stating directory, which often gets filled completely by gcc's build process.It also provides a clean environment, which minimizes interactions between your current environment and gcc's build process.