Fink won't install clang 3.5.x due to dpkg bad consider

[commandcontrolQ]

When trying to install clang35 (and its dependencies), for some unknown reason Fink always complains about unresolved dependencies with one package: (isl/isl2).

This issue appears to be coming from both Fink and dpkg:

• Fink will always state one version of isl as a dependency if the other is installed
• dpkg when considering replacing isl with isl2 (or vice versa) will always replace
• Fink clearly does not like this at all and errors out

Steps to reproduce:

1. On a system without clang 3.5.x, run fink install clang35

What should happen:

• Fink will install clang 3.5.x's dependencies

What does happen

• dpkg will either install isl over isl2 or install isl2 over isl and Fink will complain that dependencies could not be resolved.

[dmacks]

I've seen that happen when a package has simultaneous dependencies on two mutually exclusive packages (as you see, isl and isl2 cannot both be installed simultaneously). The final test before the actual build then fails because whatever fink and dpkg did wound up not accomplishing what the package wanted. That's a packaging mistake.

I've also seen it when fink is trying to build a huge set of packages at once, and can't figure out where to start. That's resolveable by manually building the first few packages directly rather than jumping to the top of a huge tree and having it run the whole thing.

However....

I don't see clang35 on my local fink (only clang37, clang39, clang50). I'm on 10.13, so maybe you're on a different platform that has this package? According to the git logs, the clangXX at version 3.5 and prior were nuked in 2015 on all platforms that fink supported at that time. Maybe in the time since then, the isl packages have been re-shuffled, or a bug that existed back then has been fixed but you're only seeing the older packages for some reason.

If we don't have the package, I don't see an easy way to debug it. And it's possible it got nuked because it became unsupportable for this or any of various other reasons. Are you using a very old OS X?

[commandcontrolQ]

Precisely - I am running MacOS X Snow Leopard (for personal reasons I am choosing not to upgrade) and the "latest" version of clang available to me is 3.5.