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#27802 - [cuda-toolkit] does not provide "opencl-headers"
Attached to Project:
Community Packages
Opened by Alexander Kiselyov (yl3gdy) - Monday, 02 January 2012, 12:27 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 06 January 2012, 02:12 GMT
Opened by Alexander Kiselyov (yl3gdy) - Monday, 02 January 2012, 12:27 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 06 January 2012, 02:12 GMT
|
DetailsDescription:
Package "cuda-toolkit", which has recently reached [community], after an upgrate does not provide "opencl-headers" while it does contain these headers. Additional info: * The upgrade was from 4.0.17-2 to 4.0.17-3. Steps to reproduce: See PKGBUILD for "cuda-toolkit" and its file list. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Friday, 06 January 2012, 02:12 GMT
Reason for closing: Won't fix
Additional comments about closing: While it does ship the headers, it doesn't ship the headers in the same location as the package it would provide for and therefore it would be lying. Lying makes other packages sad and thus I won't make it provide.
Friday, 06 January 2012, 02:12 GMT
Reason for closing: Won't fix
Additional comments about closing: While it does ship the headers, it doesn't ship the headers in the same location as the package it would provide for and therefore it would be lying. Lying makes other packages sad and thus I won't make it provide.
Comment by Sven-Hendrik Haase (Svenstaro) -
Tuesday, 03 January 2012, 09:25 GMT
Since we install them to a non-standard system location, it does not technically provide them in the same way that the opencl-headers package provides them. A package that expects these headers in standard locations would fail to find them. Opinions?