[macports-ports] branch master updated: ffmpeg: force gcc6 on PPC
Ryan Schmidt
ryandesign at macports.org
Sat Oct 21 02:08:02 UTC 2017
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:
>
> new e1f1b6b ffmpeg: force gcc6 on PPC
>
> e1f1b6b is described below
>
>
> commit e1f1b6b20678fed08e81f8a65ea0062f59a1f64c
>
> Author: Ken Cunningham <kencu at macports.org>
> AuthorDate: Fri Oct 20 18:49:11 2017 -0700
>
> ffmpeg: force gcc6 on PPC
>
> closes: https://trac.macports.org/ticket/55124
>
> ---
> multimedia/ffmpeg/Portfile | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/multimedia/ffmpeg/Portfile b/multimedia/ffmpeg/Portfile
> index bdc0919..61ec6e3 100644
> --- a/multimedia/ffmpeg/Portfile
> +++ b/multimedia/ffmpeg/Portfile
> @@ -106,6 +106,14 @@ if {[lsearch [get_canonical_archs] i386] != -1} {
> compiler.blacklist-append {clang < 422.1.7}
> }
>
> +platform darwin powerpc {
> + # https://trac.macports.org/ticket/55124
> + # requires newer compiler than gcc4.2 to build
> + compiler.blacklist
> + compiler.whitelist macports-gcc-6
> + universal_variant no
> +}
Is there a specific reason why you did it this way, instead of what we usually do, which is to blacklist the compilers that don't work and let MacPorts choose the next-best alternative? I know gcc* isn't in the list of compilers MacPorts will fall back to. Do we maybe just need to add gcc6 to the fallback list on PowerPC?
More information about the macports-dev
mailing list