Hi ,
I am using Gnu Make 3.80 on windows. I have few Gnu Make operating conditions in some situations under Windows listed in the below. Could you please explain how Gnu Make behaves under these operating conditions? I hope this may take time. Could you please give a quick explanation in less words if possible.
The listed operating conditions are,
- Assume the Gnu Make tool
depends on the environment variable <X>, which is set on
installation of the tool. The user does not know this and has accidently
redefined <X> to another value.
- Assume the Gnu Make depends
on some dlls from the operating system or other extensions, e.g. service
packs or .NET packages. What happens if these dll files are accidently
replaced by other versions. Does the tool recognize this, e.g. by checking
if the correct versions of expected dlls are present?
- Assume that the Gnu Make depends
on some entries to the windows registry, which are set on installation of
the tool. The user has installed other tools, e.g. other versions of the
same tool, or done something else, so that these registry values have
changed to other values.
- Assume that somebody has
accidently deleted some files from the Gnu Make installation directory, or
the installation has not completed.
- Assume that two instances
of the Gnu Make are executed on the same windows session at the same time.
Are both instances running completely independently? Is it possible that
both instances write/read data, e.g. temporary files, to/from the same
resource?
- Assume
the Gnu Make is executed in a situation where the CPU is very busy with
executing other programs. Hence, the execution of the tool gets
interrupted extremely often. Can this situation cause deviations in the
tool’s outputs?
- Assume
the Gnu Make is executed in a situation where the available RAM becomes
lower than specified in the minimal system requirements. Can this situation
cause deviations in the tool’s outputs?
Thank you for your time.
Thanks,
Chandrababu