Does this package include gcc 6.3.x? I have installed this but it shows 6.5 and MATLAB, unfortunately, does not accept this version. Yet, I am unable to find 6.3.x. Does anyone know how I can install 6.3.x?
Search Criteria
Package Base Details: gcc6
Package Actions
Git Clone URL: | https://aur.archlinux.org/gcc6.git (read-only, click to copy) |
---|---|
Submitter: | svenstaro |
Maintainer: | valandil |
Last Packager: | valandil |
Votes: | 20 |
Popularity: | 0.011936 |
First Submitted: | 2018-05-17 20:56 (UTC) |
Last Updated: | 2023-06-03 19:08 (UTC) |
Packages (4)
ElektrikAkar commented on 2018-11-05 13:21 (UTC) (edited on 2018-11-05 13:22 (UTC) by ElektrikAkar)
sknd commented on 2018-10-29 21:40 (UTC)
sokuban you can use pacman -U with --overwrite option
sokuban commented on 2018-08-30 08:43 (UTC) (edited on 2018-08-30 08:51 (UTC) by sokuban)
I could build fine (I needed at least 8GiB though), but I can't install the resulting packages. I looked at the conflicting files, and most of them seem to be the same size, but the size of the two libstdc++.a are different.
Any advice?
[code]$ sudo pacman -U gcc6-6.4.1-8-x86_64.pkg.tar.xz gcc6-fortran-6.4.1-8-x86_64.pkg.tar.xz gcc6-gcj-6.4.1-8-x86_64.pkg.tar.xz gcc6-libs-6.4.1-8-x86_64.pkg.tar.xz loading packages... resolving dependencies... looking for conflicting packages...
Packages (4) gcc6-6.4.1-8 gcc6-fortran-6.4.1-8 gcc6-gcj-6.4.1-8 gcc6-libs-6.4.1-8
Total Installed Size: 453.89 MiB Net Upgrade Size: 133.96 MiB
:: Proceed with installation? [Y/n] y (4/4) checking keys in keyring [######################] 100% (4/4) checking package integrity [######################] 100% (4/4) loading package files [######################] 100% (4/4) checking for file conflicts [######################] 100% error: failed to commit transaction (conflicting files) /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libstdc++.a exists in both 'gcc6-libs' and 'gcc6' /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libstdc++.la exists in both 'gcc6-libs' and 'gcc6' /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libgcj-tools.la exists in both 'gcc6-libs' and 'gcc6-gcj' /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libgcj.la exists in both 'gcc6-libs' and 'gcc6-gcj' /usr/lib/gcc/x86_64-unknown-linux-gnu/6.4.1/libgij.la exists in both 'gcc6-libs' and 'gcc6-gcj' Errors occurred, no packages were upgraded.[/code]
wjmelements commented on 2018-08-30 08:38 (UTC)
Unfortunately (or fortunately) I can no longer reproduce the build failure.
raul commented on 2018-08-28 17:28 (UTC)
just built it, 7.6G required disk space (ext4) in total
lonaowna commented on 2018-08-28 07:52 (UTC)
@wjmelements can you post your entire build log?
wjmelements commented on 2018-08-27 23:44 (UTC)
When I try to build, I always get a link-time error when linking cc1. Unfortunately there isn't a descriptive error message.
g++ -std=gnu++98 -no-pie . -g -DIN_GCC . -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing .......... -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -o cc1 c/c-lang.o c-family/stub-objc.o attribs.o .................... -lisl -lmpc -lmpfr -lgmp -rdynamic -ldl -lz
collect2: error: ld returned 1 exit status
I am also seeing warnings about not compiling with optimization
# . warning _FORTIFY_SOURCE requires compiling with optimization (-O)
When I built without yaourt, I don't get the optimization warnings but it got into an infinite loop that lasted until my disk filled up several hours later.
EndruK commented on 2018-08-09 10:28 (UTC)
With application of the patch from here I was also able to compile it.
Best regards, EndruK
lonaowna commented on 2018-08-09 09:23 (UTC) (edited on 2018-08-09 09:24 (UTC) by lonaowna)
@EndruK @TheEbolaDoc the glibc 2.28 build issues should be fixed in 6.4.1-8. Let me know if you still experience problems.
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.