Mysql/MariaDb database expert needs...
Locked
12
12
Mysql/MariaDb database expert needs...
 
|
Hi all,
In my huge task of simplification of libraries puzzle, with current 5.0.0-beta implementation, i backported all libkface code in digiKam core, including database. Now digiKam 5.0.0 will not use libkface. I review all database management code, included recognition database, factorized all when it's possible. I tested Sqlite implementation and schema, and all work fine. Now recognition database is managed as thumbnails and core database : same place to store DB files, and same Sqlite engine. As database code is common with other DB engines, this want mean that recognition DB can be managed with Mysql/MariaDB too. So now, i started a tedious task : review all Mysql bugs, that i sorted this summer. The first task is to look into migration files : And i must admit that i'm not an expert with MySql/MariaDB. So i need external expertise and help here. The code from git/master is now fixed to reproduce 4.x mysql support, with same bugs of course. There are 2 solutions to use MySql/MariaDb : internal or external (remote) server. In a first step, i would to start with the first one, which will be more simpler to test and run. But before to continue, i would to know if there is somebody in this room who can help me in this task. Thanks in advance Best Gilles Caulier _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: [Digikam-users] Mysql/MariaDb database expert needs...
|
|
At least, somebody can said me if an internal Mysql solution is suitable or not without to hack the DB installation outside digiKam. I read all bugzilla entries, and to setup Mysql, users need to grant privileges by hand before to configure digiKam with it. This is not possible to do the same with an internal server, since few years ago, Mysql switch DB engine to ImmoDB which require granted privilege to create DB indexes. And this is typically the problem that i can see when i want to create the MySql DB through the internal server. If i look how Amarok do with Mysql, internal server solution do not exist. Only a remote server is avaialble in setup. After all, it's logic. If you want an internal server, Sqlite is already implemented and robust. Mysql must be only dedicated for remote storage. I deducted that Mysql internal server must be removed from digiKam. Gilles Caulier 2015-11-12 10:30 GMT+01:00 Wolfgang Mader <[hidden email]>: On Wednesday 11 November 2015 16:59:00 Gilles Caulier wrote: _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: [Digikam-users] Mysql/MariaDb database expert needs...
|
|
Hi all,
seems I posted from the wrong address the first time... On Thu, Nov 12, 2015 at 10:55 AM, Gilles Caulier <[hidden email]> wrote: > At least, somebody can said me if an internal Mysql solution is suitable or > not without to hack the DB installation outside digiKam. > > I read all bugzilla entries, and to setup Mysql, users need to grant > privileges by hand before to configure digiKam with it. > > This is not possible to do the same with an internal server, since few years > ago, Mysql switch DB engine to ImmoDB which require granted privilege to > create DB indexes. And this is typically the problem that i can see when i > want to create the MySql DB through the internal server. > > If i look how Amarok do with Mysql, internal server solution do not exist. > Only a remote server is avaialble in setup. That is not correct, Amarok uses MySQL embedded by default, setting up an external MySQL server is just an additional option for people who need to share a database across computers. Unfortunately there is little more help I can offer :( Regards, Myriam -- Proud member of the Amarok and KDE Community Protect your freedom and join the Fellowship of FSFE: http://www.fsfe.org Please don't send me proprietary file formats, use ISO standard ODF instead (ISO/IEC 26300) _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: [Digikam-users] Mysql/MariaDb database expert needs...
|
|
2015-11-12 15:15 GMT+01:00 Myriam Schweingruber <[hidden email]>: Hi all, Ah, it's not SQlite... Interesting... So my question is : how to create DB indexes and triggers with an internal solution. When i look in bugzilla, some users have investigated and see that mysql indexes creation need granted privileges since immodb DB engine is used. And this is true : i reproduced the dysfunction and fixed it. Or perhaps Amarok do not use Indexes and triggers. In this case, DB performances will just down... Or perhaps Amarok do not use immodb engine... Gilles Caulier _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
In reply to this post by Gilles Caulier-4
Note - I switched to -devel to stop clogging up -users with compilation
related things. On 18/11/2015 14:15, Gilles Caulier wrote: > In fact when i started to port code to Qt5, i used 5.4, but i'm sure > that 5.2 will work as well. > It looked too scary to update 14.04 to get kf5 so I created a schroot image for Wily (15.10). I'm having a bit of trouble identifying all of the packages that are required. At present I'm stuck at the following error. If anyone can point me in the right direction (even if it means building a minimal version) that will be appreciated so that I can get something to test. Regards Richard (wily)laptop@duncow:~/Git/digikam/digikam-software-compilation$ ./bootstrap.local Qt Install Path : /usr KF5 Install Path : /usr digiKam Install Path : /tmp/digikam -- ---------------------------------------------------------------------------------- -- Starting CMake configuration for: digikam-software-collection -- Local shared libkipi will be compiled.......... NO (library source code not available) -- Local shared libksane will be compiled.......... NO (library source code not available) -- Local shared libmediawiki will be compiled.......... NO (library source code not available) -- Local shared libkvkontakte will be compiled.......... NO (library source code not available) -- Extract translations files..................... NO -- Translations will be compiled.................. NO -- Handbooks will be compiled..................... NO -- Tests code will be compiled.................... YES -- ---------------------------------------------------------------------------------- -- Starting CMake configuration for: kipi-plugins -- Found KF5: success (found suitable version "5.15.0", minimum required is "5.1.0") found components: Config WindowSystem XmlGui I18n KIO Service IconThemes CMake Warning at /usr/share/ECM/find-modules/FindKF5.cmake:74 (find_package): Could not find a configuration file for package "KF5CalendarCore" that is compatible with requested version "5.1.0". The following configuration files were considered but not accepted: /usr/lib/x86_64-linux-gnu/cmake/KF5CalendarCore/KF5CalendarCoreConfig.cmake, version: 4.82.0 Call Stack (most recent call first): extra/kipi-plugins/CMakeLists.txt:116 (find_package) -- Could NOT find KF5CalendarCore , checked the following files: /usr/lib/x86_64-linux-gnu/cmake/KF5CalendarCore/KF5CalendarCoreConfig.cmake (version 4.82.0) -- Found KF5: success (found suitable version "5.15.0", minimum required is "5.1.0") found components: Archive ThreadWeaver missing components: CalendarCore -- libkipi : search system based library CMake Error at extra/kipi-plugins/cmake/modules/MacroLocalLibs.cmake:13 (find_package): Could not find a package configuration file provided by "KF5Kipi" (requested version 5.0.0) with any of the following names: KF5KipiConfig.cmake kf5kipi-config.cmake Add the installation prefix of "KF5Kipi" to CMAKE_PREFIX_PATH or set "KF5Kipi_DIR" to a directory containing one of the above files. If "KF5Kipi" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): extra/kipi-plugins/CMakeLists.txt:125 (DETECT_LIBKIPI) -- Configuring incomplete, errors occurred! See also "/home/laptop/Git/digikam/digikam-software-compilation/build/CMakeFiles/CMakeOutput.log". Could not find drkonqi at /usr/lib/x86_64-linux-gnu/libexec/drkonqi kbuildsycoca5 running... Reusing existing ksycoca Recreating ksycoca file ("/tmp/digikam/var/tmp/kde-laptop/ksycoca5", version 303) Still in the time dict (i.e. deleted files) ("apps") Menu "applications-kmenuedit.menu" not found. Saving To run your local installation after building it, add this to your .bashrc: DIGIKAMROOT=/tmp/digikam alias digikam-dev="KDESYCOCA=$DIGIKAMROOT/var/tmp/kde-laptop/ksycoca5 XDG_DATA_DIRS=$DIGIKAMROOT/share QT_PLUGIN_PATH=$DIGIKAMROOT/lib64/plugins:$DIGIKAMROOT/lib/plugins:$QT_PLUGIN_PATH $DIGIKAMROOT/bin/digikam" Then open a new shell (or source .bashrc) and run "digikam-dev". _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
You try to compile digiKam as stand alone. This is not the simplest way to do. Checkout the digiKam Software Compilation with git : git clone git://anongit.kde.org/digikam-software-compilation And follow instructions in README to checkout all relevant sub-project automatically. Take a care to set "export GITSLAVE=.gitslave.devel" before to be sure to download all that you needs... Gilles Caulier
2015-11-19 17:40 GMT+01:00 Richard Mortimer <[hidden email]>: Note - I switched to -devel to stop clogging up -users with compilation _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
On 19/11/2015 18:02, Gilles Caulier wrote:
> You try to compile digiKam as stand alone. This is not the simplest way > to do. > > Checkout the digiKam Software Compilation with git : > > git clone git://anongit.kde.org/digikam-software-compilation > <http://anongit.kde.org/digikam-software-compilation> > > And follow instructions in README to checkout all relevant sub-project > automatically. Take a care to set "export GITSLAVE=.gitslave.devel" > before to be sure to download all that you needs... Many thanks. That got me a lot further. I was following the instructions from https://www.digikam.org/download/GIT and that doesn't mention the .gitslave.devel bit. I've got to 93% building now but its is stopping on the facedetector build. Can anyone point me towards what is missing to stop the build working now. Last bit of the build log is below. Regards Richard [ 93%] Built target align [ 93%] Automatic moc for target detect [ 93%] Built target detect_automoc Linking CXX executable detect ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o): In function `FacesEngine::FaceDetector::detectFaces(QImage const&, QSize const&)': /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:166: undefined reference to `DIGIKAM_FACESENGINE_LOG()' /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:166: undefined reference to `DIGIKAM_FACESENGINE_LOG()' /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:170: undefined reference to `DIGIKAM_FACESENGINE_LOG()' /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:170: undefined reference to `DIGIKAM_FACESENGINE_LOG()' ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o): In function `FacesEngine::FaceDetector::Private::backend()': /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:65: undefined reference to `DIGIKAM_FACESENGINE_LOG()' ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o):/home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:65: more undefined references to `DIGIKAM_FACESENGINE_LOG()' follow collect2: error: ld returned 1 exit status core/tests/facesengine/CMakeFiles/detect.dir/build.make:133: recipe for target 'core/tests/facesengine/detect' failed make[2]: *** [core/tests/facesengine/detect] Error 1 CMakeFiles/Makefile2:15789: recipe for target 'core/tests/facesengine/CMakeFiles/detect.dir/all' failed make[1]: *** [core/tests/facesengine/CMakeFiles/detect.dir/all] Error 2 Makefile:126: recipe for target 'all' failed make: *** [all] Error 2 _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
Strange. All compile fine here... This is the unit test code that you can drop from compilation using a cmake option : -DBUILD_TESTING=OFF. If you use bootstrap.linux, just change option in this file as well, remove cmake cache file from build sub dir, reconfigure and compile... Gilles 2015-11-20 17:27 GMT+01:00 Richard Mortimer <[hidden email]>: On 19/11/2015 18:02, Gilles Caulier wrote: _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
Any progress here ? Did you compile digiKAm with Mysql cmake option turned on ? Gilles Caulier 2015-11-20 17:57 GMT+01:00 Gilles Caulier <[hidden email]>:
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
Hi,
On 22/11/2015 17:30, Gilles Caulier wrote: > Any progress here ? Yes. I got it compiled but ran out of time before weekend commitments kicked in. > > Did you compile digiKAm with Mysql cmake option turned on ? Yes. That was auto-detected and the configuration reported that it was building with it. Digikam will now start up but it is not finding image resources and other similar files etc. I suspect it is because I tried to install in a standalone directory. so I'm planning to rebuild for a normal install and will try again at lunchtime. Regards Richard > > Gilles Caulier > > 2015-11-20 17:57 GMT+01:00 Gilles Caulier <[hidden email] > <mailto:[hidden email]>>: > > Strange. All compile fine here... > > This is the unit test code that you can drop from compilation using > a cmake option : > > -DBUILD_TESTING=OFF. > > If you use bootstrap.linux, just change option in this file as well, > remove cmake cache file from build sub dir, reconfigure and compile... > > Gilles > > > 2015-11-20 17:27 GMT+01:00 Richard Mortimer > <[hidden email] <mailto:[hidden email]>>: > > On 19/11/2015 18:02, Gilles Caulier wrote: > > You try to compile digiKam as stand alone. This is not the simplest way > > to do. > > > > Checkout the digiKam Software Compilation with git : > > > > git clone git://anongit.kde.org/digikam-software-compilation > <http://anongit.kde.org/digikam-software-compilation> > > <http://anongit.kde.org/digikam-software-compilation> > > > > And follow instructions in README to checkout all relevant sub-project > > automatically. Take a care to set "export GITSLAVE=.gitslave.devel" > > before to be sure to download all that you needs... > > Many thanks. That got me a lot further. I was following the > instructions > from https://www.digikam.org/download/GIT and that doesn't > mention the > .gitslave.devel bit. > > I've got to 93% building now but its is stopping on the facedetector > build. Can anyone point me towards what is missing to stop the build > working now. Last bit of the build log is below. > > Regards > > Richard > > > [ 93%] Built target align > [ 93%] Automatic moc for target detect > [ 93%] Built target detect_automoc > Linking CXX executable detect > ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o): > In > function `FacesEngine::FaceDetector::detectFaces(QImage const&, > QSize > const&)': > /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:166: > undefined reference to `DIGIKAM_FACESENGINE_LOG()' > /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:166: > undefined reference to `DIGIKAM_FACESENGINE_LOG()' > /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:170: > undefined reference to `DIGIKAM_FACESENGINE_LOG()' > /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:170: > undefined reference to `DIGIKAM_FACESENGINE_LOG()' > ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o): > In > function `FacesEngine::FaceDetector::Private::backend()': > /home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:65: > undefined reference to `DIGIKAM_FACESENGINE_LOG()' > ../../libs/facesengine/libdigikamfacesengine.a(facedetector.cpp.o):/home/laptop/Git/digikam/digikam-software-compilation/core/libs/facesengine/facedetector.cpp:65: > more undefined references to `DIGIKAM_FACESENGINE_LOG()' follow > collect2: error: ld returned 1 exit status > core/tests/facesengine/CMakeFiles/detect.dir/build.make:133: > recipe for > target 'core/tests/facesengine/detect' failed > make[2]: *** [core/tests/facesengine/detect] Error 1 > CMakeFiles/Makefile2:15789: recipe for target > 'core/tests/facesengine/CMakeFiles/detect.dir/all' failed > make[1]: *** [core/tests/facesengine/CMakeFiles/detect.dir/all] > Error 2 > Makefile:126: recipe for target 'all' failed > make: *** [all] Error 2 > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] <mailto:[hidden email]> > https://mail.kde.org/mailman/listinfo/digikam-devel > > > > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
2015-11-23 11:42 GMT+01:00 Richard Mortimer <[hidden email]>: Hi, ok. And don't forget to update local source code with "git up". You can use root script "gits" located to top level directory of source code. This one will update all git components comming with digiKam Software compilation. the update will be recursive. PS : i currently working to be able to setup a specific place to host database with internal server (as with Sqlite). Currently it still located in ~/.local/share/digikam Gilles Caulier _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
On 23/11/2015 10:48, Gilles Caulier wrote: > > > 2015-11-23 11:42 GMT+01:00 Richard Mortimer > <[hidden email] <mailto:[hidden email]>>: > > ok. And don't forget to update local source code with "git up". You can > use root script "gits" located to top level directory of source code. > This one will update all git components comming with digiKam Software > compilation. the update will be recursive. Thanks. Did that. > > PS : i currently working to be able to setup a specific place to host > database with internal server (as with Sqlite). Currently it still > located in ~/.local/share/digikam Will bear that in mind. I now have it running. Yah! I had a problem with kipiplugin_imgur.so that seems to be linked against some QT4 libraries and was causing a segmentation violation on startup. For now I have just removed the .so file from /usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_imgur.so and digikam now starts up fully. I've included the ldd output for the imgur plugin below and can clearly see that it is using some qt4 libraries in a couple of places. I'm not sure if that is a build issue or whether another dependency is not installed in my build environment. I have ran out of time for testing now but will try again tonight and hopefully will be able to get some MySQL testing done. Regards Richard ldd digikam-software-compilation/build/extra/kipi-plugins/imgur/kipiplugin_imgur.so linux-vdso.so.1 => (0x00007ffe0ad2d000) libKF5KIOCore.so.5 => /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 (0x00007fd5a875f000) libKF5kipiplugins.so.5.0.0 => /home/laptop/Git/digikam/digikam-software-compilation/build/extra/kipi-plugins/common/libkipiplugins/libKF5kipiplugins.so.5.0.0 (0x00007fd5a84cf000) libkqoauth.so.0 => /usr/lib/x86_64-linux-gnu/libkqoauth.so.0 (0x00007fd5a82ab000) libKF5Kipi.so.30.0.0 => /home/laptop/Git/digikam/digikam-software-compilation/build/extra/libkipi/src/libKF5Kipi.so.30.0.0 (0x00007fd5a807b000) libKF5XmlGui.so.5 => /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 (0x00007fd5a7d8d000) libKF5WindowSystem.so.5 => /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 (0x00007fd5a7b46000) libKF5ConfigGui.so.5 => /usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5 (0x00007fd5a7927000) libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007fd5a72a6000) libKF5CoreAddons.so.5 => /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 (0x00007fd5a7021000) libKF5I18n.so.5 => /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5 (0x00007fd5a6def000) libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x00007fd5a68b5000) libKF5ConfigCore.so.5 => /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 (0x00007fd5a665a000) libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x00007fd5a619e000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fd5a5e1c000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd5a5a52000) libKF5Service.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Service.so.5 (0x00007fd5a57be000) libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007fd5a8d8f000) libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5 (0x00007fd5a8d53000) libKF5DBusAddons.so.5 => /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 (0x00007fd5a55ae000) libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007fd5a53a5000) libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x00007fd5a5324000) libKF5ConfigWidgets.so.5 => /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 (0x00007fd5a50d9000) libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007fd5a43e8000) libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007fd5a4094000) libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007fd5a3ba2000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fd5a398b000) libQt5PrintSupport.so.5 => /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 (0x00007fd5a3918000) libKF5TextWidgets.so.5 => /usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5 (0x00007fd5a36db000) libKF5GlobalAccel.so.5 => /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 (0x00007fd5a34ba000) libKF5Attica.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Attica.so.5 (0x00007fd5a3222000) libKF5IconThemes.so.5 => /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 (0x00007fd5a2fe8000) libKF5WidgetsAddons.so.5 => /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 (0x00007fd5a2cb4000) libKF5ItemViews.so.5 => /usr/lib/x86_64-linux-gnu/libKF5ItemViews.so.5 (0x00007fd5a2a7c000) libQt5X11Extras.so.5 => /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 (0x00007fd5a8d48000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fd5a2742000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fd5a2521000) libxcb-keysyms.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1 (0x00007fd5a231e000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd5a2100000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fd5a1ead000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fd5a1b9e000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd5a1896000) libfam.so.0 => /usr/lib/libfam.so.0 (0x00007fd5a168d000) libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007fd5a1467000) libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007fd5a1209000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fd5a0fef000) libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007fd5a0d57000) libicui18n.so.55 => /usr/lib/x86_64-linux-gnu/libicui18n.so.55 (0x00007fd5a08f4000) libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007fd5a0560000) libpcre16.so.3 => /usr/lib/x86_64-linux-gnu/libpcre16.so.3 (0x00007fd5a02fd000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd5a00f9000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fd59fef1000) /lib64/ld-linux-x86-64.so.2 (0x00007fd5a8ce5000) libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007fd59fcec000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fd59faa0000) libKF5Codecs.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5 (0x00007fd59f867000) libKF5Auth.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Auth.so.5 (0x00007fd59f654000) libKF5GuiAddons.so.5 => /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5 (0x00007fd59f43b000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fd59f1fd000) libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007fd59efe4000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fd59ed3e000) libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007fd59eb36000) libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007fd59e91c000) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007fd59e70c000) libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fd59e502000) libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fd59e2f0000) libKF5SonnetUi.so.5 => /usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 (0x00007fd59e0ce000) libKF5SonnetCore.so.5 => /usr/lib/x86_64-linux-gnu/libKF5SonnetCore.so.5 (0x00007fd59dead000) libKF5Completion.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5 (0x00007fd59dc78000) libQt5Svg.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5 (0x00007fd59dc21000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fd59da1d000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fd59d817000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fd59d60f000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fd59d3a2000) libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007fd59d186000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fd59cf5d000) libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007fd59cd2f000) libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007fd59cb2c000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007fd59c926000) libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007fd59c724000) libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007fd59c50b000) libxcb-dri2.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0 (0x00007fd59c306000) libxcb-dri3.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 (0x00007fd59c103000) libxcb-present.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 (0x00007fd59bf00000) libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 (0x00007fd59bcf9000) libxshmfence.so.1 => /usr/lib/x86_64-linux-gnu/libxshmfence.so.1 (0x00007fd59baf6000) libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007fd59b8f0000) libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007fd59b6e2000) libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007fd599c2b000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fd599baa000) libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007fd599941000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fd59973c000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fd59951a000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fd599238000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fd599025000) > > Gilles Caulier > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
The imgur problem have been already reported to digiKam users ML. In fact the imgur tool can use a shared lib to extend capability. Look DEPENDENCIES file : libqtkoauth opt >= 0.97 ImgUr tool. This lib must be compiled with Qt5. if this lib is Qt4 based the mix Qt4/Qt5 is not compatible and crash. So 2 solutions : /1 remove libqtkoauth as well and recompile kipi-plugins. /2 remove libqtkoauth and recompile it against Qt5, and recompile kipi-plugins. Gilles Caulier 2015-11-23 15:29 GMT+01:00 Richard Mortimer <[hidden email]>:
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
In reply to this post by Richard Mortimer-2
On 11/23/2015 03:29 PM, Richard Mortimer wrote:
> I had a problem with kipiplugin_imgur.so that seems to be linked against > some QT4 libraries and was causing a segmentation violation on startup. > For now I have just removed the .so file from > /usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_imgur.so > and digikam now starts up fully. I had just that recently and it turned out to be realted to the fact that kqoauth upstream and ubuntu version I picked is still compiled for qt4 by default. Further hacking was needed on this one : the Makefile at the root dir that is used by debian/rules has been generated with qmake from qt4. You need to regenerate it using qt5 qmake, fix the script that generates the package dependency (.pc is wrong otherwyse), and fix the mkspecs location in the .install That's the way I resolved it on debian... -- eric _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
In reply to this post by Gilles Caulier-4
Thanks for the tips. I haven't tried any of your solutions yet (have
just been removing the plugin .so file when testing a new build). I'll probably just use your first solution later today. I made some good progress on MySQL last night. I have a schema that does not require "SUPER" privilege. Basically I removed the triggers and replaced them with foreign key references configured to have the same semantics as the triggers. Proof of concept patch series to follow. Regards Richard On 23/11/2015 14:39, Gilles Caulier wrote: > The imgur problem have been already reported to digiKam users ML. > > In fact the imgur tool can use a shared lib to extend capability. Look > DEPENDENCIES file : > > libqtkoauth opt >= 0.97 ImgUr tool. This lib must be > compiled with Qt5. > > if this lib is Qt4 based the mix Qt4/Qt5 is not compatible and crash. So > 2 solutions : > > /1 remove libqtkoauth as well and recompile kipi-plugins. > /2 remove libqtkoauth and recompile it against Qt5, and recompile > kipi-plugins. > > Gilles Caulier > > > > > 2015-11-23 15:29 GMT+01:00 Richard Mortimer > <[hidden email] <mailto:[hidden email]>>: > > > > On 23/11/2015 10:48, Gilles Caulier wrote: > > > > > > 2015-11-23 11:42 GMT+01:00 Richard Mortimer > > <[hidden email] > <mailto:richm%[hidden email]> > <mailto:[hidden email] > <mailto:richm%[hidden email]>>>: > > > > ok. And don't forget to update local source code with "git up". You can > > use root script "gits" located to top level directory of source code. > > This one will update all git components comming with digiKam Software > > compilation. the update will be recursive. > Thanks. Did that. > > > > > PS : i currently working to be able to setup a specific place to host > > database with internal server (as with Sqlite). Currently it still > > located in ~/.local/share/digikam > Will bear that in mind. > > I now have it running. Yah! > > I had a problem with kipiplugin_imgur.so that seems to be linked against > some QT4 libraries and was causing a segmentation violation on startup. > For now I have just removed the .so file from > /usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_imgur.so > and digikam now starts up fully. > > I've included the ldd output for the imgur plugin below and can clearly > see that it is using some qt4 libraries in a couple of places. I'm not > sure if that is a build issue or whether another dependency is not > installed in my build environment. > > I have ran out of time for testing now but will try again tonight and > hopefully will be able to get some MySQL testing done. > > Regards > > Richard > > > ldd > digikam-software-compilation/build/extra/kipi-plugins/imgur/kipiplugin_imgur.so > linux-vdso.so.1 => (0x00007ffe0ad2d000) > libKF5KIOCore.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 > (0x00007fd5a875f000) > libKF5kipiplugins.so.5.0.0 => > /home/laptop/Git/digikam/digikam-software-compilation/build/extra/kipi-plugins/common/libkipiplugins/libKF5kipiplugins.so.5.0.0 > (0x00007fd5a84cf000) > libkqoauth.so.0 => /usr/lib/x86_64-linux-gnu/libkqoauth.so.0 > (0x00007fd5a82ab000) > libKF5Kipi.so.30.0.0 => > /home/laptop/Git/digikam/digikam-software-compilation/build/extra/libkipi/src/libKF5Kipi.so.30.0.0 > (0x00007fd5a807b000) > libKF5XmlGui.so.5 => /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 > (0x00007fd5a7d8d000) > libKF5WindowSystem.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 (0x00007fd5a7b46000) > libKF5ConfigGui.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5 > (0x00007fd5a7927000) > libQt5Widgets.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > (0x00007fd5a72a6000) > libKF5CoreAddons.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 (0x00007fd5a7021000) > libKF5I18n.so.5 => /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5 > (0x00007fd5a6def000) > libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 > (0x00007fd5a68b5000) > libKF5ConfigCore.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 (0x00007fd5a665a000) > libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > (0x00007fd5a619e000) > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x00007fd5a5e1c000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x00007fd5a5a52000) > libKF5Service.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5Service.so.5 > (0x00007fd5a57be000) > libQt5Network.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 > (0x00007fd5a8d8f000) > libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5 > (0x00007fd5a8d53000) > libKF5DBusAddons.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 (0x00007fd5a55ae000) > libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 > (0x00007fd5a53a5000) > libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 > (0x00007fd5a5324000) > libKF5ConfigWidgets.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 (0x00007fd5a50d9000) > libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 > (0x00007fd5a43e8000) > libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 > (0x00007fd5a4094000) > libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 > (0x00007fd5a3ba2000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x00007fd5a398b000) > libQt5PrintSupport.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 (0x00007fd5a3918000) > libKF5TextWidgets.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5 (0x00007fd5a36db000) > libKF5GlobalAccel.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 (0x00007fd5a34ba000) > libKF5Attica.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Attica.so.5 > (0x00007fd5a3222000) > libKF5IconThemes.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 (0x00007fd5a2fe8000) > libKF5WidgetsAddons.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 (0x00007fd5a2cb4000) > libKF5ItemViews.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5ItemViews.so.5 > (0x00007fd5a2a7c000) > libQt5X11Extras.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 > (0x00007fd5a8d48000) > libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 > (0x00007fd5a2742000) > libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 > (0x00007fd5a2521000) > libxcb-keysyms.so.1 => > /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1 > (0x00007fd5a231e000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007fd5a2100000) > libgobject-2.0.so.0 => > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > (0x00007fd5a1ead000) > libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 > (0x00007fd5a1b9e000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > (0x00007fd5a1896000) > libfam.so.0 => /usr/lib/libfam.so.0 (0x00007fd5a168d000) > libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 > (0x00007fd5a1467000) > libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 > (0x00007fd5a1209000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 > (0x00007fd5a0fef000) > libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 > (0x00007fd5a0d57000) > libicui18n.so.55 => /usr/lib/x86_64-linux-gnu/libicui18n.so.55 > (0x00007fd5a08f4000) > libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 > (0x00007fd5a0560000) > libpcre16.so.3 => /usr/lib/x86_64-linux-gnu/libpcre16.so.3 > (0x00007fd5a02fd000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x00007fd5a00f9000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > (0x00007fd59fef1000) > /lib64/ld-linux-x86-64.so.2 (0x00007fd5a8ce5000) > libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 > (0x00007fd59fcec000) > libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 > (0x00007fd59faa0000) > libKF5Codecs.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5 > (0x00007fd59f867000) > libKF5Auth.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Auth.so.5 > (0x00007fd59f654000) > libKF5GuiAddons.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5 > (0x00007fd59f43b000) > libfontconfig.so.1 => > /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 > (0x00007fd59f1fd000) > libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 > (0x00007fd59efe4000) > libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 > (0x00007fd59ed3e000) > libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 > (0x00007fd59eb36000) > libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 > (0x00007fd59e91c000) > libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 > (0x00007fd59e70c000) > libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 > (0x00007fd59e502000) > libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 > (0x00007fd59e2f0000) > libKF5SonnetUi.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 > (0x00007fd59e0ce000) > libKF5SonnetCore.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5SonnetCore.so.5 (0x00007fd59dead000) > libKF5Completion.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5 (0x00007fd59dc78000) > libQt5Svg.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5 > (0x00007fd59dc21000) > libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 > (0x00007fd59da1d000) > libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 > (0x00007fd59d817000) > libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 > (0x00007fd59d60f000) > libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 > (0x00007fd59d3a2000) > libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 > (0x00007fd59d186000) > libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 > (0x00007fd59cf5d000) > libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 > (0x00007fd59cd2f000) > libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 > (0x00007fd59cb2c000) > libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 > (0x00007fd59c926000) > libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 > (0x00007fd59c724000) > libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 > (0x00007fd59c50b000) > libxcb-dri2.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0 > (0x00007fd59c306000) > libxcb-dri3.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 > (0x00007fd59c103000) > libxcb-present.so.0 => > /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 > (0x00007fd59bf00000) > libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 > (0x00007fd59bcf9000) > libxshmfence.so.1 => /usr/lib/x86_64-linux-gnu/libxshmfence.so.1 > (0x00007fd59baf6000) > libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 > (0x00007fd59b8f0000) > libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 > (0x00007fd59b6e2000) > libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 > (0x00007fd599c2b000) > libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 > (0x00007fd599baa000) > libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 > (0x00007fd599941000) > libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 > (0x00007fd59973c000) > liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 > (0x00007fd59951a000) > libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 > (0x00007fd599238000) > libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 > (0x00007fd599025000) > > > > > > > Gilles Caulier > > > > > > _______________________________________________ > > Digikam-devel mailing list > > [hidden email] <mailto:[hidden email]> > > https://mail.kde.org/mailman/listinfo/digikam-devel > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] <mailto:[hidden email]> > https://mail.kde.org/mailman/listinfo/digikam-devel > > > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
I see you post on ML about your MySQL patches, but, your patches are not visible as attachements. I recommend to open a new file in bugzilla into digiKam/database-schema section for each patches instead to use ML. Never use ML for patches, it's not safe. Thanks in advance for your work. Gilles Caulier 2015-11-24 10:24 GMT+01:00 Richard Mortimer <[hidden email]>: Thanks for the tips. I haven't tried any of your solutions yet (have _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
On 24/11/2015 10:02, Gilles Caulier wrote:
> I see you post on ML about your MySQL patches, but, your patches are not > visible as attachements. > > I recommend to open a new file in bugzilla into digiKam/database-schema > section for each patches instead to use ML. Never use ML for patches, > it's not safe. > https://bugs.kde.org/show_bug.cgi?id=355831 > Thanks in advance for your work. More importantly thanks for all your work on Digikam! Regards Richard > > Gilles Caulier > > 2015-11-24 10:24 GMT+01:00 Richard Mortimer > <[hidden email] <mailto:[hidden email]>>: > > Thanks for the tips. I haven't tried any of your solutions yet (have > just been removing the plugin .so file when testing a new build). I'll > probably just use your first solution later today. > > I made some good progress on MySQL last night. I have a schema that does > not require "SUPER" privilege. Basically I removed the triggers and > replaced them with foreign key references configured to have the same > semantics as the triggers. > > Proof of concept patch series to follow. > > Regards > > Richard > > On 23/11/2015 14:39, Gilles Caulier wrote: > > The imgur problem have been already reported to digiKam users ML. > > > > In fact the imgur tool can use a shared lib to extend capability. Look > > DEPENDENCIES file : > > > > libqtkoauth opt >= 0.97 ImgUr tool. This lib must be > > compiled with Qt5. > > > > if this lib is Qt4 based the mix Qt4/Qt5 is not compatible and crash. So > > 2 solutions : > > > > /1 remove libqtkoauth as well and recompile kipi-plugins. > > /2 remove libqtkoauth and recompile it against Qt5, and recompile > > kipi-plugins. > > > > Gilles Caulier > > > > > > > > > > 2015-11-23 15:29 GMT+01:00 Richard Mortimer > > <[hidden email] > <mailto:richm%[hidden email]> > <mailto:[hidden email] > <mailto:richm%[hidden email]>>>: > > > > > > > > On 23/11/2015 10:48, Gilles Caulier wrote: > > > > > > > > > 2015-11-23 11:42 GMT+01:00 Richard Mortimer > > > <[hidden email] <mailto:richm%[hidden email]> > > <mailto:richm%[hidden email] > <mailto:richm%[hidden email]>> > > <mailto:[hidden email] > <mailto:richm%[hidden email]> > > <mailto:richm%[hidden email] > <mailto:richm%[hidden email]>>>>: > > > > > > ok. And don't forget to update local source code with "git > up". You can > > > use root script "gits" located to top level directory of > source code. > > > This one will update all git components comming with digiKam > Software > > > compilation. the update will be recursive. > > Thanks. Did that. > > > > > > > > PS : i currently working to be able to setup a specific > place to host > > > database with internal server (as with Sqlite). Currently it > still > > > located in ~/.local/share/digikam > > Will bear that in mind. > > > > I now have it running. Yah! > > > > I had a problem with kipiplugin_imgur.so that seems to be > linked against > > some QT4 libraries and was causing a segmentation violation on > startup. > > For now I have just removed the .so file from > > /usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_imgur.so > > and digikam now starts up fully. > > > > I've included the ldd output for the imgur plugin below and > can clearly > > see that it is using some qt4 libraries in a couple of places. > I'm not > > sure if that is a build issue or whether another dependency is not > > installed in my build environment. > > > > I have ran out of time for testing now but will try again > tonight and > > hopefully will be able to get some MySQL testing done. > > > > Regards > > > > Richard > > > > > > ldd > > > digikam-software-compilation/build/extra/kipi-plugins/imgur/kipiplugin_imgur.so > > linux-vdso.so.1 => (0x00007ffe0ad2d000) > > libKF5KIOCore.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 > > (0x00007fd5a875f000) > > libKF5kipiplugins.so.5.0.0 => > > > /home/laptop/Git/digikam/digikam-software-compilation/build/extra/kipi-plugins/common/libkipiplugins/libKF5kipiplugins.so.5.0.0 > > (0x00007fd5a84cf000) > > libkqoauth.so.0 => > /usr/lib/x86_64-linux-gnu/libkqoauth.so.0 > > (0x00007fd5a82ab000) > > libKF5Kipi.so.30.0.0 => > > > /home/laptop/Git/digikam/digikam-software-compilation/build/extra/libkipi/src/libKF5Kipi.so.30.0.0 > > (0x00007fd5a807b000) > > libKF5XmlGui.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 > > (0x00007fd5a7d8d000) > > libKF5WindowSystem.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 > (0x00007fd5a7b46000) > > libKF5ConfigGui.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5ConfigGui.so.5 > > (0x00007fd5a7927000) > > libQt5Widgets.so.5 => > > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > > (0x00007fd5a72a6000) > > libKF5CoreAddons.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 > (0x00007fd5a7021000) > > libKF5I18n.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5 > > (0x00007fd5a6def000) > > libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 > > (0x00007fd5a68b5000) > > libKF5ConfigCore.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 > (0x00007fd5a665a000) > > libQt5Core.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > > (0x00007fd5a619e000) > > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > > (0x00007fd5a5e1c000) > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > > (0x00007fd5a5a52000) > > libKF5Service.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5Service.so.5 > > (0x00007fd5a57be000) > > libQt5Network.so.5 => > > /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 > > (0x00007fd5a8d8f000) > > libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5 > > (0x00007fd5a8d53000) > > libKF5DBusAddons.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 > (0x00007fd5a55ae000) > > libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 > > (0x00007fd5a53a5000) > > libQt5DBus.so.5 => > /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 > > (0x00007fd5a5324000) > > libKF5ConfigWidgets.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 > (0x00007fd5a50d9000) > > libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 > > (0x00007fd5a43e8000) > > libQtNetwork.so.4 => > /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 > > (0x00007fd5a4094000) > > libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 > > (0x00007fd5a3ba2000) > > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > > (0x00007fd5a398b000) > > libQt5PrintSupport.so.5 => > > /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 > (0x00007fd5a3918000) > > libKF5TextWidgets.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5 > (0x00007fd5a36db000) > > libKF5GlobalAccel.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5GlobalAccel.so.5 > (0x00007fd5a34ba000) > > libKF5Attica.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5Attica.so.5 > > (0x00007fd5a3222000) > > libKF5IconThemes.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 > (0x00007fd5a2fe8000) > > libKF5WidgetsAddons.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 > (0x00007fd5a2cb4000) > > libKF5ItemViews.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5ItemViews.so.5 > > (0x00007fd5a2a7c000) > > libQt5X11Extras.so.5 => > > /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 > > (0x00007fd5a8d48000) > > libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 > > (0x00007fd5a2742000) > > libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 > > (0x00007fd5a2521000) > > libxcb-keysyms.so.1 => > > /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1 > > (0x00007fd5a231e000) > > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > > (0x00007fd5a2100000) > > libgobject-2.0.so.0 => > > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > > (0x00007fd5a1ead000) > > libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 > > (0x00007fd5a1b9e000) > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > > (0x00007fd5a1896000) > > libfam.so.0 => /usr/lib/libfam.so.0 (0x00007fd5a168d000) > > libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 > > (0x00007fd5a1467000) > > libharfbuzz.so.0 => > /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 > > (0x00007fd5a1209000) > > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 > > (0x00007fd5a0fef000) > > libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 > > (0x00007fd5a0d57000) > > libicui18n.so.55 => > /usr/lib/x86_64-linux-gnu/libicui18n.so.55 > > (0x00007fd5a08f4000) > > libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 > > (0x00007fd5a0560000) > > libpcre16.so.3 => /usr/lib/x86_64-linux-gnu/libpcre16.so.3 > > (0x00007fd5a02fd000) > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > > (0x00007fd5a00f9000) > > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > > (0x00007fd59fef1000) > > /lib64/ld-linux-x86-64.so.2 (0x00007fd5a8ce5000) > > libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 > > (0x00007fd59fcec000) > > libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 > > (0x00007fd59faa0000) > > libKF5Codecs.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5Codecs.so.5 > > (0x00007fd59f867000) > > libKF5Auth.so.5 => > /usr/lib/x86_64-linux-gnu/libKF5Auth.so.5 > > (0x00007fd59f654000) > > libKF5GuiAddons.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5 > > (0x00007fd59f43b000) > > libfontconfig.so.1 => > > /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 > > (0x00007fd59f1fd000) > > libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 > > (0x00007fd59efe4000) > > libfreetype.so.6 => > /usr/lib/x86_64-linux-gnu/libfreetype.so.6 > > (0x00007fd59ed3e000) > > libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 > > (0x00007fd59eb36000) > > libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 > > (0x00007fd59e91c000) > > libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 > > (0x00007fd59e70c000) > > libXrender.so.1 => > /usr/lib/x86_64-linux-gnu/libXrender.so.1 > > (0x00007fd59e502000) > > libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 > > (0x00007fd59e2f0000) > > libKF5SonnetUi.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 > > (0x00007fd59e0ce000) > > libKF5SonnetCore.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5SonnetCore.so.5 > (0x00007fd59dead000) > > libKF5Completion.so.5 => > > /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5 > (0x00007fd59dc78000) > > libQt5Svg.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Svg.so.5 > > (0x00007fd59dc21000) > > libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 > > (0x00007fd59da1d000) > > libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 > > (0x00007fd59d817000) > > libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 > > (0x00007fd59d60f000) > > libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 > > (0x00007fd59d3a2000) > > libgraphite2.so.3 => > /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 > > (0x00007fd59d186000) > > libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 > > (0x00007fd59cf5d000) > > libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 > > (0x00007fd59cd2f000) > > libXdamage.so.1 => > /usr/lib/x86_64-linux-gnu/libXdamage.so.1 > > (0x00007fd59cb2c000) > > libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 > > (0x00007fd59c926000) > > libX11-xcb.so.1 => > /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 > > (0x00007fd59c724000) > > libxcb-glx.so.0 => > /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 > > (0x00007fd59c50b000) > > libxcb-dri2.so.0 => > /usr/lib/x86_64-linux-gnu/libxcb-dri2.so.0 > > (0x00007fd59c306000) > > libxcb-dri3.so.0 => > /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 > > (0x00007fd59c103000) > > libxcb-present.so.0 => > > /usr/lib/x86_64-linux-gnu/libxcb-present.so.0 > > (0x00007fd59bf00000) > > libxcb-sync.so.1 => > /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1 > > (0x00007fd59bcf9000) > > libxshmfence.so.1 => > /usr/lib/x86_64-linux-gnu/libxshmfence.so.1 > > (0x00007fd59baf6000) > > libXxf86vm.so.1 => > /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 > > (0x00007fd59b8f0000) > > libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 > > (0x00007fd59b6e2000) > > libicudata.so.55 => > /usr/lib/x86_64-linux-gnu/libicudata.so.55 > > (0x00007fd599c2b000) > > libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 > > (0x00007fd599baa000) > > libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 > > (0x00007fd599941000) > > libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 > > (0x00007fd59973c000) > > liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 > > (0x00007fd59951a000) > > libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 > > (0x00007fd599238000) > > libgpg-error.so.0 => > /lib/x86_64-linux-gnu/libgpg-error.so.0 > > (0x00007fd599025000) > > > > > > > > > > > > Gilles Caulier > > > > > > > > > _______________________________________________ > > > Digikam-devel mailing list > > > [hidden email] <mailto:[hidden email]> > <mailto:[hidden email] <mailto:[hidden email]>> > > > https://mail.kde.org/mailman/listinfo/digikam-devel > > > > > _______________________________________________ > > Digikam-devel mailing list > > [hidden email] <mailto:[hidden email]> > <mailto:[hidden email] <mailto:[hidden email]>> > > https://mail.kde.org/mailman/listinfo/digikam-devel > > > > > > > > > > _______________________________________________ > > Digikam-devel mailing list > > [hidden email] <mailto:[hidden email]> > > https://mail.kde.org/mailman/listinfo/digikam-devel > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] <mailto:[hidden email]> > https://mail.kde.org/mailman/listinfo/digikam-devel > > > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
2015-11-24 12:23 GMT+01:00 Richard Mortimer <[hidden email]>: On 24/11/2015 10:02, Gilles Caulier wrote: ok i take a look and comment. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
Richard, I commited some pathes, but not yet all, especially SQL statements fixes. Look also my new comment on this entry : The internal root tag auto creation is a serious dysfunction in Mysql support. Gilles 2015-11-24 12:53 GMT+01:00 Gilles Caulier <[hidden email]>:
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Building on Ubuntu Wily (was Re: [Digikam-users] Mysql/MariaDb database expert needs...)
|
|
About Mysql Internal Server and a customized place to store database data files (as SQlite), it's now implemented with this commit : Gilles 2015-11-24 16:19 GMT+01:00 Gilles Caulier <[hidden email]>:
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |