Tue 28 Mar 2017 08:37:12 AM UTC, comment #17:
Pushed https://hg.savannah.gnu.org/hgweb/octave/rev/2613334bafb2.
Closing item.
|
Tue 28 Mar 2017 06:46:37 AM UTC, comment #16:
@Mike: yes, downloading the latest 2.10 (from February 2017) release tar from https://www.riverbankcomputing.com/software/qscintilla/download and then under Qt4Qt5/qscintilla.pro (some Makefile like file) you find this target of comment #14. My point is, before the qscintilla developers had chosen this target name, they could have made a short survey, as I did in 2 Minutes:
https://software.opensuse.org/package/qscintilla-qt5
https://www.archlinux.org/packages/extra/x86_64/qscintilla-qt5/
https://apps.fedoraproject.org/packages/qscintilla-qt5
https://packages.debian.org/sid/libqt5scintilla2-dev
I push the cset soon.
|
Tue 28 Mar 2017 01:30:54 AM UTC, comment #15:
Kai - do you mean that change was made in upstream Qscintilla? If that's the way upstream is going to start naming the library, then we should probably support it, and maybe distros that made their own naming convention will adapt.
|
Mon 27 Mar 2017 10:47:16 PM UTC, comment #14:
Regarding comment #11 a change of the target in qscintilla 2.10 is to blame:
Most distributions prefer the "qscintilla2-qtX" separation and this will cause lots of patches for stable distros switching to 2.10. I like jwe's closing words on bug #48773, if any other maintainer agrees, I'll apply the patch as it does no harm. But I'm afraid this list is to grow longer if qscintilla does not adopt library naming conventions.
|
Thu 23 Mar 2017 01:18:09 AM UTC, comment #13:
Attached a patch to make octave detect qscintilla by it self (at least on Manjaro).
The patch can be applied to octave/m4/acinclude.m4
Dear developers: can you apply the patch and close the bug
regards
Saleh
(file #40088)
|
Sun 19 Mar 2017 07:54:08 AM UTC, comment #12:
@Stefan (in reply to comment #8): This is really strange. In the case where qscintilla is not found on your system, the code where the compilation error on file_editor_tab_widget occurred should never be compiled since it is located within
after the changeset 5bddd4089386.
|
Sun 19 Mar 2017 01:27:21 AM UTC, comment #11:
The problem is form my system.
I updated qscintilla. In the new version the name of the library
changed from qscintilla-q5.so to qscintilla2_qt5.
I did not notice it at first. I am not sure if the name changing is caused by the person who buid qscintilla in Manjaro or by qscintilla itself.
I added the name(qscintilla2_qt5) to the name list in line 1331 of "acinclude.m4" to solve the problem
By doing that, octave is able to detect qscintilla by itself.
@Stefan can you confirm if this is the case for arch
|
Sat 18 Mar 2017 03:58:19 PM UTC, comment #10:
It is weird. I can confirm it builds successfully on manjaro. I also have both qscintilla-qt4 and qscintilla-qt5 installed.
However, octave cannot detect neither.
Note: the path for qscintillas are
/usr/lib/libqscintilla2_qt4.so
/usr/lib/libqscintilla2_qt5.so
|
Sat 18 Mar 2017 03:08:57 PM UTC, comment #9:
Hello, obviously the issue can be worked around by deinstalling qscintilla-qt4.
|
Sat 18 Mar 2017 02:14:49 PM UTC, comment #8:
Both questions have to be answered with yes. Maybe it is relevant that I have both qscintilla-qt4 and qscintilla-qt4 installed.
The error message is exactly the same as the ticket opener had.
|
Sat 18 Mar 2017 12:51:16 PM UTC, comment #7:
@Stefan: You are taling about the error described in the original submission of this report? What is the exact error message and do you have QScintilla installed?
|
Sat 18 Mar 2017 12:45:25 PM UTC, comment #6:
I cannot confirm that 5bddd4089386 fixes the build error under Arch Linux.
|
Sat 18 Mar 2017 10:17:39 AM UTC, comment #5:
@Torsten
with 5bddd4089386 change set, it is possible to build octave
even if scintilla not detected,
@Dan
I built octave from scratch in a new folder, but still cannot detect scintilla.
I believe there is something happened since my last successful build (March 12). At that time, octave was able to detect scintilla.
I was thinking maybe my system is broken, however there are other people having the same problem
https://aur.archlinux.org/packages/octave-hg/
|
Sat 18 Mar 2017 08:57:33 AM UTC, comment #4:
Sounds familiar. See
https://savannah.gnu.org/bugs/?func=detailitem&item_id=48773
That should have been fixed for your setup, though. Have you built Octave from scratch? Sometimes that is needed to get rid of some settings hanging around from previous builds.
|
Sat 18 Mar 2017 08:50:25 AM UTC, comment #3:
Thanks for the report. The bug leading to a compilation error when no qscintilla is available was introduced with changeset changeset 23276:ea143f4f76a5 and is fixed with
http://hg.savannah.gnu.org/hgweb/octave/rev/5bddd4089386
Could you please check this with your system?
The changeset does not fix the issue, that configure does not find qscintilla on your system anymore.
|
Sat 18 Mar 2017 08:49:32 AM UTC, comment #2:
As a work around, I created a link to scintilla wiht a name that
octave familiar with.
sudo ln -s /usr/lib/libqscintilla2_qt5.so /usr/lib/libqt5scintilla2.so
By doing that the problem is solved.
is it possible to make octave figure the correct name by itself?
|
Sat 18 Mar 2017 07:27:26 AM UTC, comment #1:
I think I found a lead
octave cannot find libqscintilla2
The last week is the last time I build octave successfully
the directory of the library on my manjaro linux is
/usr/lib/libqscintilla2_qt5.so
|
Fri 17 Mar 2017 11:02:35 PM UTC, original submission:
I am using MAnjaro linux with gcc version 6.3
This bug probably related to #50567
configured as follow
|