On 2016-Nov-25, at 11:47 PM, Gerald Pfeifer <gerald at pfeifer.com> wrote:
> On Fri, 25 Nov 2016, Mark Millard wrote: >> I wonder if that leaves lang/gcc and lang/gcc49 as conflicting. > > Yes, these two ports conflict for the time being, and are properly > marked as such. > > (And I am looking for a more elegant approach going forward, in > particular when we move into GCC 5 territory where, based on input > from Tijl and others, we now distinguish between lang/gcc5 and > lang/gcc5-devel.) That explains why I've only had lang/gcc5 vs. devel/powerpc64-gcc conflicts at times: devel/powerpc64-gcc is not treated as a 3rd alternative to lang/gcc5-devel and lang/gcc5 and it overlaps with lang/gcc5 when the .x part of the versions (of .x.y) happen to be the same. [Long ago it was devel/powerpc64-gcc and lang/gcc49 conflicts.] devel/powerpc64-gcc is currently a gcc5 variant. I actually install and use devel/powerpc64-xtoolchain-gcc and its devel/powerpc64-gcc on the powerpc64 contexts that I have. (This requires a staging-failure workaround.) I learned to avoid having lang/gcc5 (in more modern times). Sounds like I could have lang/gcc5-devel without conflicts. I use devel/powerpc64-gcc for "self hosted cross builds" in order to have a modern libc++ based powerpc64 environment without requiring actual cross builds. [I've never gotten lib32 to work under this technique so I build without it.] >> But luckily so far I've not picked to build anything that built >> lang/gcc. Or, more likely(?), if some gcc is already installed it >> is used instead if lang/gcc is not installed yet. > > Correct. If lang/gcc49 or lang/gcc is installed, either of the > two is picked up; if a newer version is installed and USE_GCC=yes > or USE_GCC=X.Y+ are requested (and the installed version is newer), > that one is used. > > Nothing to do with luck on your side, Mark. Rather, design and > implementation in the Ports Collection. :-) > > Gerald === Mark Millard markmi at dsl-only.net _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
