Package Base Details: gcc-git

Git Clone URL: (read-only, click to copy)
Submitter: Allan
Maintainer: jamespharvey20
Last Packager: jamespharvey20
Votes: 11
Popularity: 0.001383
First Submitted: 2013-06-26 03:43
Last Updated: 2019-10-13 02:29

Pinned Comments

jamespharvey20 commented on 2019-10-13 02:28

Temporarily hold to commit fcab78b9 (2019-10-01 18:21:31.) Otherwise, fails to build. There are several breaking commits after this, involving packaging failures on ada and a bootstrap failure when comparing stages 2 and 3.

jamespharvey20 commented on 2017-02-15 04:30

*** 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 2 3 4 5 6 7 Next › Last »

sir_lucjan commented on 2017-02-08 16:26

I've PKGBUILD but without gcc-ada-git. Are you interesed?

sleeping commented on 2017-02-08 16:23

Thanks for your effort James.
Would be really great to have this working again. :)

jamespharvey20 commented on 2017-02-08 11:13

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

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().
==> 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

Cannot install, tried on 3 machines

janisozaur commented on 2016-02-25 11:05

It seems ISL 0.16.1 is available now and mentions it as a compatible, can you check & update the PKGBUILD?

See!topic/isl-announce/i8PTGG0ZbzE for announcment

jamespharvey20 commented on 2015-12-13 21:00

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

Think this is where it came from:

^^^ "This is a minimally invasive change"

Then brought downstream into GCC:;a=commit;h=c14bac81551d6769741c2b1cc55e04d94fe8d3a7

Allan commented on 2015-12-13 10:48

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

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:

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.