On Sun, 31 Jul 2016 17:24:16 +0000 (UTC) "Amadeus W.M." <amadeus84@xxxxxxxxxxx> wrote: > On Sun, 31 Jul 2016 16:36:10 +0000, Rick Stevens wrote: > > > IIRC the cuda installer lets you override the check for the gcc > > version (try running the installer ".run" file with the "--help" > > option). > > > > > > Note that overrides the gcc check during installation--there's no > > guarantee that compilations will work. Cuda uses certain gcc flags > > that may be deprecated or non-existent in newer gcc implementations. > > > > > > Rick Stevens, Systems Engineer AllDigital, Inc. > > ________________________________ > > NVIDIA provides a cuda rpm repository and I installed everything from > there with dnf, so it installed with whatever defaults it came with. > And, as you said, even if it doesn't check for the compiler, it won't > necessarily compile. I'm really looking for a clean way of installing > gcc-4.9. A possible workaround would be to set the version of C that you want gcc to adhere to. I think there are flags in gcc that tell it to use, say, C99. You'd have to determine which standard gcc 4.9 aligned with, and use that one. Another possibility is to get the gcc 4.9 src.rpm from koji, build it as an rpm that installs itself in your home directory. Then, you would tell cuda to invoke that version of gcc. You could also just extract the tar file from the src.rpm and build it. It's a major undertaking, since it does several compiles. But the packages won't co-exist on the system because they'll have file collisions, especially serious in the libraries. I think you'd also have to compile statically, so that the executable built with gcc 4.9 didn't try to use the dynamic libraries from gcc 6.1. http://koji.fedoraproject.org/koji/packageinfo?buildStart=100&packageID=40&buildOrder=-completion_time&tagOrder=name&tagStart=0#buildlist I haven't ever used it, but I think that the program mock is specifically designed to work for situations like this. It builds a chroot jail, creates the required environment, and does everything there with the different build environment. So, you could build cuda using mock, but you'd have to run it in the jail so you used the appropriate libraries. Or, again, statically link it. Description : Mock takes an SRPM and builds it in a chroot. Interesting problem. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
