I download the http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.51-x86-64-linux-binary.tar.bz2 and install in SUSE 10 x86-64. But when run sbcl it error say: floating point exception
and http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.51-x86-linux-binary.tar.bz2 is the same error.
should I compile sbcl from source?
Related
This is the error that shows up when I try to run "pip install PySide" on my Jetson Nano. Can someone please let me know how I can fix this error?
CMake Warning at /usr/share/cmake-3.10/Modules/FindQt4.cmake:620 (message):
/usr/bin/qmake reported QT_INSTALL_LIBS as "/usr/lib/aarch64-linux-gnu" but
QtCore could not be found there. Qt is NOT installed correctly for the
target build environment.
Call Stack (most recent call first):
CMakeLists.txt:9 (find_package)
-- Found PythonLibs: /usr/lib/aarch64-linux-gnu/libpython2.7.so (found suitable version "2.7.17", minimum required is "2.6")
-- Found LibXml2: /usr/lib/aarch64-linux-gnu/libxml2.so (found suitable version "2.9.4", minimum required is "2.6.32")
-- Could NOT find LibXslt (missing: LIBXSLT_LIBRARIES LIBXSLT_INCLUDE_DIR) (Required is at least version "1.1.19")
Qt QTGUI library not found.
Qt QTXML library not found.
Qt QTCORE library not found.
CMake Error at ApiExtractor/CMakeLists.txt:82 (qt4_add_resources):
Unknown CMake command "qt4_add_resources".
-- Configuring incomplete, errors occurred!
See also "/tmp/pip-build-mimaL7/PySide/pyside_build/py2.7-qt4.8.7-64bit-release/shiboken/CMakeFiles/CMakeOutput.log".
error: Error configuring shiboken
PySide does not have official release package for ARM systems. You have to build it yourself. All I can afford is this .whl, but keep in mind that it was built on Ubuntu 20.04 with JetPack 4 and Python 3.6 on board.
I have been attempting to install the gpuR package as it is a dependency for another package I want to use. However, simply running install.packages('gpuR') generates an error. For context, I am using a very new install of Linux. The error:
.onAttach failed in attachNamespace() for 'gpuR', details:
call: initContexts()
error: ViennaCL: FATAL ERROR: ViennaCL encountered an unknown OpenCL error. Most likely your OpenCL SDK or driver is not installed properly. In some cases, this error is due to an invalid global work size or several kernel compilation errors.
So it says the potential error clearly there. However, the question now lies on how to properly install OpenCL. Using an AskUbuntu post, I ran the following commands:
sudo apt update
sudo apt install ocl-icd-opencl-dev
Still, this gave the same error. I browsed the intel forums a bit, and installation seems to vary. What would be the correct steps to install OpenCL so that gpuR may be used on Ubuntu 18.04?
ocl-icd is only the loader library. You need to install an implementation (that can be loaded by ocl-icd). Where can you get the implementation, depends on what hardware (GPU) you have. I'll assume Intel since you mention their forums. If you have Haswell or older, google for "intel beignet". If you have Broadwell & newer, google "intel compute runtime".
I am trying to install MultiNest and PyMultiNest on Ubutnu 16.04. I have OpenMPI installed and can successfully run programs with it. However, during the installation of MultiNest, I get this:
kevin#kevin-VirtualBox:~/MultiNest/build$ cmake ..
-- A library with BLAS API found.
-- A library with LAPACK API found.
-- Detected gfortran, adding -ffree-line-length-none compiler flag.
CMake Warning at /usr/share/cmake-3.5/Modules/FindMPI.cmake:406 (message):
Unable to find MPI library mpi_mpifh
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindMPI.cmake:596 (interrogate_mpi_compiler)
src/CMakeLists.txt:86 (FIND_PACKAGE)
-- Could NOT find MPI_Fortran (missing: MPI_Fortran_LIBRARIES)
-- MPI not found, only non-MPI MultiNest libraries will be built.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/kevin/MultiNest/build
Any guidance on how to fix this?
When I installed 'libopenmpi-dev', the cmake process seemed to finish properly.
I'm trying to build an R package which calls Fortran code in Windows system. R BUILD works well but I got some error in R CHECK or R INSTALL.
To compile the Fortran code to get a dll file in Windows system, I have to specify x64 (64 bit) or i386 (32-bit). But when I used dll file compiled by x64 in R CHECK, I will get the error:
Error in inDL(x, as.logical(local), as.logical(now), ...) :
unable to load shared object 'C:/Program Files/R/R-3.3.1/bin/catch.Rcheck/catch/libs/i386/tensor.dll':
LoadLibrary failure: %1 is not a valid Win32 application.
Similarly, if I used the dll file compiled by i386, I will get error in 64-bit installation.
I was wondering is there any way that I can specify using dll from x64 to build a package works for 64 bit machine and dll from i386 to build one for 32 bit machine. Thanks!
It's been a while, but just in case people have the same issue. It's a designed issue and the 32-bit and 64-bit compiled files need to be built separately. Solution is that to build 64 bit version, i386 needs to be moved out of the folder.
Since the R package glmnet doesn't provide binary for windows, so I have to compile it under my OS win7 64bit. How ever I got this error message:
gfortran -m64 -fdefault-real-8 -ffixed-form -O2 -mtune=core2 -c newGLMnet.f90
-o newGLMnet.o
f951.exe: sorry, unimplemented: 64-bit mode not compiled in
make: *** [newGLMnet.o] Error 1
ERROR: compilation failed for package 'glmnet'
I also tried to compile it under windows XP 32bit, but with 'configuration failed for package glmnet' error message.
Has anyone succeed compiling glmnet in Windows?
Trevor Hastie posted this on r-help 12 hours ago:
"We are aware that glmnet_1.7.3 does not pass for windows
and are looking into the problem. It has something to do
with the gcc compiler being slightly different on
windows versus linux/mac platforms. As soon as we have
resolved the issue, we will post a new version to CRAN"
On 64bit Windows, instead of the default PATH :
C:\Rtools\MinGW\bin
try :
C:\Rtools\gcc-4.6.3\bin
Then of course, stop and start a new DOS window to pick up the new PATH.
Also see: https://stackoverflow.com/a/15221883/403310