Re: cmake + WRKOBJDIR

[Roland Illig <roland.illig%gmx.de@localhost>]

On 15.08.2020 04:06, Brook Milligan wrote:
>
>> On Aug 14, 2020, at 7:57 PM, Roland Illig <roland.illig%gmx.de@localhost> wrote:
>>
>> On 14.08.2020 17:43, Brook Milligan wrote:
>>> Building cmake failed for me with WRKOBJDIR=/private/tmp/pkgsrc on a Mac (Catalina).
>>>
>>> Even though WRKOBJDIR points to a directory, cmake reports the following during the bootstrap/configure step:
>>>
>>> -- Check for working C compiler: /tmp/pkgsrc/devel/cmake/work/.cwrapper/bin/clang - skipped
>>>
>>> On this system /tmp is a symlink for /private/tmp, so cmake seems to be somehow reverting to the symlink.  I do not understand the cmake magic enough to see where this is happening.  Any ideas?
>>
>> pkgsrc does not support symlinks for PREFIX, WRKOBJDIR and a few other
>> directories, exactly because of problems like these.
>
> But none of those are symlinks in this case.  WRKOBJDIR is the full path to a directory (/private/tmp/pkgsrc) but the cmake magic reverts to using /tmp/pkgsrc instead, where tmp -> /private/tmp.
>
> The question is, why does it do that and how can it be fixed.

grep -r /tmp/pkgsrc $PREFIX

I suspect there's some package that still contains a reference to the
symlink.  Candidates are libtool-base or any other compiler wrapper.

If there is no reference to /tmp/pkgsrc anywhere, I'm out of guesses.
In that case, you probably need to track the problem down using the
macOS equivalent of ktrace, strace, truss.