Summary: | dev-python/qscintilla-python-2.3.2 refuses to build on amd64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Waller <p> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
emerg -pvq qscintilla qlist qscintilla |
Description
Peter Waller
2009-05-13 15:56:01 UTC
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. |