Michael Forney <mforney%mforney.org@localhost> writes: > I've been able to work around this problem by adding > > .include "../../devel/libexecinfo/buildlink3.mk" > > to lang/llvm/Makefile. Is this the right solution or is there some way > to prevent cmake from detecting the pkgsrc libexecinfo? 1) One option is to do that, but given that libexecinfo seems builtin normally, there needs to be builtin.mk support so that the native version is used when present. I haven't looked in this case, but this pattern is common in pkgsrc. 2) Another approach is to find out why libexecinfo is in the buildlink tree; it seems that cmake as a tool shouldn't be pulling in things like that. 3) A third approach is to patch the llvm build to not ind it, but I suspect it is better for llvm to have it, not to turn it off. It doesn't seem good to turn it off elsewhere, and it doesn't seem good to have it be different. So I would look into 1, and separately see if there is a bug as described in 2.
Attachment:
signature.asc
Description: PGP signature