Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation error: Endless loop of "Enter y or n, or enter q to quit" #209

Closed
tyleransom opened this issue Jul 5, 2019 · 3 comments
Closed
Labels
reprex needs a minimal reproducible example

Comments

@tyleransom
Copy link

tyleransom commented Jul 5, 2019

I am trying to install fs on Linux x86_64 using the basic install.packages('fs') syntax from the cloud.r-project.org mirror.

Installation appears to go fine until I'm met with an endless loop of

Enter y or n, or enter q to quit:

Does anyone know what might be the issue? I've never encountered this before when installing any other package. Any help would be greatly appreciated!

I can't tell after which compilation line the error begins, because I'm not quick enough to hit ^C and it quickly overflows my terminal.

Below is my sessionInfo() output:

>  sessionInfo()
R version 3.4.2 (2017-09-28)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Red Hat Enterprise Linux Server 7.6 (Maipo)

Matrix products: default
BLAS: /usr/lib64/libblas.so.3.4.2
LAPACK: /usr/lib64/liblapack.so.3.4.2

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
 [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

loaded via a namespace (and not attached):
[1] compiler_3.4.2 tools_3.4.2

as well as the output of R CMD config --all:

CC = gcc -std=gnu99
CFLAGS = -g -O2
CPICFLAGS = -fpic
CPP = gcc -std=gnu99 -E
CPPFLAGS = -I/usr/local/include
CXX = g++
CXXCPP = g++ -E
CXXFLAGS = -g -O2
CXXPICFLAGS = -fpic
CXX11 = g++
CXX11STD = -std=gnu++11
CXX11FLAGS = -g -O2
CXX11PICFLAGS = -fpic
CXX14 =
CXX14STD =
CXX14FLAGS =
CXX14PICFLAGS =
CXX98 = g++
CXX98STD =
CXX98FLAGS = -g -O2
CXX98PICFLAGS = -fpic
CXX17 =
CXX17STD =
CXX17FLAGS =
CXX17PICFLAGS =
CXX1X = g++
CXX1XSTD = -std=gnu++11
CXX1XFLAGS = -g -O2
CXX1XPICFLAGS = -fpic
DYLIB_EXT = .so
DYLIB_LD = gcc -std=gnu99
DYLIB_LDFLAGS = -shared -fopenmp
F77 = gfortran
FFLAGS = -g -O2
FPICFLAGS = -fpic
FLIBS = -lgfortran -lm -lquadmath
SAFE_FFLAGS = -g -O2 -ffloat-store
FC = gfortran
FCFLAGS = -g -O2
FCPICFLAGS = -fpic
OBJC =
OBJCFLAGS =
JAVA = /opt/apps/rhel7/jdk1.8.0_60/bin/java
JAVAC = /opt/apps/rhel7/jdk1.8.0_60/bin/javac
JAVAH = /opt/apps/rhel7/jdk1.8.0_60/bin/javah
JAR = /opt/apps/rhel7/jdk1.8.0_60/bin/jar
JAVA_HOME = /hpchome/apps/rhel7/jdk1.8.0_60/jre
JAVA_LIBS = -L/hpchome/apps/rhel7/jdk1.8.0_60/jre/lib/amd64/server -ljvm
JAVA_CPPFLAGS = -I/hpchome/apps/rhel7/jdk1.8.0_60/jre/../include -I/hpchome/apps/rhel7/jdk1.8.0_60/jre/../include/linux
LDFLAGS = -L/usr/local/lib64
SHLIB_CFLAGS =
SHLIB_CXXLD = g++
SHLIB_CXXLDFLAGS = -shared
SHLIB_CXX98LD = g++
SHLIB_CXX98LDFLAGS = -shared
SHLIB_CXX11LD = g++ -std=gnu++11
SHLIB_CXX11LDFLAGS = -shared
SHLIB_CXX14LD =
SHLIB_CXX14LDFLAGS = -shared
SHLIB_CXX17LD =
SHLIB_CXX17LDFLAGS = -shared
SHLIB_EXT = .so
SHLIB_FFLAGS =
SHLIB_LD = gcc -std=gnu99
SHLIB_LDFLAGS = -shared
SHLIB_FCLD = gfortran
SHLIB_FCLDFLAGS = -shared
SHLIB_CXX1XLD = g++ -std=gnu++11
SHLIB_CXX1XLDFLAGS = -shared
TCLTK_CPPFLAGS = -I/usr/include -I/usr/include
TCLTK_LIBS = -L/usr/lib64 -ltcl8.5 -L/usr/lib64 -ltk8.5 -lX11
BLAS_LIBS = -lblas
LAPACK_LIBS = -llapack
MAKE = make
LIBnn = lib64
LOCAL_SOFT =
COMPILED_BY =
@jimhester
Copy link
Member

I don't believe this has anything to do with fs in particular, we certainly are not prompting the user for anything during installation.

You could use screen or tmux to provide a larger navigable terminal buffer which maybe would provide more context, there unfortunately is not enough here for us to do anything actionable.

@jimhester jimhester added the reprex needs a minimal reproducible example label Jul 27, 2019
@rjkimble
Copy link

rjkimble commented Nov 8, 2019

I ran into this exact problem. The problem turned out to be a file named "install" in our Stata 16 directory, which unfortunately was the first directory in our path. Once I removed the directory from the path, the installation proceeded without a problem.

@davidjiyangcai
Copy link

thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reprex needs a minimal reproducible example
Projects
None yet
Development

No branches or pull requests

4 participants