[Bug 459] New: Review request: nvidia-cuda-toolkit - NVIDIA CUDA Toolkit libraries

RPM Fusion Bugzilla noreply at rpmfusion.org
Sun Mar 22 14:58:01 CET 2009


http://bugzilla.rpmfusion.org/show_bug.cgi?id=459

           Summary: Review request: nvidia-cuda-toolkit - NVIDIA CUDA
                    Toolkit libraries
           Product: Package Reviews
           Version: Current
          Platform: All
        OS/Version: GNU/Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Review Request
        AssignedTo: rpmfusion-package-review at rpmfusion.org
        ReportedBy: xjakub at fi.muni.cz
                CC: rpmfusion-package-review at rpmfusion.org
            Blocks: 2
   Estimated Hours: 0.0


SPEC:
http://mjakubicek.fedorapeople.org/nvidia-cuda-toolkit/nvidia-cuda-toolkit.spec
SRPM:
http://mjakubicek.fedorapeople.org/nvidia-cuda-toolkit/nvidia-cuda-toolkit-2.1-1.src.rpm

Description:
NVIDIA(R)CUDA(TM) is a general purpose parallel computing architecture
that leverages the parallel compute engine in NVIDIA graphics
processing units (GPUs) to solve many complex computational problems
in a fraction of the time required on a CPU. It includes the CUDA
Instruction Set Architecture (ISA) and the parallel compute engine in
the GPU. To program to the CUDATM architecture, developers can, today,
use C, one of the most widely used high-level programming languages,
which can then be run at great performance on a CUDATM enabled
processor. Other languages will be supported in the future, including
FORTRAN and C++.

Why this package is not eligible to be included in Fedora:
Not open source.

rpmlint output:

>rpmlint ../SRPMS/nvidia-cuda-toolkit-2.1-1.src.rpm
nvidia-cuda-toolkit.src:53: E: hardcoded-library-path in %{_prefix}/lib

This is ok, even moving file from the hardcoded path.

nvidia-cuda-toolkit.src: W: no-%build-section

Nothing to build. This, however, implies no stripping & no debuginfo.
Unfortunately, debuginfo creation fails because the binaries don't contatin
build id. I don't know whether there is something I could do with this.

>rpmlint ../RPMS/x86_64/nvidia-cuda-toolkit-*
nvidia-cuda-toolkit.x86_64: W: unstripped-binary-or-object /usr/bin/bec
nvidia-cuda-toolkit.x86_64: W: unstripped-binary-or-object /usr/bin/inline
nvidia-cuda-toolkit.x86_64: W: unstripped-binary-or-object /usr/bin/be
nvidia-cuda-toolkit.x86_64: W: unstripped-binary-or-object /usr/bin/gfec
nvidia-cuda-toolkit.x86_64: W: unstripped-binary-or-object /usr/bin/nvopencc

See the previous comment.

nvidia-cuda-toolkit.x86_64: W: shared-lib-calls-exit /usr/lib64/libcufft.so.2.1
exit at GLIBC_2.2.5
nvidia-cuda-toolkit.x86_64: W: shared-lib-calls-exit
/usr/lib64/libcufftemu.so.2.1 exit at GLIBC_2.2.5
nvidia-cuda-toolkit.x86_64: W: shared-lib-calls-exit
/usr/lib64/libcudart.so.2.1 exit at GLIBC_2.2.5

Again, there is nothing we can do with this, AFAIK.

This is my first RPM Fusion package, I'm already a Fedora packager (both FAS
names are mjakubicek). My primary motivation to package this is that I maintain
a CUDA-enabled application, see
https://bugzilla.redhat.com/show_bug.cgi?id=487981.


-- 
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the rpmfusion-developers mailing list