Re: circular dependency when using a seperately-built gcc

To: pkgsrc-Users%netbsd.org@localhost
Subject: Re: circular dependency when using a seperately-built gcc
From: Edgar Fuß <ef%math.uni-bonn.de@localhost>
Date: Fri, 2 Sep 2022 19:58:27 +0200

> Am 02.09.2022 um It might not be the problem, but you really don't want to have your separate compiler be under LOCALBASE, there's a possibility it will cause issues with the wrapper rewrites and be invisible via buildlink.
What‘s the way it‘s supposed to work if I use pkgsrc with FooBarIX which has an old gcc in /usr/bin I want to avoid and a newer one in /opt/expensive/gcc6 that I want to use?

Follow-Ups:
- Re: circular dependency when using a seperately-built gcc
  - From: Jonathan Perkin

References:
- Re: circular dependency when using a seperately-built gcc
  - From: Jonathan Perkin

Prev by Date: Re: circular dependency when using a seperately-built gcc
Next by Date: Re: circular dependency when using a seperately-built gcc
Previous by Thread: Re: circular dependency when using a seperately-built gcc
Next by Thread: Re: circular dependency when using a seperately-built gcc
Indexes:

Home | Main Index | Thread Index | Old Index