We have noticed that qcc doesn't seem to work correctly when the path name includes an @ in it. For example:

[q65]rchung@randolph-pc:/tmp/test$ ls *
t:
foo.c

t@1:
foo.c

[q65]rchung@randolph-pc:/tmp/test$ qcc -v -c t/foo.c
cc: looking for gcc_ntox86 in /opt/qnx650/host/linux/x86/etc/qcc/gcc/4.4.2/gcc_ntox86++.conf
cc: looking for gcc_ntox86 in /opt/qnx650/host/linux/x86/etc/qcc/gcc/4.4.2/gcc_ntox86.conf
/opt/qnx650/host/linux/x86/usr/lib/gcc/i486-pc-nto-qnx6.5.0/4.4.2/cc1 -quiet -nostdinc -D__LANGUAGE_C -D_LANGUAGE_C -
D__QNX__ -D__QNXNTO__ -D__GNUC__=4 -D__GNUC_MINOR__=4 -D__GNUC_PATCHLEVEL__=2 -D__unix__ -D__unix -D__ELF__ -D__X86__ -
D__i386__ -D__LITTLEENDIAN__ -isystem /opt/qnx650/target/qnx6/usr/include -isystem /opt/qnx650/host/linux/x86/usr/lib/
gcc/i486-pc-nto-qnx6.5.0/4.4.2/include t/foo.c -dumpbase t/foo.c -o - | \
 /opt/qnx650/host/linux/x86/usr/bin/ntox86-as -o foo.o

[q65]rchung@randolph-pc:/tmp/test$ qcc -v -c t@1/foo.c
cc: looking for gcc_ntox86 in /opt/qnx650/host/linux/x86/etc/qcc/gcc/4.4.2/gcc_ntox86++.conf
cc: looking for gcc_ntox86 in /opt/qnx650/host/linux/x86/etc/qcc/gcc/4.4.2/gcc_ntox86.conf

It looks like qcc parses the path name somehow and the @ confuses it. Is there a way to make qcc work in this 
environment?