|
Description
|
This failure has happened many times during install bundling, has something to do with builds trying to skip the fastdebug build, usually happens on windows. Since the fastdebug image creation is optional, it makes sense that the install makefiles allow for an empty debug area.
I suspect it's windows only, due to the fact that the initial OUTPUTDIR for fastdebug gets created in a strange way (via a $shell) command assignment to a dummy variable, and in the make target rules. And that fact that the two dosname commands will show that the short paths to the same directory that is created twice is different:
mkdir windows-i586
dosname -s windows-i586
rm -f -r windows-i586
mkdir windows-i586
dosname -s windows-i586
I suspect the Makefile logic may be assuming that a short pathname on windows is not a changing thing. But it seems to be somewhat dynamic, perhaps uniquely created each time a new directory is created?
Posted Date : 2007-08-20 19:48:02.0
|