Re: pkg requires gcc44 or later, but won't use existing gcc46?

To: "John D. Baker" <jdbaker%mylinuxisp.com@localhost>
Subject: Re: pkg requires gcc44 or later, but won't use existing gcc46?
From: Greg Troxel <gdt%ir.bbn.com@localhost>
Date: Mon, 24 Mar 2014 15:47:03 -0400

"John D. Baker" <jdbaker%mylinuxisp.com@localhost> writes:

> On Mon, 24 Mar 2014, Jonathan Perkin wrote:
>
>> This is wrong, and is fixed in pkgsrc trunk.  GCC_REQD should be
>> appended to, not set.  Setting it means that any newer versions are
>> ignored, hence pulling in gcc44 regardless of having 4.6 installed.
>
> Yes.  I misquoted the Makefile.  It does have "GCC_REQD+=4.4" as you
> say.  Nevertheless, the behavior is as I described and the already-
> installed gcc46 is ignored in favor building gcc44.  I am using pkgsrc
> from HEAD.

Is GCC_REQD supposed to have the semantics of "or newer", or an exact
match?  If exact, is there a syntax for expressing a set, any of which
are acceptable?

What happens if one uses clang?

Attachment: pgpRfGPAgMU_k.pgp
Description: PGP signature

References:
- pkg requires gcc44 or later, but won't use existing gcc46?
  - From: John D. Baker
- Re: pkg requires gcc44 or later, but won't use existing gcc46?
  - From: Richard PALO
- Re: pkg requires gcc44 or later, but won't use existing gcc46?
  - From: John D. Baker
- Re: pkg requires gcc44 or later, but won't use existing gcc46?
  - From: Jonathan Perkin
- Re: pkg requires gcc44 or later, but won't use existing gcc46?
  - From: John D. Baker

Prev by Date: Re: pkg requires gcc44 or later, but won't use existing gcc46?
Next by Date: Re: pkg requires gcc44 or later, but won't use existing gcc46?
Previous by Thread: Re: pkg requires gcc44 or later, but won't use existing gcc46?
Next by Thread: Re: pkg requires gcc44 or later, but won't use existing gcc46?
Indexes:

Home | Main Index | Thread Index | Old Index