Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#55222 - [cuda] gcc -> gcc-5 symlink breaks system in subtle ways
Attached to Project:
Community Packages
Opened by Sami Liedes (sliedes) - Monday, 21 August 2017, 16:40 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 22 August 2017, 10:47 GMT
Opened by Sami Liedes (sliedes) - Monday, 21 August 2017, 16:40 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 22 August 2017, 10:47 GMT
|
DetailsDescription:
The cuda package installs an /opt/cuda/bin/gcc -> /usr/bin/gcc-5 symlink and adds it to the path so that "gcc" invokes gcc-5. This breaks the system in subtle ways; among other things, makepkg -si will fail for most(?) AUR packages after that, since gcc 5 does not support the -fno-plt flag. (Of course, the C++ ABI will also be different, so linking C++ code would be expected to fail.) Additional info: cuda 8.0.61-2 Steps to reproduce: 1. Install cuda 2. Try to build a package, eg. package-query, with makepkg -si |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Monday, 21 August 2017, 17:49 GMT
cuda appends /opt/cuda/bin to $PATH, so /usr/bin/gcc should be found first unless your $PATH is really screwed up.
Comment by Sami Liedes (sliedes) -
Tuesday, 22 August 2017, 08:18 GMT
Ugh, you are right, I had neglected to install base-devel on that computer. My bad!