On Wed, Jul 1, 2020 at 9:36 AM Michael Orlitzky wrote:
>
> On 2020-06-30 12:22, Matthew Thode wrote:
> >
> > I'd like to suggest allowing only approved variables in the build
> > environment, having portage unset all variables and setting only what is
> > needed (or configured).
>
> I think this i
On 2020-06-30 12:22, Matthew Thode wrote:
>
> I'd like to suggest allowing only approved variables in the build
> environment, having portage unset all variables and setting only what is
> needed (or configured).
I think this is orthogonal to the problem I'm trying to solve. Even if
all environme
On 20-06-28 08:18:23, Michael Orlitzky wrote:
> As many of you probably know, ago@ has been expanding the scope of our
> CFLAGS/CC support to include some other common build variables:
>
> * CC
> * CXX
> * AR
> * CPP
> * NM
> * RANLIB
> * AS
> * LD
>
> Some of those are POSIX stan
On Sun, Jun 28, 2020 at 8:18 AM Michael Orlitzky wrote:
>
> As many of you probably know, ago@ has been expanding the scope of our
> CFLAGS/CC support to include some other common build variables:
>
> * CC
> * CXX
> * AR
> * CPP
> * NM
> * RANLIB
> * AS
> * LD
>
> Some of those are
On Sun, 28 Jun 2020 08:18:23 -0400
Michael Orlitzky wrote:
> With LD set to something libtooly in the
> environment, the pari build fails. We can solve that by unsetting LD in
> the ebuild, but for that to be The Right Thing To Do, we should be
> expecting LD to contain something libtooly, and th
As many of you probably know, ago@ has been expanding the scope of our
CFLAGS/CC support to include some other common build variables:
* CC
* CXX
* AR
* CPP
* NM
* RANLIB
* AS
* LD
Some of those are POSIX standards[0],
* CC
* AR
Others are de-facto GNU make standards[1],
