> Dirk Eddelbuettel
> on Thu, 5 Sep 2019 10:14:21 -0500 writes:
> On 5 September 2019 at 16:53, Ralf Stubner wrote:
> | I don't know what is best, but here are three alternatives:
> |
> | * Use PKG_CHECK_MODULES which sets up default variables with _CFLAGS
> | and
On 5 September 2019 at 16:53, Ralf Stubner wrote:
| I don't know what is best, but here are three alternatives:
|
| * Use PKG_CHECK_MODULES which sets up default variables with _CFLAGS
| and _LIBS suffix after searching for a library with pkg-config, c.f.
| https://autotools.io/pkgconfig/pkg_che
On Thu, Sep 5, 2019 at 12:27 PM Martin Maechler
wrote:
> Now what is the officially / best way to have either 'configure'
> or Makevars.{in,win} use the 'pkg-config' information
> *dynamically*, i.e.,
> if I update my MPFR from 4.0.1 to 4.0.2 the newer 4.0.2 is found ?
I don't know what is be
On 05/09/2019 12:26, Martin Maechler wrote:
Sameh M Abdulah
on Fri, 30 Aug 2019 18:50:55 + writes:
> Hi,
> I recently asked some questions about my R package which were well
responded by Dirk.
> I have another question related to pkg_config path,
> I am using thi
On 3 September 2019 at 15:37, Tomas Kalibera wrote:
| Yes, that seems to be an upstream problem.
Maybe checking with the documentation for Armadillo documentation at
http://arma.sourceforge.net/docs.html (large page, see about the various
#define in config.hpp near the bottom) could be of help.
> Sameh M Abdulah
> on Fri, 30 Aug 2019 18:50:55 + writes:
> Hi,
> I recently asked some questions about my R package which were well
responded by Dirk.
> I have another question related to pkg_config path,
> I am using this command to add the installation path