Package Base Details: gcc-git

Git Clone URL: https://aur.archlinux.org/gcc-git.git (read-only, click to copy)
Submitter: Allan
Maintainer: IslandC0der (ptr1337)
Last Packager: ptr1337
Votes: 15
Popularity: 0.000044
First Submitted: 2013-06-26 03:43 (UTC)
Last Updated: 2024-03-21 19:26 (UTC)

Pinned Comments

DAC324 commented on 2021-09-17 08:04 (UTC)

In addition to the jamespharvey20's sticky comment: The current GCC 12 versions are labelled "Experimental" for a reason. Development is ongoing, and there are still significant bugs. Hence, it is not recommended to use GCC 12 as a daily driver or on production systems.

At the moment, it is not even possible to build a working Linux kernel with GCC 12, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101941 .

jamespharvey20 commented on 2017-02-15 04:30 (UTC) (edited on 2017-02-15 11:01 (UTC) by jamespharvey20)

*** STICKY *** These gcc*-git packages replace core's gcc* (non-git) packages. Technically, replacing the system gcc-libs can be dangerous. The possibility of a new upstream gcc git commit breaking your system isn't zero. When you compile and install this, you're using the latest git source, so you may be the first Arch user to be using that particular commit. In practice, I haven't seen an Arch user report such a problem for many years. Just understand that if installing these packages causes your computer to eat you, don't have your loved ones blame me. Oh, and know that if things go wrong, all you *should* have to do is uninstall the git version and go back to a previously working git version or even the core version. You might be able to do this while your system is still running, or you might have to do something like boot off an Arch ISO CD.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 Next › Last »

jamespharvey20 commented on 2017-02-08 11:13 (UTC)

I'm tied up for a few hours, but later today I have a lot of time to give this. Thanks for letting me know.

sleeping commented on 2017-02-08 09:47 (UTC) (edited on 2017-02-08 09:48 (UTC) by sleeping)

install: failed to access '/home/me/tmp/yaourt-tmp-bart/aur-gcc-git/pkg/gcc-git/usr/lib/gcc/x86_64-pc-linux-gnu/6.0.0/': No such file or directory ==> ERROR: A failure occurred in package_gcc-git(). Aborting... ==> ERROR: Makepkg was unable to build gcc-git. The problem now seems to be the hard-coded pkgver.

TaylerNest commented on 2017-01-25 17:31 (UTC)

Cannot install, tried on 3 machines http://pastebin.com/vLsm4Tfg

janisozaur commented on 2016-02-25 11:05 (UTC) (edited on 2016-02-25 11:07 (UTC) by janisozaur)

It seems ISL 0.16.1 is available now and https://gcc.gnu.org/install/prerequisites.html mentions it as a compatible, can you check & update the PKGBUILD? See https://groups.google.com/forum/#!topic/isl-announce/i8PTGG0ZbzE for announcment

jamespharvey20 commented on 2015-12-13 21:00 (UTC)

So, it might be easy enough to patch config.guess:1041, if we wanted to deviate from upstream if they won't revert it. If you'd like, I can see if that works.

jamespharvey20 commented on 2015-12-13 20:52 (UTC)

Think this is where it came from: https://lists.gnu.org/archive/html/config-patches/2015-06/msg00017.html ^^^ "This is a minimally invasive change" http://git.savannah.gnu.org/cgit/config.git/commit/?id=ca9bfb8cc75a2be1819d89c664a867785c96c9ba Then brought downstream into GCC: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=c14bac81551d6769741c2b1cc55e04d94fe8d3a7

Allan commented on 2015-12-13 10:48 (UTC)

Thanks - I'll look into why this has changed. Changing the CHOST like that is a bad idea (TM), so I'll figure out why this has occurred.

jamespharvey20 commented on 2015-12-13 10:45 (UTC) (edited on 2015-12-13 10:46 (UTC) by jamespharvey20)

Sure. The first instance I ran into it was at PKGBUILD::build(), at "make -C $CHOST/libstdc++-v3/doc doc-man-doxygen". It failed, expecting there to be a "${srcdir}/gcc-build/x86_64-unknown-linux-gnu/libstdc++-v3/doc" directory. But, instead, "${srcdir}/gcc-build/" has: build-x86_64-pc-linux-gnu/ prev-x86_64-pc-linux-gnu/ stage1-x86_64-pc-linux-gnu/ x86_64-pc-linux-gnu/ So, it doesn't actually detect CHOST using "unknown" and give an error. It makes the directories (at least on my system) with "pc" rather than "unknown", so every instance PKGBUILD uses $CHOST points to a non-existant directory. Off to bed. 6am here.

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 Next › Last »