affyPara build error
0
0
Entering edit mode
@e6d99402
Last seen 2.6 years ago
United Kingdom
  • R: 4.1.2
  • OS: ArchLinux

Code should be placed in three backticks as shown below


R CMD INSTALL git.tar.gz -l the_dir_I_want

* installing *source* package ‘affyPara’ ...
** using staged installation
** R
** byte-compile and prepare package for lazy loading
Warning message:
no DISPLAY variable so Tk is not available 
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
Warning: no DISPLAY variable so Tk is not available
Error: package or namespace load failed for ‘affyPara’:
 .onLoad failed in loadNamespace() for 'affyPara', details:
  call: assign(".affyParaInternalEnv", .affyParaInternalEnv, envir = topenv(parent.frame()))
  error: cannot add binding of '.affyParaInternalEnv' to the base environment
Error: loading failed
Execution halted
ERROR: loading failed
affyPara • 1.2k views
ADD COMMENT
0
Entering edit mode

The following discussion between OP and Henrik Bengtsson may be helpful to anyone who tries to answers this question: https://github.com/HenrikBengtsson/affxparser/issues/36

ADD REPLY
0
Entering edit mode

this is the affxparser instead of affypara

ADD REPLY
0
Entering edit mode

It is likely that you have the same underlying problem with all the different packages. You have raised similar issues with 8 different packages, but it is extremely unlikely that you have 8 completely unrelated issues.

ADD REPLY
0
Entering edit mode

why not? so strange answers. Different packages with different problems, no upstream, I compile almost all bioocnductors packages, I can't find almost all upstream I should report to. That's not my problem.

ADD REPLY
0
Entering edit mode

A different but similar point to what Gordon made is that there is a build report that you can look at, and if you were to do so, you would see that pretty much all of the packages you are complaining about are not building. It is very likely that there is one (maybe two) package(s) that are dependencies for all these packages that won't build, and a problem with the dependency is propagating to all these other packages.

Rather than spamming the support site with 8 different posts, you could just say 'hey, I have like 8 packages that will not build for various reasons', and here's my sessionInfo.

ADD REPLY
0
Entering edit mode

okay, thanks, I don't have experience, when I report GitHub issues, for different reason, I need to open different issues.

ADD REPLY

Login before adding your answer.

Traffic: 1011 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6