passing default variants to dependencies?

Joshua Root jmr at macports.org
Sun Nov 16 14:17:06 PST 2014


Asking to ensure that your dependencies have certain variants applied is
depending on variants. Restricting it to variants that the dependent
port has itself doesn't change the fundamental issues.

- Josh

On 2014-11-17 09:05 , David Strubbe wrote:
> Thanks for the comments. I'm not trying to depend on a variant, and I am
> already using active_variants (that is what blocks fftw-3 without a
> Fortran variant). I just wonder why default variants are not passed to
> dependencies (because other variants do seem to be passed to
> dependencies) and whether there is some way to get around this.
> 
> David
> 
> On Sun, Nov 16, 2014 at 5:01 PM, Joshua Root <jmr at macports.org
> <mailto:jmr at macports.org>> wrote:
> 
>     On 2014-11-17 08:52 , David Strubbe wrote:
>     > Hi all,
>     >
>     > Is there a way to make default variants be passed to dependencies when
>     > installing them? My octopus port depends on fftw-3 and needs it to be
>     > built with a Fortran variant. octopus has +gcc48 as default
>     variant, and
>     > building fftw-3 +gcc48 will work. But on the buildbots it just builds
>     > fftw-3 with no variant for the dependency, which then does not
>     work. How
>     > can I solve this?
>     >
>     > Thanks,
>     > David
> 
>     No, you can't depend on a variant. This isn't buildbot-specific; anyone
>     running 'port install octopus' from a fresh installation will see the
>     same result.
> 
>     - Josh



More information about the macports-dev mailing list