3597N/A**

3597N/A** Set PATH = .:$(@D):/bin

3597N/A** This produces no conflict (unless /bin contains conflict!):

3597N/ACurrent working directory is "$(@D)"

3597N/A-> .

3597N/A--> /bin

3597N/A*+: conflict

3597N/A**

3597N/A** Set PATH = .:$(@D):/bin

3597N/A** This shows conflict between different filetypes

3597N/ACurrent working directory is "$(@D)"

3597N/A:----> .

3597N/A:----:----> /bin

3597N/A:co.-:--.-: conflict (.c,.o,)

3597N/A**

3597N/A** Set PATH = .:$(@D):/bin

3597N/A** This repeats the last test, with pathnames-only

3597N/A/conflict.c

3597N/A/conflict.o

3597N/A/conflict

3597N/A/bin/conflict

3597N/A**

3597N/A** Add a dummy executable in the current directory

3597N/A** /tmp/conflict.xxxxxx

3597N/A**

3597N/A** producing a conflict with the executable

3597N/A**

3597N/A** For Unix, the conflict will be in the empty suffix (first column

3597N/A** of the report). For Win32 it will be in the combination of empty

3597N/A** and "e" (.exe) suffixes.

3597N/ACurrent working directory is "/tmp/conflict.xxxxxx"

3597N/A:---> .

3597N/A:---:---> $(@D)

3597N/A:---:---:---> /bin

3597N/A:.--:.--:.--: conflict ()