Package Details: gcc8-libs 8.4.0-2

Git Clone URL: https://aur.archlinux.org/gcc8.git (read-only, click to copy)
Package Base: gcc8
Description: Runtime libraries shipped by GCC (8.x.x)
Upstream URL: http://gcc.gnu.org
Licenses: GPL, custom, LGPL, FDL
Submitter: dvzrv
Maintainer: jonathon
Last Packager: jonathon
Votes: 2
Popularity: 0.198352
First Submitted: 2020-11-23 19:45
Last Updated: 2021-05-13 20:42

Pinned Comments

jonathon commented on 2020-11-30 14:29

Please read the AUR wiki page before reporting issues.

In addition, if you are experiencing a build issue then ensure you have tried building without using an AUR helper (e.g. makepkg) and with a clean chroot (e.g. makechrootpkg).

Latest Comments

1 2 Next › Last »

jonathon commented on 2021-05-13 20:43

OK, I've been trying for a week or so to get the patch that's now included in gcc=11 to make a difference to this package, but the only way that worked for me was to force it via flags in the PKGBUILD.

There's no need to rebuild (no no pkgrel bump), but new builds should work again.

Ergus commented on 2021-05-11 15:32

Hi @pychuang I have a similar problem.

Basically this:

gcc8/src/gcc/libcpp/expr.c: In function ‘unsigned int cpp_classify_number(cpp_reader*, const cpp_token*, const char**, source_location)’:
gcc8/src/gcc/libcpp/expr.c:797:18: error: format not a string literal and no format arguments [-Werror=format-security]
  797 |        0, message);
      |                  ^
gcc8/src/gcc/libcpp/expr.c:800:39: error: format not a string literal and no format arguments [-Werror=format-security]
  800 |           virtual_location, 0, message);

jonathon commented on 2021-05-05 01:02

I'm keeping an eye on FS#70701 to see what the approach will be. Switching CFLAGS seems like a workaround.

jonathon commented on 2021-04-26 19:38

That's a recent addition to makepkg.conf's CFLAGS (https://github.com/archlinux/svntogit-packages/commit/a790c389cb0fd2ddd35e1f581ee337f6891801fc#diff-8da5d04d27b7ace195751c5e1e5e52c0bbd59e1ec3fd89d656496cc1d272d4b0).

The file's lines that error (libcpp/expr.c) haven't changed between GCC8 and GCC11 so this may be an upstream bug...

pychuang commented on 2021-04-26 17:27

Not sure why but I have to remove the compilation flag -Werror=format-security from CFLAGS in order to build these packages. I don't know where the -Werror=format-security comes from. I don't see that flag in makepkg.conf. Anyway, I added the following lines to the build section to make it work:

CFLAGS=${CFLAGS/-Werror=format-security/}
CXXFLAGS=${CXXFLAGS/-Werror=format-security/}

I'm using clean build.

offmilk commented on 2021-02-28 02:05

To avoid using the aur as per jonathon's comment, I attempted to build the package using extra-x86_64-build after cloning the repo. This would however fail installing and when checking the build would say

==> Running checkpkg error: target not found: gcc8 error: target not found: gcc8-libs error: target not found: gcc8-fortran ==> WARNING: Skipped checkpkg due to missing repo packages

to which I just tried using the aur helper yay and was installed successfully.

tinytangent commented on 2021-01-14 12:54

Some of the testcases failed, and counted as "unexpected failures". Like

                === g++ Summary ===

# of expected passes            126511
# of unexpected failures        9
# of expected failures          506
# of unsupported tests          5202

But the packaging procedure still finished. Is that normal?

bred commented on 2020-12-30 12:21

It ends with this compilation error:

(I've compiled with the PKGBUILD without any aur-helper)

libtool: link: ranlib .libs/libtsan.a

libtool: link: rm -fr .libs/libtsan.lax

libtool: link: ( cd ".libs" && rm -f "libtsan.la" && ln -s "../libtsan.la" "libtsan.la" )

make[4]: uscita dalla directory «/tmp/gcccomp/gcc8/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer/tsan»

make[4]: ingresso nella directory «/tmp/gcccomp/gcc8/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer» true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "CXXFLAGS=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE" "CFLAGS_FOR_BUILD=-march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "CFLAGS_FOR_TARGET=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "JC1FLAGS=" "LDFLAGS=" "LIBCFLAGS=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "LIBCFLAGS_FOR_TARGET=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "MAKE=make" "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS=" "exec_prefix=/usr" "infodir=/usr/share/info" "libdir=/usr/lib" "prefix=/usr" "includedir=/usr/include" "AR=ar" "AS=/tmp/gcccomp/gcc8/src/gcc-build/./gcc/as" "LD=/tmp/gcccomp/gcc8/src/gcc-build/./gcc/collect-ld" "LIBCFLAGS=-g -O2 -march=x86-64 -mtune=native -O3 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" "NM=/tmp/gcccomp/gcc8/src/gcc-build/./gcc/nm" "PICFLAG=" "RANLIB=ranlib" "DESTDIR=" DO=all multi-do # make

make[4]: uscita dalla directory «/tmp/gcccomp/gcc8/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer»

make[3]: uscita dalla directory «/tmp/gcccomp/gcc8/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer»

make[2]: uscita dalla directory «/tmp/gcccomp/gcc8/src/gcc-build/x86_64-pc-linux-gnu/libsanitizer»

make[1]: uscita dalla directory «/tmp/gcccomp/gcc8/src/gcc-build»

make: *** x86_64-unknown-linux-gnu/libstdc++-v3/doc: File o directory non esistente. Arresto.

jonathon commented on 2020-11-30 14:29

Please read the AUR wiki page before reporting issues.

In addition, if you are experiencing a build issue then ensure you have tried building without using an AUR helper (e.g. makepkg) and with a clean chroot (e.g. makechrootpkg).

simokron commented on 2020-11-30 09:46

Thanks, Jonathon. Building in a clean chroot was the answer.