Re: [macports-ports] branch master updated: ffmpeg: force gcc6 on PPC

> > > The issue in doing that is that C++ ports will possibly be build > inconsistently because macports-gcc6 will use the MacPorts-provided runtimes > from libgcc which are not compatible with the host's libstdc++ (used by > gcc42). > > If you want to use gcc6 for a full build of MacPorts

Re: [macports-ports] branch master updated: ffmpeg: force gcc6 on PPC

> On Oct 20, 2017, at 20:32, Ken Cunningham > wrote: > > > >> On Oct 20, 2017, at 7:39 PM, Ryan Schmidt wrote: >> >> I guess my question was: is there something unique about ffmpeg that makes >> it require gcc6 on PowerPC, as

Re: [macports-ports] branch master updated: ffmpeg: force gcc6 on PPC

> On Oct 20, 2017, at 7:39 PM, Ryan Schmidt wrote: > > I guess my question was: is there something unique about ffmpeg that makes it > require gcc6 on PowerPC, as opposed to one of the alternatives MacPorts would > choose, or is MacPorts choosing inappropriate

Re: [macports-ports] branch master updated: ffmpeg: force gcc6 on PPC

The fallbacks on PPC don't work correctly, I find. If I were to blacklist gcc42, MacPorts would lead in almost all cases to building it with clang-3.4, which always fails. Also, there's no point falling back to any gcc prior to gcc6. So what I saw as options was to blacklist: all the gcc

Re: [macports-ports] branch master updated: ffmpeg: force gcc6 on PPC

On Oct 20, 2017, at 20:49, Ken wrote: > Ken (kencu) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/e1f1b6b20678fed08e81f8a65ea0062f59a1f64c > > The following commit(s) were added to refs/heads/master by this push: > >