In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
a user report against lang/gcc* ports that could be traced back to
a certain functionality (option) in another port (devel/binutils)
missing.
In pseudo-code this could be addressed as follows in lang/gcc*
.if $(binutils built
On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
>
> In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
> a user report against lang/gcc* ports that could be traced back to
> a certain functionality (option) in another port (devel/binutils)
> missing.
>
> In pseudo-code this c
On 2019-06-08 9:57, Adam Weinberger wrote:
On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
a user report against lang/gcc* ports that could be traced back to
a certain functionality (option) in another port (devel/binutil
On Sat, Jun 8, 2019 at 11:00 PM Mel Pilgrim
wrote:
>
> On 2019-06-08 9:57, Adam Weinberger wrote:
> > On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
> >>
> >> In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
> >> a user report against lang/gcc* ports that could be traced
Hi,
On 6/9/19 11:48 AM, Adam Weinberger wrote:
No, you're absolutely right. Flavours is the right way to do it now. I
keep forgetting about them, because I don't in any way understand how
to use them.
Hmm, flavors have to be something that can be installed in parallel,
right? How does that i
On 13/06/2019 17:00, Steve Wills wrote:
Hmm, flavors have to be something that can be installed in parallel,
right? How does that impact binutils?
They don't /have/ to be something that can be installed in parallel.
Different flavours of the same package can conflict with each other.
Look at
