Re: [cfe-users] Compiling on network share using relative paths fails

2020-09-10 Thread Jan Korous via cfe-users
[mailto:dblai...@gmail.com] > Sent: Thursday, September 10, 2020 1:06 PM > To: Telium Technical Support > Cc: via cfe-users > Subject: Re: [cfe-users] Compiling on network share using relative paths fails > > Can you confirm other tools given similar path specifications in si

Re: [cfe-users] Compiling on network share using relative paths fails

2020-09-10 Thread Telium Technical Support via cfe-users
: Re: [cfe-users] Compiling on network share using relative paths fails Can you confirm other tools given similar path specifications in similar circumstances (command line/current working directory/etc) succeed where clang fails? (MSVC, notepad, gcc, 'cat' (if Windows has a 'ca

Re: [cfe-users] Compiling on network share using relative paths fails

2020-09-10 Thread David Blaikie via cfe-users
Can you confirm other tools given similar path specifications in similar circumstances (command line/current working directory/etc) succeed where clang fails? (MSVC, notepad, gcc, 'cat' (if Windows has a 'cat')) On Wed, Sep 9, 2020 at 10:41 AM Telium Technical Support via cfe-users < cfe-users@lis

[cfe-users] Compiling on network share using relative paths fails

2020-09-09 Thread Telium Technical Support via cfe-users
I think this is a bug.but it's so big that I can't believe I'm the first person to find it. Perhaps someone can help me find a workaround. I discovered that clang++ will not find a source file if it is located on a network share (if using a relative path). For example, I have place the same fi