10:15 p.m.
Hi,
I'm having trouble with the akmod build of the nvidia module, log:
=====
13 Apr 08:08:43 akmods: Building RPM using the command
'/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.35.11-83.fc14.x86_64
/usr/src/akmods/nvidia-kmod.latest'
tail: cannot open `/tmp/akmodsbuild.OFge8ysC/.jobexit' for reading: No
such file or directory
/usr/bin/akmodsbuild: line 218: ((: != 0 : syntax error: operand
expected (error token is "!= 0 ")
mv: cannot stat `/tmp/akmodsbuild.OFge8ysC/RPMS/x86_64/*': No such file
or directory
13 Apr 08:08:43 akmodsbuild: * Rebuilding
/usr/src/akmods/nvidia-kmod.latest for kernel(s)
2.6.35.11-83.fc14.x86_64: /usr/bin/akmodsbuild: line 185: /usr/bin/time:
No such file or directory
13 Apr 08:08:43 akmodsbuild:
13 Apr 08:08:43 akmodsbuild: Failed to move
/tmp/akmodsbuild.OFge8ysC/RPMS/x86_64/* to /tmp/akmods.5KJJZTjz/results
13 Apr 08:08:43 akmods: Building rpms failed; see
/var/cache/akmods/nvidia/260.19.36-1-for-2.6.35.11-83.fc14.x86_64.failed.log
for details
=====
Is this because it doesn't have access to the /tmp folder ?
Or maybe something disappears between creation and next read ?
7:24 a.m.
2011/4/13 David Timms <dtimms(a)iinet.net.au>:
Hi,
I'm having trouble with the akmod build of the nvidia module, log:
=====
13 Apr 08:08:43 akmods: Building RPM using the command '/usr/bin/akmodsbuild
--target x86_64 --kernels 2.6.35.11-83.fc14.x86_64
/usr/src/akmods/nvidia-kmod.latest'
tail: cannot open `/tmp/akmodsbuild.OFge8ysC/.jobexit' for reading: No such
file or directory
/usr/bin/akmodsbuild: line 218: ((: != 0 : syntax error: operand expected
(error token is "!= 0 ")
mv: cannot stat `/tmp/akmodsbuild.OFge8ysC/RPMS/x86_64/*': No such file or
directory
13 Apr 08:08:43 akmodsbuild: * Rebuilding /usr/src/akmods/nvidia-kmod.latest
for kernel(s) 2.6.35.11-83.fc14.x86_64: /usr/bin/akmodsbuild: line 185:
/usr/bin/time: No such file or directory
13 Apr 08:08:43 akmodsbuild:
13 Apr 08:08:43 akmodsbuild: Failed to move
/tmp/akmodsbuild.OFge8ysC/RPMS/x86_64/* to /tmp/akmods.5KJJZTjz/results
13 Apr 08:08:43 akmods: Building rpms failed; see
/var/cache/akmods/nvidia/260.19.36-1-for-2.6.35.11-83.fc14.x86_64.failed.log
for details
=====
Is this because it doesn't have access to the /tmp folder ?
Or maybe something disappears between creation and next read ?
Are you running a minimal environnement ?
Can you retry with yum install time , it may have to be added to the
akmod package.
Nicolas (kwizart)
11:19 a.m.
New subject: akmod nvidia - failing to build - time rpm fixes it
On 13/04/11 17:24, Nicolas Chauvet wrote:
Are you running a minimal environnement ?
Not really, but did
have some trouble during install, that was manually
fixed.
Can you retry with yum install time , it may have to be added to the
akmod package.
When I had seen the indication of time mentioned, I checked that
"time"
worked:
time:
real 0m0.000s
user 0m0.000s
sys 0m0.000s
However, this must be a built in.
yum install time gives /usr/bin/time:
/usr/bin/time ls h
ls: cannot access h: No such file or directory
0.00user 0.00system 0:00.00elapsed 0%CPU (0avgtext+0avgdata
3840maxresident)k
0inputs+0outputs (0major+299minor)pagefaults 0swaps
Now a: akmods --force --kernels 2.6.35.11-83.fc14.x86_64
Checking kmods exist for 2.6.35.11-83.fc14.x86_64 [ OK ]
Building and installing nvidia-kmod [ OK ]
succeeds. (I only installed the nvidia driver this past week, so hadn't
seen this occur before).
Unless time.rpm is in the default install, it seems it would be good to
install it. Cheers.
4972
days inactive
4973
days old
rpmfusion-developers@lists.rpmfusion.org
2 comments
2 participants
participants (2)
-
Agnes Jones -
Nicolas Chauvet