Re: BLAS in pkgsrc: present and future

To: Jason Bacon <outpaddling%yahoo.com@localhost>
Subject: Re: BLAS in pkgsrc: present and future
From: "Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>
Date: Thu, 18 Apr 2019 08:57:57 +0200

Am Wed, 17 Apr 2019 13:28:12 -0500
schrieb Jason Bacon <outpaddling%yahoo.com@localhost>: 

> As currently configured, one must include
> 
> .include "../../wip/mk/blas.buildlink3.mk"
> .include "../../wip/cblas/buildlink3.mk"
> 
> Is there a clear purpose behind the current cblas implementation, or 
> have you not gotten around to refining it yet?

Hm, I suppose that's a bug. Cblas is supposed to pull in blas, just
like direct inclusion would.


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg

References:
- BLAS in pkgsrc: present and future
  - From: Dr. Thomas Orgis
- Re: BLAS in pkgsrc: present and future
  - From: Greg Troxel
- Re: BLAS in pkgsrc: present and future
  - From: Dr. Thomas Orgis
- Re: BLAS in pkgsrc: present and future
  - From: Jason Bacon

Prev by Date: daily pkgsrc CVS update output
Next by Date: pkgsrc namespaces (was: BLAS in pkgsrc: present and future)
Previous by Thread: Re: BLAS in pkgsrc: present and future
Next by Thread: Re: BLAS in pkgsrc: present and future
Indexes:

Home | Main Index | Thread Index | Old Index