qscintilla-python's build process seems to expect libraries in /usr/lib instead of /usr/lib64 on 64-bit platforms. Build log: >>> Unpacking source... >>> Unpacking QScintilla-gpl-2.3.2.tar.gz to /var/tmp/portage/dev-python/qscintilla-python-2.3.2/work * Applying qscintilla-python-2.2-nostrip.patch ... [ ok ] >>> Source unpacked in /var/tmp/portage/dev-python/qscintilla-python-2.3.2/work >>> Compiling source in /var/tmp/portage/dev-python/qscintilla-python-2.3.2/work/QScintilla-gpl-2.3.2/Python ... Error: The QScintilla library could not be found in /usr/lib. If QScintilla is installed then use the -o argument to explicitly specify the correct directory. * * ERROR: dev-python/qscintilla-python-2.3.2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2471: Called die * The specific snippet of code: * ${python} configure.py ${myconf} || die "configure.py failed"; * The die message: * configure.py failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-python/qscintilla-python-2.3.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/qscintilla-python-2.3.2/temp/environment'. *
Please provide "emerge --info", "emerge -pvq x11-libs/qscintilla" and "qlist x11-libs/qscintilla". (qlist belongs to app-portage/portage-utils)
Reopen this bug when you provide the requested information.
Created attachment 191718 [details] emerge --info
Created attachment 191720 [details] emerg -pvq qscintilla
Created attachment 191721 [details] qlist qscintilla
Hi - Sorry about this. I simply forgot about it. My bad :/ For the time begin my workaround was to set USE="-python" when emerging qscintilla.
Crud, accidentially hit "Closed" when I meant "Reopen". Sorry for spam.
That's strange... I compiled x11-libs/qscintilla with various USE flag combinations and dev-python/qscintilla-python always installed successfully. I tried the following USE flag combinations: python -qt4 -python -qt4 python qt4 -python qt4 which of these combinations were failing for you?
(In reply to comment #8) > > which of these combinations were failing for you? > Fails on all of them. I don't see how it is relevant. qscintilla is correctly installing things to /usr/lib64. The problem seems to be that qscintilla-python is looking in the wrong place (/usr/lib) for the libraries?
Isn't /usr/lib supposed to be a symlink to /usr/lib64? What gives "ls -l /usr |grep lib" on your system?
(In reply to comment #10) > Isn't /usr/lib supposed to be a symlink to /usr/lib64? What gives "ls -l /usr > |grep lib" on your system? > It is not a symlink, it is its own directory. I did not know this. I don't know why it isn't linked. Do you have any idea where I might find documentation on amd64's layout of thinks like /usr/lib64?
Sorry. It seems that this bug was probably caused my own error at some point. I did not know that /usr/lib was supposed to be a symlink to /usr/lib64, and somehow I had two separate directories. I have now remedied this problem. This bug is a non-bug.
