Sources (2)

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.

EndlessEden commented on 2017-05-21 00:27

Please update the PKGBUILD to conform with binutils-git(s/binutils>=2.26/binutils>=2.29/)

jamespharvey20 commented on 2017-04-03 01:28

@giacombum. Also, I've never used yaourt before. But, out of curiosity, in a VM, I installed yaourt and successfully built gcc-git 7.0.1.r153096.7714131b8c8-1.

jamespharvey20 commented on 2017-04-02 04:21

@giacombum. This is caused by your CHOST environment variable being set incorrectly.

My bet is: (1) in your /etc/makepkg.conf, your CHOST is set to "x86_64-unknown-linux-gnu", rather than "x86_64-pc-linux-gnu"; and (2) there's probably an /etc/makepkg.conf.pacnew file. If this is the case, if you never made custom modifications to makepkg.conf, move the .pacnew file to the .conf file. Read up at https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave, and read through pacman notifications when upgrading packages for the future.

Please comment back if this was the issue or not.

I ran into the exact failure you're having in late 2015 (you can see comments on this package) when upstream gcc git changed, and no longer expected the vendor portion of CHOST to be "unknown". On a x86_64 platform, it started expecting "pc".

In late 2015, I changed this PKGBUILD to have a workaround of changing unknown to pc, which should have worked for everyone on x86_64 platforms. On 2/15/2017, I changed the PKGBUILD to mirror the gcc (non git) package, which was able to avoid this workaround since /etc/makepkg.conf had been changed to use "pc".

You'll see in the beginning part of your build, it's properly using "x86_64-pc-linux-gnu". Then, you hit PKGBUILD line 110 (just after running "make") which is "make -C $CHOST/libstdc++-v3/doc doc-man-doxygen" which causes the failure.

jamespharvey20 commented on 2017-02-15 10:53

Allan commented on 2017-02-15 04:46

Well... I when originally uploaded this package, it had provides/conflicts/replaces entries. So i guess my opinion is they should be there.

Nothing should be installed into /usr/local. People can have this as a standalone gcc-git package does not not replace the system version by adding this to configure:
"--program-suffix=-git --enable-version-specific-runtime-libs"

jamespharvey20 commented on 2017-02-15 04:38

@Allan - Thanks! I didn't even get to send my pacman-dev email. :-) By the way, what are your thoughts on replacing (provides/conflicts) the core gcc* packages? Do you think it's appropriate to have a warning posted, since it doesn't seem to have caused a problem for anyone recently? Or, would you urge it to be moved into /usr/local?

Allan commented on 2017-02-15 04:35

You need to add a version to your provides. E.g.

provides=('gcc-libs=7.0.1')

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.

* Now uses the github mirror repo. I had many times recently where the git clone from the upstream gcc git repo failed, or took even longer than the long time it is expected to take. I've seen this in the past for the official repo also.
* Has been updated to parse _pkgver_base, _pkgver, and _libdir, rather than be hardcoded.
* Uses isl 0.18

EDIT: The rest no longer applies. See more recent comments.

But, I haven't been able to install it using pacman. I haven't ever used pacaur or yaourt, but I'll probably check if those successfully install it somehow.

Trying to remove gcc-libs without accounting for that gcc-libs-git will take its place marks almost every package installed for removal. (Just run pactree --reverse gcc-libs and you'll see almost everything installed.)

This used to work. I'm thinking a pacman change must have been made, so it doesn't recognize that the -git version provide the non-git versions, when examining broken dependencies.

(EDIT: This is no longer being considered.) That made me consider having gcc*-git install to /usr/local instead for 2 reasons. (1) Replacing the system gcc-libs can be dangerous. In practice, I and others haven't had problems with it recently, but the possible danger remains. (2) It would avoid the pacman issues above. I've almost completed this switch.

I'm going to reach out to the pacman devs to see if its current refusal to replace the non-git versions with git versions is desirable or not.