Hello Hervé,
Thanks for confirming what I was thinking. Does anyone know how long it
should take for win-builder to use the updated Rhtslib version? I just
tried it again today, and it's still using the older version.
Cheers,
Lucas
On Sun, Feb 2, 2020 at 11:34 PM Hervé Pagès wrote:
> To me it
Thanks everyone for your help. It's still giving me the same error on the
development win-builder and on AppVeyor. Truncated install logs for both
are below. I'm not sure that Rhtslib 1.91.1 (the one with the new changes)
is being used on win-builder, which is why I've included the AppVeyor
results
On 27/01/2020 5:48 p.m., Martin Morgan wrote:
what are the correct paths?
The src/gnuwin32/MkRules.dist file gives the patterns. They are based
on environment variables LOCAL_SOFT, R_HOME, etc. Most people should
modify that file to MkRules.local when building R; the variables defined
the
what are the correct paths?
On 1/27/20, 3:32 PM, "R-package-devel on behalf of Uwe Ligges"
wrote:
Thanks, one suspicious part from the log below is
-LC:/extsoft/lib/i386
which is clearly not in any variable we define on CRAN.
Looking close shows that
> Rhtsl
Thanks, one suspicious part from the log below is
-LC:/extsoft/lib/i386
which is clearly not in any variable we define on CRAN.
Looking close shows that
> Rhtslib::pkgconfig("PKG_LIBS")
gives
'D:/RCompile/CRANpkg/lib/4.0/Rhtslib/usrlib/x64/libhts.a'
-LC:/extsoft/lib/x64 -lcurl -lrtmp -lssl -