Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Joerg Sonnenberger
On Mon, May 29, 2017 at 06:54:52PM +0100, Stuart Henderson wrote: > On 2017/05/29 20:26, Vadim Zhukov wrote: > > The clang and gcc behave differently regarding executing tools. > > While gcc simply runs what he said to, clang tries to be clever > > and always find absolute path for a tool,

Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Vadim Zhukov
2017-05-29 21:14 GMT+03:00 Mark Kettenis : >> From: Vadim Zhukov >> Date: Mon, 29 May 2017 20:29:20 +0300 >> >> 2017-05-29 20:26 GMT+03:00 Vadim Zhukov : >> > The clang and gcc behave differently regarding executing tools. >> >

Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Vadim Zhukov
2017-05-29 20:54 GMT+03:00 Stuart Henderson : > On 2017/05/29 20:26, Vadim Zhukov wrote: >> The clang and gcc behave differently regarding executing tools. >> While gcc simply runs what he said to, clang tries to be clever >> and always find absolute path for a tool, refusing

Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Mark Kettenis
> From: Vadim Zhukov > Date: Mon, 29 May 2017 20:29:20 +0300 > > 2017-05-29 20:26 GMT+03:00 Vadim Zhukov : > > The clang and gcc behave differently regarding executing tools. > > While gcc simply runs what he said to, clang tries to be clever > > and

Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Stuart Henderson
On 2017/05/29 20:26, Vadim Zhukov wrote: > The clang and gcc behave differently regarding executing tools. > While gcc simply runs what he said to, clang tries to be clever > and always find absolute path for a tool, refusing start otherwise. > > The actual problem is starting a linker: ports

Re: Make clang accept and use relative filenames for tools

2017-05-29 Thread Vadim Zhukov
2017-05-29 20:26 GMT+03:00 Vadim Zhukov : > The clang and gcc behave differently regarding executing tools. > While gcc simply runs what he said to, clang tries to be clever > and always find absolute path for a tool, refusing start otherwise. > > The actual problem is starting

Make clang accept and use relative filenames for tools

2017-05-29 Thread Vadim Zhukov
The clang and gcc behave differently regarding executing tools. While gcc simply runs what he said to, clang tries to be clever and always find absolute path for a tool, refusing start otherwise. The actual problem is starting a linker: ports infrastructure expects tools are called by name, not