Mailing List Archive

Building nvidia 310 driver for Fedora 16 x86_64
All:

I've followed Paulo's directions to build the nvidia libs and kmdl in the
past with great success; however, I've always used a src.rpm from Axel's
repository to do so. Since there isn't one yet for the 310 driver, I
thought I would follow Paulo's directions from a week or so ago to
substitute the new binary blob from nvidia and adjust the .spec file, then
rebuild the src.rpm file.

I've done that, but I get a bunch of errors when trying to build the lib
file in the form of:
-> Unable to access previously installed file
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/libnvidia-glcore.so.310.14'
(No such file or directory).
-> Unable to access previously installed file
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/libGL.so.310.14'
(No such file or directory).
-> Unable to access previously installed file
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/xorg/modules/extensions/libglx.so.310.14'
(No such file or directory).
-> Unable to access previously installed file
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/libnvidia-tls.so.310.14'
(No such file or directory).

These file are all there, but in a slightly different location. For all of
these files, the location is the same as expected by the .spec file, but
with the addition of the driver name to the path. So
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/libnvidia-glcore.so.310.14',

should really be
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/nvidia-graphics-310.14/libnvidia-glcore.so.310.14'

and
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/xorg/modules/extensions/libglx.so.310.14'
should really be
'rpmbuild/BUILDROOT/nvidia-graphics310.14-310.14-150.fc16.x86_64/usr/lib64/xorg/modules/extensions/nvidia-graphics-310.14/libglx.so.310.14'


In each case, the path differs by the addition of "nvidia-graphics-310.14"
before the file being looked for. Does anyone have any idea how to either
adjust the spec file or alter the way it looks for these files?

Thanks,

George
Re: Building nvidia 310 driver for Fedora 16 x86_64 [ In reply to ]
>
> In each case, the path differs by the addition of
> "nvidia-graphics-310.14" before the file being looked for. Does
> anyone have any idea how to either adjust the spec file or alter the
> way it looks for these files?
>
> Thanks,
>
> George
Hello Guys,

I am trying to package up the new 310.19 drivers for el6 64 bit and
striking similar issue . I my case the stopping point is :

+ mv
'/root/redhat/BUILDROOT/nvidia-graphics310.19-310.19-151.el6.x86_64/usr/lib64/lib*.so*'
/root/redhat/BUILDROOT/nvidia-graphics310.19-310.19-151.el6.x86_64/usr/lib64/nvidia-graphics-310.19/

mv: cannot stat
`/root/redhat/BUILDROOT/nvidia-graphics310.19-310.19-151.el6.x86_64/usr/lib64/lib*.so*':
No such file or directory
error: Bad exit status from /root/redhat/tmp/rpm-tmp.6Hwirh (%install)

In the previous version 304 , the compilation proceeded here like this :

+ mkdir -p
/root/redhat/BUILDROOT/nvidia-graphics304.64-304.64-150.el6.x86_64/usr/lib64/nvidia-graphics-304.64

+ mv
/root/redhat/BUILDROOT/nvidia-graphics304.64-304.64-150.el6.x86_64/usr/lib64/libXvMCNVIDIA.so.304.64
/root/redhat/BUILDROOT/nvidia-graphics304.64-304.64-150.el6.x86_64/usr/lib64/libXvMCNVIDIA_dynamic.so
/root/redhat/BUILDROOT/nvidia-graphics304.64-304.64-150.el6.x86_64/usr/lib64/libXvMCNVIDIA_dynamic.so.1
/root/redhat/BUILDROOT/nvidia-graphics304.64-304.64-150.el6.x86_64/usr/lib64/nvidia-graphics-304.64/

which is to move the libXvMCNVIDIA across to the new dir as this was the
last lot of libs to move . However the new rev 310 do not contain this
lib as we can see from the .run archive contents :

-rwxr-xr-x. 1 root root 10220750 Oct 31 05:32 libcuda.so.304.64
-rw-r--r--. 1 root root 652 Oct 31 06:06 libGL.la
-rwxr-xr-x. 1 root root 1076560 Oct 31 05:18 libGL.so.304.64
-rwxr-xr-x. 1 root root 8488456 Oct 31 05:20 libglx.so.304.64
-rwxr-xr-x. 1 root root 2196224 Oct 31 06:05 libnvcuvid.so.304.64
-rwxr-xr-x. 1 root root 144864 Oct 31 06:04 libnvidia-cfg.so.304.64
-rwxr-xr-x. 1 root root 27749808 Oct 31 06:06 libnvidia-compiler.so.304.64
-rwxr-xr-x. 1 root root 35453520 Oct 31 05:17 libnvidia-glcore.so.304.64
-rwxr-xr-x. 1 root root 394280 Oct 31 06:05 libnvidia-ml.so.304.64
-rwxr-xr-x. 1 root root 8628148 Oct 31 05:26 libnvidia-opencl.so.304.64
-rwxr-xr-x. 1 root root 11704 Oct 31 05:20 libnvidia-tls.so.304.64
-r-xr-xr-x. 1 root root 295416 Jul 6 04:35 libnvidia-wfb.so.304.64
-rwxr-xr-x. 1 root root 21296 Oct 31 05:26 libOpenCL.so.1.0.0
-rw-r--r--. 1 root root 1813064 Oct 31 05:20 libvdpau_nvidia.so.304.64
-rwxr-xr-x. 1 root root 4704 Oct 31 05:20 libvdpau.so.304.64
-rwxr-xr-x. 1 root root 46872 Oct 31 05:20 libvdpau_trace.so.304.64
-rw-r--r--. 1 root root 233540 Oct 31 05:03 libXvMCNVIDIA.a
-rwxr-xr-x. 1 root root 167000 Oct 31 05:03 libXvMCNVIDIA.so.304.64



-rwxr-xr-x. 1 root root 10321518 Nov 8 20:29 libcuda.so.310.19
-rw-r--r--. 1 root root 652 Nov 8 21:11 libGL.la
-rwxr-xr-x. 1 root root 1099472 Nov 8 20:12 libGL.so.310.19
-rwxr-xr-x. 1 root root 8623560 Nov 8 20:14 libglx.so.310.19
-rwxr-xr-x. 1 root root 2358352 Nov 8 21:10 libnvcuvid.so.310.19
-rwxr-xr-x. 1 root root 148960 Nov 8 21:09 libnvidia-cfg.so.310.19
-rwxr-xr-x. 1 root root 27749808 Nov 8 21:11 libnvidia-compiler.so.310.19
-rwxr-xr-x. 1 root root 131056 Nov 8 21:10 libnvidia-encode.so.310.19
-rwxr-xr-x. 1 root root 36540016 Nov 8 20:11 libnvidia-glcore.so.310.19
-rwxr-xr-x. 1 root root 394280 Nov 8 21:09 libnvidia-ml.so.310.19
-rwxr-xr-x. 1 root root 8612212 Nov 8 20:21 libnvidia-opencl.so.310.19
-rwxr-xr-x. 1 root root 11736 Nov 8 20:14 libnvidia-tls.so.310.19
-r-xr-xr-x. 1 root root 295416 Nov 19 2010 libnvidia-wfb.so.310.19
-rwxr-xr-x. 1 root root 21296 Nov 8 20:21 libOpenCL.so.1.0.0
-rw-r--r--. 1 root root 1813064 Nov 8 20:15 libvdpau_nvidia.so.310.19
-rwxr-xr-x. 1 root root 6304 Nov 8 20:15 libvdpau.so.310.19
-rwxr-xr-x. 1 root root 46872 Nov 8 20:15 libvdpau_trace.so.310.19

So this leaves us in a bit of a sticky situation . Specially as the
specfile goes on to link these libs as per :

mkdir -p %{buildroot}%{_x_libraries}/%{NVfolder}
mv %{buildroot}%{_x_libraries}/lib*.so*
%{buildroot}%{_x_libraries}/%{NVfolder}/
/sbin/ldconfig -n %{buildroot}%{_x_libraries}/%{NVfolder}
ln -s %{NVfolder}/libXvMCNVIDIA_dynamic.so.1
%{buildroot}%{_x_libraries}/libXvMCNVIDIA.so


We need to change this part , but not knowing what that lib did or if
there is an equivalent , this becomes a trickier proposition . Any
information welcomed on how to move on from this stalemate ..

Best Regards

Milorad


_______________________________________________
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users
Re: Building nvidia 310 driver for Fedora 16 x86_64 [ In reply to ]
On Sat, Nov 17, 2012 at 2:13 AM, O&M Ugarcina <mo.ucina@gmail.com> wrote:

>
>
>> In each case, the path differs by the addition of
>> "nvidia-graphics-310.14" before the file being looked for. Does anyone
>> have any idea how to either adjust the spec file or alter the way it looks
>> for these files?
>>
>> Thanks,
>>
>> George
>>
> Hello Guys,
>
> I am trying to package up the new 310.19 drivers for el6 64 bit and
> striking similar issue . I my case the stopping point is :
>
> + mv '/root/redhat/BUILDROOT/**nvidia-graphics310.19-310.19-**
> 151.el6.x86_64/usr/lib64/lib*.**so*' /root/redhat/BUILDROOT/nvidia-**
> graphics310.19-310.19-151.el6.**x86_64/usr/lib64/nvidia-**graphics-310.19/
>
> mv: cannot stat `/root/redhat/BUILDROOT/**nvidia-graphics310.19-310.19-**
> 151.el6.x86_64/usr/lib64/lib*.**so*': No such file or directory
> error: Bad exit status from /root/redhat/tmp/rpm-tmp.**6Hwirh (%install)
>
> In the previous version 304 , the compilation proceeded here like this :
>
> + mkdir -p /root/redhat/BUILDROOT/nvidia-**graphics304.64-304.64-150.el6.*
> *x86_64/usr/lib64/nvidia-**graphics-304.64
>
> + mv /root/redhat/BUILDROOT/nvidia-**graphics304.64-304.64-150.el6.**
> x86_64/usr/lib64/**libXvMCNVIDIA.so.304.64 /root/redhat/BUILDROOT/nvidia-*
> *graphics304.64-304.64-150.el6.**x86_64/usr/lib64/**libXvMCNVIDIA_dynamic.so
> /root/redhat/BUILDROOT/nvidia-**graphics304.64-304.64-150.el6.**
> x86_64/usr/lib64/**libXvMCNVIDIA_dynamic.so.1
> /root/redhat/BUILDROOT/nvidia-**graphics304.64-304.64-150.el6.**
> x86_64/usr/lib64/nvidia-**graphics-304.64/
>
> which is to move the libXvMCNVIDIA across to the new dir as this was the
> last lot of libs to move . However the new rev 310 do not contain this lib
> as we can see from the .run archive contents :
>
> -rwxr-xr-x. 1 root root 10220750 Oct 31 05:32 libcuda.so.304.64
> -rw-r--r--. 1 root root 652 Oct 31 06:06 libGL.la
> -rwxr-xr-x. 1 root root 1076560 Oct 31 05:18 libGL.so.304.64
> -rwxr-xr-x. 1 root root 8488456 Oct 31 05:20 libglx.so.304.64
> -rwxr-xr-x. 1 root root 2196224 Oct 31 06:05 libnvcuvid.so.304.64
> -rwxr-xr-x. 1 root root 144864 Oct 31 06:04 libnvidia-cfg.so.304.64
> -rwxr-xr-x. 1 root root 27749808 Oct 31 06:06 libnvidia-compiler.so.304.64
> -rwxr-xr-x. 1 root root 35453520 Oct 31 05:17 libnvidia-glcore.so.304.64
> -rwxr-xr-x. 1 root root 394280 Oct 31 06:05 libnvidia-ml.so.304.64
> -rwxr-xr-x. 1 root root 8628148 Oct 31 05:26 libnvidia-opencl.so.304.64
> -rwxr-xr-x. 1 root root 11704 Oct 31 05:20 libnvidia-tls.so.304.64
> -r-xr-xr-x. 1 root root 295416 Jul 6 04:35 libnvidia-wfb.so.304.64
> -rwxr-xr-x. 1 root root 21296 Oct 31 05:26 libOpenCL.so.1.0.0
> -rw-r--r--. 1 root root 1813064 Oct 31 05:20 libvdpau_nvidia.so.304.64
> -rwxr-xr-x. 1 root root 4704 Oct 31 05:20 libvdpau.so.304.64
> -rwxr-xr-x. 1 root root 46872 Oct 31 05:20 libvdpau_trace.so.304.64
> -rw-r--r--. 1 root root 233540 Oct 31 05:03 libXvMCNVIDIA.a
> -rwxr-xr-x. 1 root root 167000 Oct 31 05:03 libXvMCNVIDIA.so.304.64
>
>
>
> -rwxr-xr-x. 1 root root 10321518 Nov 8 20:29 libcuda.so.310.19
> -rw-r--r--. 1 root root 652 Nov 8 21:11 libGL.la
> -rwxr-xr-x. 1 root root 1099472 Nov 8 20:12 libGL.so.310.19
> -rwxr-xr-x. 1 root root 8623560 Nov 8 20:14 libglx.so.310.19
> -rwxr-xr-x. 1 root root 2358352 Nov 8 21:10 libnvcuvid.so.310.19
> -rwxr-xr-x. 1 root root 148960 Nov 8 21:09 libnvidia-cfg.so.310.19
> -rwxr-xr-x. 1 root root 27749808 Nov 8 21:11 libnvidia-compiler.so.310.19
> -rwxr-xr-x. 1 root root 131056 Nov 8 21:10 libnvidia-encode.so.310.19
> -rwxr-xr-x. 1 root root 36540016 Nov 8 20:11 libnvidia-glcore.so.310.19
> -rwxr-xr-x. 1 root root 394280 Nov 8 21:09 libnvidia-ml.so.310.19
> -rwxr-xr-x. 1 root root 8612212 Nov 8 20:21 libnvidia-opencl.so.310.19
> -rwxr-xr-x. 1 root root 11736 Nov 8 20:14 libnvidia-tls.so.310.19
> -r-xr-xr-x. 1 root root 295416 Nov 19 2010 libnvidia-wfb.so.310.19
> -rwxr-xr-x. 1 root root 21296 Nov 8 20:21 libOpenCL.so.1.0.0
> -rw-r--r--. 1 root root 1813064 Nov 8 20:15 libvdpau_nvidia.so.310.19
> -rwxr-xr-x. 1 root root 6304 Nov 8 20:15 libvdpau.so.310.19
> -rwxr-xr-x. 1 root root 46872 Nov 8 20:15 libvdpau_trace.so.310.19
>
> So this leaves us in a bit of a sticky situation . Specially as the
> specfile goes on to link these libs as per :
>
> mkdir -p %{buildroot}%{_x_libraries}/%{**NVfolder}
> mv %{buildroot}%{_x_libraries}/**lib*.so* %{buildroot}%{_x_libraries}/%{**
> NVfolder}/
> /sbin/ldconfig -n %{buildroot}%{_x_libraries}/%{**NVfolder}
> ln -s %{NVfolder}/libXvMCNVIDIA_**dynamic.so.1
> %{buildroot}%{_x_libraries}/**libXvMCNVIDIA.so
>
>
> We need to change this part , but not knowing what that lib did or if
> there is an equivalent , this becomes a trickier proposition . Any
> information welcomed on how to move on from this stalemate ..
>
> Best Regards
>
> Milorad
>
>
First of all, if you define a macro (tcsh):

alias reval 'rpm --eval "%{\!*}"'

and,

[cascavel:~/RPMS174/updates] reval %{_x_libraries}
%{/usr/lib64}

will expand the spec macros, so you know the real paths.

Then, you need to see what is being installed in
~/redhat/BUILD and ~/redhat/BUILDROOT
and try to fix the spec accordingly ....


--
Paulo Roma Cavalcanti
DCC - UFRJ
Re: Building nvidia 310 driver for Fedora 16 x86_64 [ In reply to ]
On Mon, Nov 19, 2012 at 2:45 PM, George Galt <george.galt@gmail.com> wrote:

> On Mon, Nov 19, 2012 at 5:24 AM, Paulo Cavalcanti <promac@gmail.com>wrote:
>
>>
>>
>> On Sat, Nov 17, 2012 at 2:13 AM, O&M Ugarcina <mo.ucina@gmail.com> wrote:
>>
>>>
>>>
>>>> In each case, the path differs by the addition of
>>>> "nvidia-graphics-310.14" before the file being looked for. Does anyone
>>>> have any idea how to either adjust the spec file or alter the way it looks
>>>> for these files?
>>>>
>>>> Thanks,
>>>>
>>>> George
>>>>
>>> Hello Guys,
>>>
>>>

I have a fixed .src.rpm, here:

http://people.atrpms.net/~pcavalcanti/srpms/nvidia-graphics310.19-310.19-151.fc17.src.rpm

In fact, the fix was easy, and I just had to comment a few lines in the
spec file.

However, when installing, rpm keeps complaining about

libnvcuvid.so()(64bit) is needed by
nvidia-graphics310.19-libs-310.19-151.fc17.x86_64

I just used --nodeps and everything installs and runs fine.

Maybe someone can take a look and figure what is going on...


--
Paulo Roma Cavalcanti
DCC - UFRJ
Re: Building nvidia 310 driver for Fedora 16 x86_64 [ In reply to ]
Paulo:

Oddly, prior iterations of the nvidia-graphics-libs didn't require
libnvcuvid.so, even though they installed them. I'm currently running the
304.51 driver, and rpm reports:

rpm -q --requires -p nvidia-graphics304.51-libs-304.51-149.fc16.x86_64.rpm
/bin/sh
/bin/sh
libX11.so.6()(64bit)
libXext.so.6()(64bit)
libXv.so.1()(64bit)
libXvMC.so.1()(64bit)
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libdl.so.2()(64bit)
libdl.so.2(GLIBC_2.2.5)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libgcc_s.so.1(GCC_3.3)(64bit)
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
libnvidia-glcore.so.304.51()(64bit)
libnvidia-tls.so.304.51()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
librt.so.1()(64bit)
librt.so.1(GLIBC_2.2.5)(64bit)
libvdpau.so.1()(64bit)
libvdpau_nvidia.so.1()(64bit)
libvdpau_trace.so.1()(64bit)
libz.so.1()(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1

and the driver also installed libnvcuvid.so as:
/usr/lib64/nvidia-graphics-304.51/libnvcuvid.so.1
/usr/lib64/nvidia-graphics-304.51/libnvcuvid.so.304.51

As you can see, the new 310 driver, unlike the 304 driver, requires
libnvcuvid:
rpm -q --requires -p nvidia-graphics310.19-libs-310.19-151.fc16.x86_64.rpm
/bin/sh
/bin/sh
libX11.so.6()(64bit)
libXext.so.6()(64bit)
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libdl.so.2()(64bit)
libdl.so.2(GLIBC_2.2.5)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libgcc_s.so.1(GCC_3.3)(64bit)
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
libnvcuvid.so()(64bit)
libnvidia-glcore.so.310.19()(64bit)
libnvidia-tls.so.310.19()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
librt.so.1()(64bit)
librt.so.1(GLIBC_2.2.5)(64bit)
libvdpau.so.1()(64bit)
libvdpau_nvidia.so.1()(64bit)
libvdpau_trace.so.1()(64bit)
libz.so.1()(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1


But you can see that the package will install it:
rpm -q --filesbypkg -p nvidia-graphics310.19-libs-310.19-151.fc16.x86_64.rpm
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libGL.so.1
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libGL.so.310.19
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1.0
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1.0.0
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libcuda.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libcuda.so.310.19
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libnvcuvid.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvcuvid.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-cfg.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-cfg.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-compiler.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-encode.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-encode.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-glcore.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-ml.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-ml.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-opencl.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-opencl.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libnvidia-tls.so.310.19
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libvdpau.so
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libvdpau.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libvdpau.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libvdpau_nvidia.so
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/libvdpau_trace.so
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/tls
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/tls/libnvidia-tls.so.310.19
nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/vdpau
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_nvidia.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_nvidia.so.310.19
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_trace.so.1
nvidia-graphics310.19-libs
/usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_trace.so.310.19


Do you know where the "requires" variables are set? I am assuming that it
is something in the SPEC file. We could simply take the route of prior
drivers and eliminate libnvcuvid.so() from the list of requirements. But
it seems odd that it requires a file that it will install itself without
being aware that it will deliver its own "requirement".

In any event, it seems that installing this with --nodeps will be OK, but I
would just prefer to fix the correct files so that others can comfortably
do the install.

George



On Sat, Dec 1, 2012 at 8:50 AM, Paulo Cavalcanti <promac@gmail.com> wrote:

>
>
> On Mon, Nov 19, 2012 at 2:45 PM, George Galt <george.galt@gmail.com>wrote:
>
>> On Mon, Nov 19, 2012 at 5:24 AM, Paulo Cavalcanti <promac@gmail.com>wrote:
>>
>>>
>>>
>>> On Sat, Nov 17, 2012 at 2:13 AM, O&M Ugarcina <mo.ucina@gmail.com>wrote:
>>>
>>>>
>>>>
>>>>> In each case, the path differs by the addition of
>>>>> "nvidia-graphics-310.14" before the file being looked for. Does anyone
>>>>> have any idea how to either adjust the spec file or alter the way it looks
>>>>> for these files?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> George
>>>>>
>>>> Hello Guys,
>>>>
>>>>
>
> I have a fixed .src.rpm, here:
>
>
> http://people.atrpms.net/~pcavalcanti/srpms/nvidia-graphics310.19-310.19-151.fc17.src.rpm
>
> In fact, the fix was easy, and I just had to comment a few lines in the
> spec file.
>
> However, when installing, rpm keeps complaining about
>
> libnvcuvid.so()(64bit) is needed by
> nvidia-graphics310.19-libs-310.19-151.fc17.x86_64
>
> I just used --nodeps and everything installs and runs fine.
>
> Maybe someone can take a look and figure what is going on...
>
>
>
> --
> Paulo Roma Cavalcanti
> DCC - UFRJ
>
Re: Building nvidia 310 driver for Fedora 16 x86_64 [ In reply to ]
Paulo:

Sorry, I also meant to include a diff from the 304.51 spec file to the
310.19. Nothing jumps out at me:

diff nvidia-graphics304.51.spec nvidia-graphics310.19.spec
2,3c2,3
< Version: 304.51
< Release: 149%{?dist}
---
> Version: 310.19
> Release: 151%{?dist}
191c191
< mv %{buildroot}%{_x_libraries}/lib*.so*
%{buildroot}%{_x_libraries}/%{NVfolder}/
---
> #mv %{buildroot}%{_x_libraries}/lib*.so*
%{buildroot}%{_x_libraries}/%{NVfolder}/
193c193
< ln -s %{NVfolder}/libXvMCNVIDIA_dynamic.so.1
%{buildroot}%{_x_libraries}/libXvMCNVIDIA.so
---
> #ln -s %{NVfolder}/libXvMCNVIDIA_dynamic.so.1
%{buildroot}%{_x_libraries}/libXvMCNVIDIA.so
287c287
< %{_x_libraries}/%{NVfolder}/libXvMCNVIDIA*.so.*
---
> #%{_x_libraries}/%{NVfolder}/libXvMCNVIDIA*.so.*
306,308c306,308
< %{_x_libraries}/libXvMCNVIDIA.a
< %{_x_libraries}/libXvMCNVIDIA.so
< %{_x_libraries}/%{NVfolder}/libXvMCNVIDIA_dynamic.so
---
> #%{_x_libraries}/libXvMCNVIDIA.a
> #%{_x_libraries}/libXvMCNVIDIA.so
> #%{_x_libraries}/%{NVfolder}/libXvMCNVIDIA_dynamic.so
327c327,333
< * Sun Oct 21 2012 Axel Thimm Paulo Roma <roma@lcg.ufrj.br> - 304.51-149
---
> * Sat Dec 01 2012 Paulo Roma <roma@lcg.ufrj.br> - 310.19-151
> - Update to 310.19.
>
> * Fri Nov 9 2012 Axel Thimm <Axel.Thimm@ATrpms.net> - 304.64-150
> - Update to 304.64.
>
> * Sun Oct 21 2012 Paulo Roma Paulo Roma <roma@lcg.ufrj.br> - 304.51-149



On Tue, Dec 4, 2012 at 3:08 PM, George Galt <george.galt@gmail.com> wrote:

> Paulo:
>
> Oddly, prior iterations of the nvidia-graphics-libs didn't require
> libnvcuvid.so, even though they installed them. I'm currently running the
> 304.51 driver, and rpm reports:
>
> rpm -q --requires -p nvidia-graphics304.51-libs-304.51-149.fc16.x86_64.rpm
> /bin/sh
> /bin/sh
> libX11.so.6()(64bit)
> libXext.so.6()(64bit)
> libXv.so.1()(64bit)
> libXvMC.so.1()(64bit)
> libc.so.6()(64bit)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libdl.so.2()(64bit)
> libdl.so.2(GLIBC_2.2.5)(64bit)
> libgcc_s.so.1()(64bit)
> libgcc_s.so.1(GCC_3.0)(64bit)
> libgcc_s.so.1(GCC_3.3)(64bit)
> libm.so.6()(64bit)
> libm.so.6(GLIBC_2.2.5)(64bit)
> libnvidia-glcore.so.304.51()(64bit)
> libnvidia-tls.so.304.51()(64bit)
> libpthread.so.0()(64bit)
> libpthread.so.0(GLIBC_2.2.5)(64bit)
> librt.so.1()(64bit)
> librt.so.1(GLIBC_2.2.5)(64bit)
> libvdpau.so.1()(64bit)
> libvdpau_nvidia.so.1()(64bit)
> libvdpau_trace.so.1()(64bit)
> libz.so.1()(64bit)
> rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(FileDigests) <= 4.6.0-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(PayloadIsXz) <= 5.2-1
>
> and the driver also installed libnvcuvid.so as:
> /usr/lib64/nvidia-graphics-304.51/libnvcuvid.so.1
> /usr/lib64/nvidia-graphics-304.51/libnvcuvid.so.304.51
>
> As you can see, the new 310 driver, unlike the 304 driver, requires
> libnvcuvid:
> rpm -q --requires -p nvidia-graphics310.19-libs-310.19-151.fc16.x86_64.rpm
> /bin/sh
> /bin/sh
> libX11.so.6()(64bit)
> libXext.so.6()(64bit)
> libc.so.6()(64bit)
> libc.so.6(GLIBC_2.2.5)(64bit)
> libdl.so.2()(64bit)
> libdl.so.2(GLIBC_2.2.5)(64bit)
> libgcc_s.so.1()(64bit)
> libgcc_s.so.1(GCC_3.0)(64bit)
> libgcc_s.so.1(GCC_3.3)(64bit)
> libm.so.6()(64bit)
> libm.so.6(GLIBC_2.2.5)(64bit)
> libnvcuvid.so()(64bit)
> libnvidia-glcore.so.310.19()(64bit)
> libnvidia-tls.so.310.19()(64bit)
> libpthread.so.0()(64bit)
> libpthread.so.0(GLIBC_2.2.5)(64bit)
> librt.so.1()(64bit)
> librt.so.1(GLIBC_2.2.5)(64bit)
> libvdpau.so.1()(64bit)
> libvdpau_nvidia.so.1()(64bit)
> libvdpau_trace.so.1()(64bit)
> libz.so.1()(64bit)
> rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(FileDigests) <= 4.6.0-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(PayloadIsXz) <= 5.2-1
>
>
> But you can see that the package will install it:
> rpm -q --filesbypkg -p
> nvidia-graphics310.19-libs-310.19-151.fc16.x86_64.rpm
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libGL.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libGL.so.310.19
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1.0
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libOpenCL.so.1.0.0
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libcuda.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libcuda.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvcuvid.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvcuvid.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-cfg.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-cfg.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-compiler.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-encode.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-encode.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-glcore.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-ml.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-ml.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-opencl.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-opencl.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libnvidia-tls.so.310.19
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libvdpau.so
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/libvdpau.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libvdpau.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libvdpau_nvidia.so
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/libvdpau_trace.so
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/tls
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/tls/libnvidia-tls.so.310.19
> nvidia-graphics310.19-libs /usr/lib64/nvidia-graphics-310.19/vdpau
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_nvidia.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_nvidia.so.310.19
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_trace.so.1
> nvidia-graphics310.19-libs
> /usr/lib64/nvidia-graphics-310.19/vdpau/libvdpau_trace.so.310.19
>
>
> Do you know where the "requires" variables are set? I am assuming that it
> is something in the SPEC file. We could simply take the route of prior
> drivers and eliminate libnvcuvid.so() from the list of requirements. But
> it seems odd that it requires a file that it will install itself without
> being aware that it will deliver its own "requirement".
>
> In any event, it seems that installing this with --nodeps will be OK, but
> I would just prefer to fix the correct files so that others can comfortably
> do the install.
>
> George
>
>
>
>
> On Sat, Dec 1, 2012 at 8:50 AM, Paulo Cavalcanti <promac@gmail.com> wrote:
>
>>
>>
>> On Mon, Nov 19, 2012 at 2:45 PM, George Galt <george.galt@gmail.com>wrote:
>>
>>> On Mon, Nov 19, 2012 at 5:24 AM, Paulo Cavalcanti <promac@gmail.com>wrote:
>>>
>>>>
>>>>
>>>> On Sat, Nov 17, 2012 at 2:13 AM, O&M Ugarcina <mo.ucina@gmail.com>wrote:
>>>>
>>>>>
>>>>>
>>>>>> In each case, the path differs by the addition of
>>>>>> "nvidia-graphics-310.14" before the file being looked for. Does anyone
>>>>>> have any idea how to either adjust the spec file or alter the way it looks
>>>>>> for these files?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> George
>>>>>>
>>>>> Hello Guys,
>>>>>
>>>>>
>>
>> I have a fixed .src.rpm, here:
>>
>>
>> http://people.atrpms.net/~pcavalcanti/srpms/nvidia-graphics310.19-310.19-151.fc17.src.rpm
>>
>> In fact, the fix was easy, and I just had to comment a few lines in the
>> spec file.
>>
>> However, when installing, rpm keeps complaining about
>>
>> libnvcuvid.so()(64bit) is needed by
>> nvidia-graphics310.19-libs-310.19-151.fc17.x86_64
>>
>> I just used --nodeps and everything installs and runs fine.
>>
>> Maybe someone can take a look and figure what is going on...
>>
>>
>>
>> --
>> Paulo Roma Cavalcanti
>> DCC - UFRJ
>>
>
>