[Bioc-devel] iGraph depending packages failing on Windows build machines

[Obenchain, Valerie]

Petr,

Yesterday I installed R 3.5.0 beta on the devel Windows builder (tokay2). The report has not posted yet but I checked on the build of PharmacoGx and it is clean.

It looks like the CRAN 'maps' package was updated on April 4. It's possible that during the nightly builds, the new version of 'maps' was installed for x64 arch only. The build system uses update.packages() to update CRAN dependencies. update.packages() may have picked up the source package because the Windows binary for the new version was not available yet which resulted in a x64-only installation of 'maps'.

We'll look into modifying in the build system code to handle this situation better. Thanks again for reporting it.

Valerie


On 04/10/2018 04:44 PM, petr smirnov wrote:

I noticed that our Bioconductor package (PharmacoGx) is failing to build on
Windows development, with the error:

 error: DLL 'maps' not found: maybe not installed for this architecture?

A google search brings up the package 'sincell', which has experienced this
error before.

The only dependency that package has is iGraph (CRAN), which we share with
them. Checking some of the build reports, there's a handful of packages
failing with the same issue.

There is also at least one package, 'Mulcom', that is failing with the
error:

Error : package 'maps' is not installed for 'arch = i386'

The CRAN package 'maps' seems to be the one providing the 'maps.dll' file.
There seems to be a successful binary build of the 'maps' package on CRAN
for both the release and prerelease versions of R.

Is this is an issue with the package 'maps' not being successfully
installed on the Windows build system?





This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
	[[alternative HTML version deleted]]