I'm running Anaconda Spyder on Fedora 34.
When I run spyder I get the following error
No QCoreApplication instance found. Application patches not applied. You have to call load_stylesheet function after instantiation of QApplication to take effect.
libGL error: MESA-LOADER: failed to open iris: /home/ted/anaconda3/lib/python3.8/site-packages/zmq/backend/cython/../../../../.././libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib64/dri/iris_dri.so) (search paths /usr/lib64/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /home/ted/anaconda3/lib/python3.8/site-packages/zmq/backend/cython/../../../../.././libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib64/dri/swrast_dri.so) (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
libpng warning: bKGD: invalid
libpng warning: bKGD: invalid
I can see that libstdc++.so.6 is in /usr/lib64, but the search path is /usr/lib64/dri
How can I get iris and swrast to search /usr/lib64 for the driver?
Creating a symlink didn't work.
I have found the answer in this video at 14:50
https://www.youtube.com/watch?v=OqqZ3tqgJnA
You have simply to rename files
libstdc++.so
libstdc++.so.6
libstdc++.so.6.0.28
(or any that have libstdc++.so in it)
in home/anaconda3/lib
You might try this out.
https://unix.stackexchange.com/questions/655495/trying-to-run-pygame-on-my-conda-environment-on-my-fresh-manjaro-install-and-ge
I recommend to directly copy your /usr/lib/libstdc++.so.6 into (anaconda)/lib/.
All the above answers are correct . Also remember if you are in different environment than the base environment. Then you will have to rename
it in that envrionment.
You will find those in env/(env_name)/lib
libstdc++.so -> libstdc++.so.old
libstdc++.so.6 -> libstdc++.so.6.old
libstdc++.so.6.0.28 -> libstdc++.so.0.28.old
Sometimes instead of libstdc++.so.6.0.28 it might be libstdc++.so.6.0.29 or any other number.
Refer this video
https://youtu.be/OqqZ3tqgJnA?t=876
Related
I am trying to install LightGBM GPU version on Windows systems (I am using Anaconda on Windows for Python). I followed the installation guide from the beginning.
I have succefully completed the first two tasks:
Install the appropriate OpenCL SDK
Install MinGW
However, I encountered error after this command for Boost Compilation:
b2 install --build_dir="C:\boost\boost-build" --prefix="C:\boost\boost-build" toolset=gcc --with=filesystem,system threading=multi --layout=system release
The Error Message are as followed:
error: Name clash for 'libboost_atomic.a'
error:
error: Tried to build the target twice, with property sets having
error: these incompatible properties:
error:
error: - 64
error: - 32
error:
error: Please make sure to have consistent requirements for these
error: properties everywhere in your project, especially for install
error: targets.
Please share me any suggestions on how should I rectify the problem?
When I try to get the fabric-sdk-go I get the following error:
$ go get github.com/hyperledger/fabric-sdk-go/pkg/fabric-client
# github.com/hyperledger/fabric-sdk-go/vendor/github.com/miekg/pkcs11
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lltdl
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lltdl
collect2.exe: error: ld returned 1 exit status
Does anyone have an idea what is the issue and how to resolve this?
The error message told us that the library libltdl which is required by github.com/miekg/pkcs11 is missing. Although you didn't mention it explicitly, I think you're using MSYS2 as the development environment. Do the following steps to install the missing library.
Search for the missing library, type pacman -Ss ltdl in MSYS2 terminal to get the exact package name. Here, ltdl is the keyword related to missing library which we got from error message. You should get something like:
msys/libltdl 2.4.6-2
A system independent dlopen wrapper for GNU libtool
From the result we know that the missing library is provided in libltdl package. It seems trivial, but sometimes a library may be provided by more than one package, e.g. a package which has prefix mingw-w64-i686-* for 32-bit system and the other with prefix mingw-w64-x86_64-* for 64-bit system.
Install the package by: pacman -S libltdl.
Reinstall the go package by: go get -v github.com/hyperledger/fabric-sdk-go/pkg/fabric-client.
I need to build Erlang R16B02 on OSX 10.10.5 with support for SSL so I can use crypto application. I have already installed OpenSSL 0.9.8 with Homebrew. Running openssl > version yields the following:
$ openssl
OpenSSL> version
OpenSSL 0.9.8zg 14 July 2015
I am able to get Erlang R16B02 built and installed, but I consistently get the same error when trying to start the crypto application:
1> crypto:start().
** exception error: undefined function crypto:start/0
2>
=ERROR REPORT==== 1-Feb-2016::14:19:17 ===
Unable to load crypto library. Failed with error:
"load_failed, Failed to load NIF library: 'dlopen(~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so, 2): Symbol not found: _AES_cbc_encrypt
Referenced from: ~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so
Expected in: flat namespace
in ~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so'"
OpenSSL might not be installed on this system.
=ERROR REPORT==== 1-Feb-2016::14:19:17 ===
The on_load function for module crypto returned {error,
{load_failed,
"Failed to load NIF library: 'dlopen(~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so, 2): Symbol not found: _AES_cbc_encrypt\n Referenced from: ~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so\n Expected in: flat namespace\n in ~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so'"}}
I have tried calling other functions, like crypto:module_info(), but I always get the same error. I have built Erlang R16B02 with various flags using asdf. Here a couple combinations I tried:
Building with options: --enable-dynamic-ssl-lib --prefix=~/.asdf/installs/erlang/R16B02
Building with options: --with-ssl=/usr/local/opt/openssl --prefix=~/.asdf/installs/erlang/R16B02 # with-ssl points to the OpenSSL install
Building with options: --with-ssl --prefix=~/.asdf/installs/erlang/R16B02
All of these resulted in the same error. One strange thing I noticed when I was trying to figure out how to get Erlang built with SSL was the --enable-darwin-64bit and the --enable-darwin-universal flags caused the build to fail. This seems odd as I am building on OSX, so it seems like these flags would be required.
So to recap:
I am using asdf (shouldn't really matter though)
With all the successfully builds I get the error above when invoking any function in the crypto module
I have Erlang 17 built with OpenSSL and the crypto application
Update
I came across this https://gist.github.com/ThePicard/7378417 so I tried a couple of the options listed there for the configure script but I still got the same error.
Update 2
otool -L ~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so prints this:
~/.asdf/installs/erlang/R16B02/lib/erlang/lib/crypto-3.1/priv/lib/crypto.so:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
I am trying to install Plone to my Ubuntu 14.04, however the install.sh gives me error:
Installing instance. Getting distribution for 'Pillow==1.7.8'.
warning: no previously-included files found matching '.hgignore'
warning: no previously-included files found matching '.hgtags'
warning: no previously-included files found matching 'BUILDME.bat'
warning: no previously-included files found matching
'make-manifest.py' warning: no previously-included files found
matching 'SHIP' warning: no previously-included files found matching
'SHIP.bat' warning: no previously-included files matching '*' found
under directory 'Tests' _imaging.c:3017:5: warning:
initialization from incompatible pointer type [enabled by default]
(inquiry) image_length, /*sq_length*/
^ _imaging.c:3017:5: warning: (near initialization for ‘image_as_sequence.sq_length’) [enabled by default]
_imaging.c:3077:5: warning: initialization from incompatible pointer type [enabled by default]
(inquiry) NULL, /*mp_length*/
^ _imaging.c:3077:5: warning: (near initialization for ‘pixel_access_as_mapping.mp_length’) [enabled by default]
_imaging.c: In function ‘_filter’: _imaging.c:842:8: warning: ‘kernelsize’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
if (kernelsize != xsize * ysize) {
^ libImaging/Quant.c: In function ‘rehash_collide’: libImaging/Quant.c:154:10: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast] *valp=(void *)((*(int
*)valp)+(*(int *)&newval));
^ _imagingft.c:73:31: fatal error: freetype/fterrors.h: No such file or directory #include <freetype/fterrors.h>
^ compilation terminated. error: Setup script exited with error: command 'gcc' failed with exit status 1 An
error occurred when trying to install Pillow 1.7.8. Look above this
message for any errors that were output by easy_install. While:
Installing instance. Getting distribution for 'Pillow==1.7.8'.
Error: Couldn't install: Pillow 1.7.8
And here is what I did with the Unified installer:
I used --build-python option because I am using Enthought Canopy version of Python, which does not have the Python.h that Zope needs to in order to build its instance. So I just build up a new python -which honestly I don't know how it works, but I am guessing it is using virtualenv to isolate the installation environment, correct me if I am wrong.
me#me-N550JV:~/Downloads/Plone-4.3-UnifiedInstaller$ ./install.sh standalone --build-python
Rootless install method chosen. Will install for use by system user me
Detailed installation log being written to /home/me/Downloads/Plone-4.3-UnifiedInstaller/install.log
Installing Plone 4.3 at /home/me/Plone
Skipping libjpeg build
Skipping readline build
Installing Python-2.7.3. This takes a while...
Installing distribute...
Warning: This Python does not have readline support.
It may still be usable for Zope, but interacting directly with Python will be painful.
Python build looks OK.
Unpacking buildout cache to /home/me/Plone/buildout-cache
Copying Plone-docs
Copying buildout skeleton
Fixing up bin/buildout
Building Zope/Plone; this takes a while...
Buildout returned an error code: 1; Aborting.
Buildout failed. Unable to continue
Installation has failed.
See the detailed installation log at /home/me/Downloads/Plone-4.3-UnifiedInstaller/install.log
to determine the cause.
Can someone explain how I can fix the issue with Pillow and get Plone installed in my machine? Thanks so much!
install like this
./install.sh --target=/home/tclap1006/all_folders/unifiedinstallers/Plone --build-python standalone
here --target is path (means at which directory u want to install ur Plone)
I am trying to build boost on cygwin but I cannot find a way to get bjam to start the compilation. May be I am missing something. Can someone give me a clue? FYI: I got following error message.
$ bjam --without-python --without-serialization toolset=gcc-android4.4.3 link=s
tatic runtime-link=static target-os=linux --stagedir=android
warning: mismatched versions of Boost.Build engine and core
warning: Boost.Build engine (bjam) is 03.1.18
warning: Boost.Build core (at /cygdrive/c/progra~1/android/android-ndk-r6b/sourc
es/boost/tools/build/v2) is 2011.04-svn
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/tools/build/v2/util/p
ath.jam:476: in path.makedirs
rule MAKEDIR unknown in module path.
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/tools/build/v2/build/
configure.jam:190: in configure.set-log-file
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/tools/build/v2/build-
system.jam:725: in load
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/tools/build/v2/kernel
/modules.jam:283: in import
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/tools/build/v2/kernel
/bootstrap.jam:142: in boost-build
/cygdrive/c/progra~1/android/android-ndk-r6b/sources/boost/boost-build.jam:17: i
n module scope
UPDATE: this was a problem of old bjam.exe placed in one of my system path. After using right bjam, the problem went away.