Installing gcc-git not working

Candroidgenie · 2021-02-20 14:58:39

I am trying to move to gcc 11 and hence am installing gcc-git from the AUR.
I initially tried to install it following recommended settings and it failed (I didn't think to capture the error message).
I then tried it but when prompted removed conflicting packages:

:: gcc-libs-git and gcc-libs are in conflict. Remove gcc-libs? [y/N] y
:: gcc-git and gcc are in conflict. Remove gcc? [y/N] y
:: gcc-git and sysprof are in conflict (gcc). Remove sysprof? [y/N] y

When doing this I got the following error:

error: failed to prepare transaction (could not satisfy dependencies)
:: removing gcc breaks dependency 'gcc=10.2.0-6' required by gcc-ada

I do not need ada and likely never will however I cannot (I do not think) remove it as it is part of the larger gcc package.

Even after applying optimizations to MAKEPKG in the form of "-j12" and allowing the use of cache it still takes 12-16 hours to compile and run all the tests, requiring me to be in front of my computer for all 12-16 hours so I don't miss the sudo password timeout (which has happened). I have tried various ways of disabling the timeout to no avail.
My question is does any one have any advice on either how to fix the problem outright (allowing me to upgrade to gcc 11) or how to allow me to run the compilation in steps so that I can try different options without having to wait for 12-16 hours?

note: I am using yay as my AUR manager

loqs · 2021-02-20 15:07:40

The transaction failed but the packages were still built so you do not have to rebuild them. You can remove gcc-ada, gcc-d, gcc-fortran, gcc-go, provided no packages depend on them.

See also Sudo#Disable_password_prompt_timeout.

Slithery · 2021-02-20 15:17:16

Use makepkg to build the packages instead of yay, no sudo needed.

Candroidgenie · 2021-02-20 15:20:13

loqs wrote:

The transaction failed but the packages were still built so you do not have to rebuild them. You can remove gcc-ada, gcc-d, gcc-fortran, gcc-go, provided no packages depend on them.
See also Sudo#Disable_password_prompt_timeout.

I may be wrong in saying this but I was under the impression that MAKEPKG first builds the packages, then copied the binaries, then removed the build files. In the event of failure, no binaries are copied and then the build files are deleted.
Assuming that's not the case where would I find the binaries and where should I copy them to?

I did follow the guide for disabling the timeout and it didn't work for me.

Candroidgenie · 2021-02-20 15:23:37

Slithery wrote:

Use makepkg to build the packages instead of yay, no sudo needed.

I may be missing something but in the end, you need to copy the binaries to the correct binary directory. That requires superuser permissions regardless of method?

loqs · 2021-02-20 15:28:15

Candroidgenie wrote:

loqs wrote:
The transaction failed but the packages were still built so you do not have to rebuild them. You can remove gcc-ada, gcc-d, gcc-fortran, gcc-go, provided no packages depend on them.
See also Sudo#Disable_password_prompt_timeout.
I may be wrong in saying this but I was under the impression that MAKEPKG first builds the packages, then copied the binaries, then removed the build files. In the event of failure, no binaries are copied and then the build files are deleted.

makepkg can clean $srcdir after build completes successfully, the -c option, it does not remove built packages even if package installation fails.
By default the package is created in the same directory as the PKGBUILD. I have no idea where yay places them try ~/.cache/yay/.

Candroidgenie · 2021-02-20 15:33:50

loqs wrote:

Candroidgenie wrote:
loqs wrote:
The transaction failed but the packages were still built so you do not have to rebuild them. You can remove gcc-ada, gcc-d, gcc-fortran, gcc-go, provided no packages depend on them.
See also Sudo#Disable_password_prompt_timeout.
I may be wrong in saying this but I was under the impression that MAKEPKG first builds the packages, then copied the binaries, then removed the build files. In the event of failure, no binaries are copied and then the build files are deleted.
makepkg can clean $srcdir after build completes successfully, the -c option, it does not remove built packages even if package installation fails.
By default the package is created in the same directory as the PKGBUILD. I have no idea where yay places them try ~/.cache/yay/.

yay creates ~/.cache/yay/package_name for each package. Where though do I copy the finished binaries to?

V1del · 2021-02-20 15:37:29

You install the finished binary with pacman -U

loqs · 2021-02-20 15:37:39

See Makepkg#Usage. Covers installing the built package using pacman. You do not manually copy the binaries.

Last edited by loqs (2021-02-20 15:38:02)

Arch Linux

#1 2021-02-20 14:58:39

Installing gcc-git not working

#2 2021-02-20 15:07:40

Re: Installing gcc-git not working

#3 2021-02-20 15:17:16

Re: Installing gcc-git not working

#4 2021-02-20 15:20:13

Re: Installing gcc-git not working

#5 2021-02-20 15:23:37

Re: Installing gcc-git not working

#6 2021-02-20 15:28:15

Re: Installing gcc-git not working

#7 2021-02-20 15:33:50

Re: Installing gcc-git not working

#8 2021-02-20 15:37:29

Re: Installing gcc-git not working

#9 2021-02-20 15:37:39

Re: Installing gcc-git not working

Board footer