Oh, sorry, I didn't read the question in detail about how -save-temps
was making things work when they otherwise were not.
If you run clang with -### it'll show the command lines it's using,
which should show you where it's trying to write the files so you can
change that/make them writable. I'm n
Thanks Fang-rui.
I still haven't been able to fix the issue, I still use --save-temps, and
that makes linking very slow.
Why does this error go away when I set --save-temps, any idea??
On Thu, Aug 13, 2020 at 7:16 PM Fāng-ruì Sòng wrote:
> On Thu, Aug 13, 2020 at 8:59 AM David Blaikie wrote:
On Thu, Aug 13, 2020 at 8:59 AM David Blaikie wrote:
>
> On Thu, Aug 13, 2020 at 2:59 AM Danijel DOMAZET
> wrote:
> >
> > Thanks David.
> > Why do you think this could be about current dir?
> > Isn't it about TMP (or TEMP or TMPDIR) environment variables?
Neither the driver option -save-temps no
On Thu, Aug 13, 2020 at 2:59 AM Danijel DOMAZET
wrote:
>
> Thanks David.
> Why do you think this could be about current dir?
> Isn't it about TMP (or TEMP or TMPDIR) environment variables?
Because I ran it locally, and observed that that's where the files
were written to.
>
> Thanks,
> Danijel D
Thanks David.
Why do you think this could be about current dir?
Isn't it about TMP (or TEMP or TMPDIR) environment variables?
Thanks,
Danijel Domazet
On Thu, Aug 13, 2020 at 12:11 AM David Blaikie wrote:
> Looks like it writes the files to the current directory - do you have
> permission to ac
