Hi Ryan, You can easily see the issue with
> sudo port -d select llvm mp-llvm-13 the linkage starts out in sync, but then starts to diverge.. <snip> DEBUG: ln -sf /opt/local/bin/llvm-symbolizer-mp-13 /opt/local/bin/llvm-symbolizer DEBUG: rm -f /opt/local/bin/llvm-tblgen DEBUG: rm -f /opt/local/bin/llvmc DEBUG: ln -sf /opt/local/bin/opt-mp-13 /opt/local/bin/macho-dump DEBUG: ln -sf /opt/local/bin/llvm-tblgen-mp-13 /opt/local/bin/opt <snip> I tried applying the patch as supplied, and then reran port select, but it didn't’ make any difference. I confess I am not that familiar with how the port select mechanism works - does the port need to be rev-bump in order to get rebuilt with the patch (which would be a bit of a pain) ? cheers Chris > On 14 Mar 2022, at 6:06 pm, Ryan Schmidt <[email protected]> wrote: > > > > On Mar 14, 2022, at 00:28, 조성빈 wrote: > >> Hello, >> >> I’m not sure who to CC so just sending it to the dev list: >> >> it seems that the mp-llvm-* select groups of the llvm-12, llvm-13 (and >> possibly >> more?) ports mislink certain programs. > > Could you describe exactly what is mislinked? > > >> I think adding a line over opt-mp-* will >> fix the bug, but I’m not an expert on these ports. > > Could be. If so, the revision would need to be increased as well. > > >> Thanks. >> >> <0001-llvm-fix-broken-mp-llvm-groups.patch> >
smime.p7s
Description: S/MIME cryptographic signature
