The only thing that comes to mind is to make dead bang sure that absolutely nothing (you, process or otherwise) has the file in question in it's grips. I've yelled and screamed at my boxen only to discover hidden away under a layer of terminal windows that I'd be doing something that the OS would interpret as access and therefore a resulting error message of 'file busy'. That it is a text file is interesting but may or may not be of help. Is the file part of previous step(s) of the make? Some sort of temporary file? You might also determine if editing (out) the entry in the make file is enough to work around the problem. Another possible source of help might be to contact the author of the module to see if anything comes to mind. Module installs are not always a simple and straight forward process and you might be running up against some need that is unobvious and problematic on your machine.
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."