ppl has gcc variants but gcc45+ depend on ppl

[mf2k (Frank Schima)]

Not sure how this happened, but gcc45 and ppl +gcc45 both depend on each other and cannot be built. Seems related to ticket:33151 and r91016. This is especially troubling for me because I use +gcc45 as a default variant.

[adfernandes (Andrew Fernandes)]

If anyone needs to change ppl, cloog, or cloog-ppl to fix this, please go ahead; I'm very busy with non-macports things and won't be able to touch this for at least a couple of weeks.

Note that there is an outstanding ticket to upgrade ppl (#33635) that, if someone wants to tackle as part of this, I'd be very appreciative!

[ryandesign (Ryan Carsten Schmidt)]

ppl only depends on a gcc port if you request one of its gcc variants. By default ppl does not require a gcc port.

Why does ppl provide variants to use a gcc port as its compiler? What benefit does this achieve?

According to "port echo depends::ppl$" the only ports that depend on ppl are gcc45 and up, and cloog-ppl; as such it seems ill-advised to allow ppl to depend on a gcc port, since as Frank points out that introduces a circular dependency.

I don't see any relationship between this problem and #33151, except that in a sidetracked comment in that ticket someone pointed out that gcc45 was not using ppl, and I therefore added the dependency to gcc45 and gcc47 in r91016, since gcc46 already had it (and gcc48 was subsequently copied from gcc47 so it has it too).

[mf2k (Frank Schima)]

I removed the gcc45 and gcc46 variants of ppl in r91316.

[ryandesign (Ryan Carsten Schmidt)]

Thank you, but that still leaves the gcc43 and gcc44 variants, and I'm still curious about their purpose. Why would anybody want to build ppl with gcc43 or gcc44 when it builds fine with the standard Xcode compiler?