Community Packages

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!
Tasklist

FS#27821 - [cuda-toolkit] needs gcc <= 4.4

Attached to Project: Community Packages
Opened by hauptmech (hauptmech) - Wednesday, 04 January 2012, 12:29 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 06 January 2012, 02:11 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
nvcc does not work...

http://stackoverflow.com/questions/6622454/cuda-incompatible-with-my-gcc-version

This was not a problem when this package was in AUR because gcc44 was a dependency and nvcc.profile was modified to use it.

Not an upstream bug because Nvidia never supported > gcc 4.4

Nvidia is releasing cuda-toolkit 4.1 soon which is based on llvm. (it's at RC2 now)

Please consider moving this package back to aur until that time.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 06 January 2012, 02:11 GMT
Reason for closing:  Fixed
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 04 January 2012, 18:50 GMT
gcc44 is still in AUR. I maintain it, with the sole motivation to make nvcc happy.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 04 January 2012, 20:03 GMT
I need it for proper Blender Cycles support. Should I rename the package to reflect the current usage more properly?
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 04 January 2012, 22:52 GMT
Also, the llvm base has nothing to do with nvcc, apparently. They now merely support up to gcc 4.5. However, I was able to compile the samples so I suppose it's all good?
Comment by hauptmech (hauptmech) - Wednesday, 04 January 2012, 23:29 GMT
Unfortunately I don't have much experience with cuda so there's not a lot I can tell you. I'm building the cuda-sdk and pcl (point cloud library) using cuda-toolkit.

It all works fine with gcc44, fails with gcc current. I can get detailed fail scenarios tomorrow if it's necessary... (rather not though)

I think more packages will start depending on cuda-toolkit; so it's good to have it maintained officially. I can add (re-add the old one) a cuda-toolkit-gcc44 to aur deal with the gcc dependency I rely on.

I'm happy if you update to cuda-toolkit 4.1 as soon as it's out of rc


Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 05 January 2012, 08:11 GMT
With the rc2, I get the whole SDK to compile and Blender's CUDA core as well. Will push that for now as it seems to be the lesser evil. If you still have problems, please use an AUR package because I need some kind of cuda-toolkit package that Blender can use. However, please do tell me what kind of issues exactly you are seeing. Being able to compile the SDK is a fairly good indication I think.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 05 January 2012, 10:01 GMT
Ok, it's in the repo. Please tell me if you are still having problems.
Comment by Martin Schmidt (Blind) - Thursday, 05 January 2012, 18:10 GMT
I am sorry, I just reported two bugs in the normal arch bug system.
please search there for cuda-toolkit.

BTW: at least gcc version 4.5 is now supported. I dont think 4.6 is supported yet, but I could be wrong.

Loading...