I regularly use dkms to build & install fglrx for new Cauldron kernels. Each time it leaves behind a zero byte file in "/" with the name: Module.symvers. Maybe line 1384 of /usr/sbin/dkms does this. It seems to me it would be better left in /tmp, for example. Version-Release number of selected component (if applicable): How reproducible: always This bug was sort of cloned from the bug shown at the URL
> I regularly use dkms to build & install fglrx for new Cauldron kernels. Automatically or manuals ? > Each time it leaves behind a zero byte file in "/" with the name: > Module.symvers. Here the file is about 36Ko (automatically and in mga1 )
Both auto & manual.
Assigned to the package maintainer.
Keywords: (none) => TriagedAssignee: bugsquad => doktor5000Source RPM: dkms-minimal-2.0.19-24.mga1 => dkms
(In reply to comment #1) > > > Each time it leaves behind a zero byte file in "/" with the name: > > Module.symvers. > > Here the file is about 36Ko (automatically and in mga1 ) Here it's also zero byte, and i regularly use it for nvidia and virtualbox. Will look into it.
Status: NEW => ASSIGNED
For references, this seems to come from one of our patches, not dkms itself: http://svnweb.mageia.org/packages/updates/1/dkms/current/SOURCES/dkms-symvers.patch?view=markup Seems it was an oversight to not check/remove the leftover file.
It should be created in the build directory, I guess this function changed to no longer be run from there. I'll update the patch to create it at the right place.
CC: (none) => pterjanAssignee: doktor5000 => pterjan
OK, actually the error was a bit further when creating one for each module to be built. It was created in "${built_module_location[$count]}/Module.symvers" but built_module_location can be empty if the module is built at the root of the sources. I fixed it in dkms-2.0.19-25.mga2.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED