| Summary: | empty file Module.symvers always left behind in root filesystem | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dick Gevers <dvgevers> |
| Component: | RPM Packages | Assignee: | Pascal Terjan <pterjan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | pterjan |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://qa.mandriva.com/show_bug.cgi?id=52624 | ||
| Whiteboard: | |||
| Source RPM: | dkms | CVE: | |
| Status comment: | |||
|
Description
Dick Gevers
2011-11-22 21:11:18 CET
> 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) =>
Triaged (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) =>
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 =>
RESOLVED |