0.10-beta1 Building error

This morning I downloaded the 0.10.0-beta1. I had never compiled the KDE4
branch. The cmake went OK and did not shout any error. During the make the
process stoped with this:

[ 20%] Building CXX object
digikam/CMakeFiles/digikam.dir/__/utilities/imageeditor/tools/imageresize.o
[ 20%] Building CXX object
digikam/CMakeFiles/digikam.dir/__/utilities/imageeditor/editor/editorwindow.o
In file included from
/home/paurullan/experiment/digikam-0.10.0-beta1/utilities/imageeditor/editor/editorwindow.cpp:93:
/home/paurullan/experiment/digikam-0.10.0-beta1/digikam/../utilities/imageeditor/tools/imageprint.h:44:2:
warning: #warning "TODO: KPrinter is disabled for KDE4.0";
/home/paurullan/experiment/digikam-0.10.0-beta1/utilities/imageeditor/editor/editorwindow.cpp:588:2:
warning: #warning "TODO: KPrinter is disabled for KDE4.0";
^[[2~[ 20%] Building CXX object
digikam/CMakeFiles/digikam.dir/__/utilities/imageeditor/editor/imageiface.o
Linking CXX shared library ../lib/libdigikam.so
CMakeFiles/digikam.dir/__/libs/greycstoration/greycstorationiface.o: In
function
`cimg_library::CImg<float>::greycstoration_run(cimg_library::CImg<unsigned
char> const&, float, float, float, float, float, float, float, float, float,
unsigned int, bool, unsigned int, unsigned int, unsigned int)':
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycstoration.h:218:
undefined reference to `pthread_create'
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycstoration.h:218:
undefined reference to `pthread_create'
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycstoration.h:218:
undefined reference to `pthread_create'
collect2: ld returned 1 exit status
make[2]: *** [lib/libdigikam.so.1.0.0] Error 1
make[1]: *** [digikam/CMakeFiles/digikam.dir/all] Error 2
make: *** [all] Error 2

What kind of information would you need?

Please CC on replies since I am not subscribed to the list.

--
"You say you are true evil? Shall I tell you what true evil is? It is to submit
to you. It is when we surrender our freedom, our dignity, instead of defying
you."
  - Captain Picard, ST:TNG 1.23 «Skin of evil»
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mark Purcell]

On Thu, 10 Jul 2008, =?UTF-8?Q?Pau_Rul=C2=B7lan_Ferragut?= wrote:
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycst
>oration.h:218: undefined reference to `pthread_create'
> collect2: ld returned 1 exit status
> make[2]: *** [lib/libdigikam.so.1.0.0] Error 1
> make[1]: *** [digikam/CMakeFiles/digikam.dir/all] Error 2
> make: *** [all] Error 2

Have a look at this thread:

http://mail.kde.org/pipermail/digikam-devel/2008-July/019672.html

and apply this patch:

--- digikam/CMakeLists.txt.orig 2008-07-07 22:21:31.000000000 +1000
+++ digikam/CMakeLists.txt      2008-07-07 21:57:05.000000000 +1000
@@ -117,6 +117,7 @@
                      ${KDCRAW_LIBRARIES}
                      ${KEXIV2_LIBRARIES}
                      ${KIPI_LIBRARIES}
+                      ${CMAKE_THREAD_LIBS_INIT}
               )  


Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Thu, Jul 10, 2008 at 10:04:52PM +1000, Mark Purcell wrote:
>On Thu, 10 Jul 2008, =?UTF-8?Q?Pau_Rul=C2=B7lan_Ferragut?= wrote:

>> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycst
>>oration.h:218: undefined reference to `pthread_create'
>> collect2: ld returned 1 exit status
>> make[2]: *** [lib/libdigikam.so.1.0.0] Error 1
>> make[1]: *** [digikam/CMakeFiles/digikam.dir/all] Error 2
>> make: *** [all] Error 2
>
>Have a look at this thread:
>
>http://mail.kde.org/pipermail/digikam-devel/2008-July/019672.html

Great, that was it.

Now I have another problem during the make:
[ 31%] Building C object
digikam/CMakeFiles/digikamdatabase.dir/__/libs/database/sqlite2/where.o
Linking CXX shared library ../lib/libdigikamdatabase.so
CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
function `CollectionManager':
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
undefined reference to `Solid::DeviceNotifier::instance()'
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:511:
undefined reference to `Solid::DeviceNotifier::instance()'
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
undefined reference to `Solid::DeviceNotifier::instance()'
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:511:
undefined reference to `Solid::DeviceNotifier::instance()'
CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
function `Digikam::CollectionManagerPrivate::actuallyListVolumes()':
/home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:243:
undefined reference to
`Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
const&)'



And a whole lot more. I know it must be my fault but because the cmake seemed
to work I am blind:

paurullan@silverymoon:~/experiment/digikam-0.10.0-beta1 % cmake .
-- Found Qt-Version 4.4.0 (using /usr/bin/qmake-qt4)
-- Found X11: /usr/lib/libX11.so
-- Found Automoc4: /usr/bin/automoc4
-- Found Perl: /usr/bin/perl
-- Found KDE 4.1 include dir: /usr/include
-- Found KDE 4.1 library dir: /usr/lib
-- Found KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler
-- Found KDE4 automoc: /usr/bin/automoc4
-- Found lcms version 1.16, /usr/lib/liblcms.so
-- Found JPEG: /usr/lib/libjpeg.so
-- Found PNG: /usr/lib/libpng.so
-- Found gphoto2: -L/usr/lib -lgphoto2_port;-L/usr/lib -lgphoto2 -lgphoto2_port
-lm
-- Found JPEG: /usr/lib/libjpeg.so
-- Found Jasper: /usr/lib/libjasper.so
-- Found Kdcraw library in cache: /usr/lib/libkdcraw.so
-- Found Kexiv2 library in cache: /usr/lib/libkexiv2.so
-- Found Kipi library in cache: /usr/lib/libkipi.so
-- Found KDE PIM libraries
-- Found LensFun: /usr/local/include
--
--  digiKam dependencies results -------------------
--  Qt4 SQL module found........... YES
--  libgphoto2 library found....... YES
--  libtiff library found.......... YES
--  libpng library found........... YES
--  libjasper library found........ YES
--  liblcms library found.......... YES
--  libkipi library found.......... YES
--  libkexiv2 library found........ YES
--  libkdcraw library found........ YES
--  libkdepimlibs library found.... YES
--  libmarblewiget library found... NO
--
--  digiKam will be compiled without geolocation using Marble widget support.
--
--  liblensfun library found....... YES
--  digiKam will be compiled...
-- ------------------------------------------------
--
-- Warning, you using a bugous GCC version ( 4.3.1)
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/paurullan/experiment/digikam-0.10.0-beta1


How may I add info?

There is no need to CC me, I subscribed again to the list.

--
"You say you are true evil? Shall I tell you what true evil is? It is to submit
to you. It is when we surrender our freedom, our dignity, instead of defying
you."
  - Captain Picard, ST:TNG 1.23 «Skin of evil»
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

2008/7/11 Pau Ruŀlan Ferragut <[hidden email]>:

> On Thu, Jul 10, 2008 at 10:04:52PM +1000, Mark Purcell wrote:
>>On Thu, 10 Jul 2008, =?UTF-8?Q?Pau_Rul=C2=B7lan_Ferragut?= wrote:
>
>>> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/greycstoration/greycst
>>>oration.h:218: undefined reference to `pthread_create'
>>> collect2: ld returned 1 exit status
>>> make[2]: *** [lib/libdigikam.so.1.0.0] Error 1
>>> make[1]: *** [digikam/CMakeFiles/digikam.dir/all] Error 2
>>> make: *** [all] Error 2
>>
>>Have a look at this thread:
>>
>>http://mail.kde.org/pipermail/digikam-devel/2008-July/019672.html
>
> Great, that was it.
>
> Now I have another problem during the make:
> [ 31%] Building C object
> digikam/CMakeFiles/digikamdatabase.dir/__/libs/database/sqlite2/where.o
> Linking CXX shared library ../lib/libdigikamdatabase.so
> CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
> function `CollectionManager':
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
> undefined reference to `Solid::DeviceNotifier::instance()'
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:511:
> undefined reference to `Solid::DeviceNotifier::instance()'
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
> undefined reference to `Solid::DeviceNotifier::instance()'
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:511:
> undefined reference to `Solid::DeviceNotifier::instance()'
> CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
> function `Digikam::CollectionManagerPrivate::actuallyListVolumes()':
> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:243:
> undefined reference to
> `Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
> const&)'
>

Are you installed libsolid from KDE4 ?

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

2008/7/11 Gilles Caulier <caulier.gilles at gmail.com>:
> 2008/7/11 Pau Ruŀlan Ferragut <paurullan at bulma.net>:

>> Now I have another problem during the make:
>> [ 31%] Building C object
>> digikam/CMakeFiles/digikamdatabase.dir/__/libs/database/sqlite2/where.o
>> Linking CXX shared library ../lib/libdigikamdatabase.so
>> CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
>> function `CollectionManager':
>> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
>> undefined reference to `Solid::DeviceNotifier::instance()'

> Are you installed libsolid from KDE4 ?

I am on Debian and here there is no libsolid package. The kdelibs5 and
kdelibs5-dev packages
seem to have the files.

root@silverymoon:~/experiment/digikam-0.10.0-beta1 # dpkg -L kdelibs5
| grep solid
/usr/lib/libsolid.so.4.1.0
/usr/lib/libsolid.so.4
root@silverymoon:~/experiment/digikam-0.10.0-beta1 # dpkg -L
kdelibs5-dev | grep solid
/usr/include/solid
/usr/include/solid/solidnamespace.h
/usr/include/solid/networking.h
/usr/include/solid/opticaldisc.h
/usr/include/solid/video.h
/usr/include/solid/devicenotifier.h
/usr/include/solid/storagevolume.h
/usr/include/solid/networkinterface.h
/usr/include/solid/dvbinterface.h
/usr/include/solid/acadapter.h
/usr/include/solid/predicate.h
/usr/include/solid/button.h
/usr/include/solid/genericinterface.h
/usr/include/solid/block.h
/usr/include/solid/solid_export.h
/usr/include/solid/processor.h
/usr/include/solid/portablemediaplayer.h
/usr/include/solid/storageaccess.h
/usr/include/solid/audiointerface.h
/usr/include/solid/opticaldrive.h
/usr/include/solid/storagedrive.h
/usr/include/solid/powermanagement.h
/usr/include/solid/battery.h
/usr/include/solid/camera.h
/usr/include/solid/deviceinterface.h
/usr/include/solid/device.h
/usr/lib/libsolid.so

Any idea or Debian user?

--
Do not be too quick to decide what is impossible.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

On Fri, 11 Jul 2008, [UTF-8] Pau Rul·lan Ferragut wrote

> 2008/7/11 Gilles Caulier <caulier.gilles at gmail.com>:
> > 2008/7/11 Pau Ruŀlan Ferragut <paurullan at bulma.net>:
>
> >> Now I have another problem during the make:
> >> [ 31%] Building C object
> >> digikam/CMakeFiles/digikamdatabase.dir/__/libs/database/sqlite2/where.o
> >> Linking CXX shared library ../lib/libdigikamdatabase.so
> >> CMakeFiles/digikamdatabase.dir/__/libs/database/collectionmanager.o: In
> >> function `CollectionManager':
> >> /home/paurullan/experiment/digikam-0.10.0-beta1/libs/database/collectionmanager.cpp:506:
> >> undefined reference to `Solid::DeviceNotifier::instance()'
>
> > Are you installed libsolid from KDE4 ?
>
> I am on Debian and here there is no libsolid package. The kdelibs5 and
> kdelibs5-dev packages
> seem to have the files.

almost ... ;-)

> root@silverymoon:~/experiment/digikam-0.10.0-beta1 # dpkg -L kdelibs5
> | grep solid
> /usr/lib/libsolid.so.4.1.0
> /usr/lib/libsolid.so.4

It misses /usr/lib/libsolid.so which is a symbolic link to
/usr/lib/libsolid.so.4
You should get this by installing
kdelibs5-dev

HTH, Arnd
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mark Purcell]

On Fri, 11 Jul 2008, =?UTF-8?Q?Pau_Rul=C2=B7lan_Ferragut?= wrote:
> > Are you installed libsolid from KDE4 ?
>
> I am on Debian and here there is no libsolid package. The kdelibs5 and
> kdelibs5-dev packages
> seem to have the files.

The depends I have for the upcoming Debian pacakge are:

Build-Depends: cdbs, debhelper (>= 5), cmake (>= 2.6),
 libqt4-dev (>= 4.3), kdelibs5-dev,
 libgphoto2-2-dev (>= 2.4),
 libkipi5-dev, libkexiv2-6-dev, libkdcraw5-dev,
 liblcms1-dev, libtiff4-dev, libpng12-dev,
 libjasper-dev,
 kdepimlibs5-dev, libmarble-dev,
 libsqlite3-dev,
 libltdl3-dev

I can confirm that this builds on a Debian environment.

Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Fri, Jul 11, 2008 at 10:27 AM, Mark Purcell <msp at debian.org> wrote:
> On Fri, 11 Jul 2008, =?UTF-8?Q?Pau_Rul=C2=B7lan_Ferragut?= wrote:

>> > Are you installed libsolid from KDE4 ?
>>
>> I am on Debian and here there is no libsolid package. The kdelibs5 and
>> kdelibs5-dev packages
>> seem to have the files.
>
> The depends I have for the upcoming Debian pacakge are:
>
> Build-Depends: cdbs, debhelper (>= 5), cmake (>= 2.6),
>  libqt4-dev (>= 4.3), kdelibs5-dev,
>  libgphoto2-2-dev (>= 2.4),
>  libkipi5-dev, libkexiv2-6-dev, libkdcraw5-dev,
>  liblcms1-dev, libtiff4-dev, libpng12-dev,
>  libjasper-dev,
>  kdepimlibs5-dev, libmarble-dev,
>  libsqlite3-dev,
>  libltdl3-dev
>
> I can confirm that this builds on a Debian environment.

Now I am completely confused. I have all those packages installed and
happens the same error. I installed all them in another machine and
the same thing happened.

Any hint or idea?

--
Do not be too quick to decide what is impossible.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> Now I am completely confused. I have all those packages installed and
> happens the same error. I installed all them in another machine and
> the same thing happened.
>
> Any hint or idea?

Does it help if you add

                      ${KDE4_SOLID_LIBS}

to line 150 of digikam/CMakeLists.txt:

TARGET_LINK_LIBRARIES(digikamdatabase
                      digikam
                      ${QT_QTSQL_LIBRARY}
                      ${KDE4_SOLID_LIBS}
                     )
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Fri, Jul 11, 2008 at 03:06:01PM +0200, Marcel Wiesweg wrote:

>> Now I am completely confused. I have all those packages installed and
>> happens the same error. I installed all them in another machine and the same
>> thing happened.

>> Any hint or idea?
>
>Does it help if you add
>
>                      ${KDE4_SOLID_LIBS}
>
>to line 150 of digikam/CMakeLists.txt:
>
>TARGET_LINK_LIBRARIES(digikamdatabase
>                      digikam
>                      ${QT_QTSQL_LIBRARY}
>                      ${KDE4_SOLID_LIBS}
>                     )

OK, that worked.

I had to install libqt4-sql-sqlite later when I runned digikam for the first
time.

Then it crashed with this: (I am beginning to feel like a pain for you!)

Application: digiKam (digikam), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb4ac6720 (LWP 14672)]
[New Thread 0xb294ab90 (LWP 14691)]
[New Thread 0xb2149b90 (LWP 14690)]
[New Thread 0xb3478b90 (LWP 14673)]
0xb7f1b424 in __kernel_vsyscall ()
[Current thread is 0 (LWP 14672)]

Thread 4 (Thread 0xb3478b90 (LWP 14673)):
#0  0xb7f1b424 in __kernel_vsyscall ()
#1  0xb5827015 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb5f8d332 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0x08297d05 in Digikam::ScanController::run (this=0x9da95b0)
    at
    /home/paurullan/experiment/digikam-0.10.0-beta1/digikam/scancontroller.cpp:299
#4  0xb5f8c322 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb58234b0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#6  0xb555938e in clone () from /lib/i686/cmov/libc.so.6

Thread 3 (Thread 0xb2149b90 (LWP 14690)):
#0  0xb7f1b424 in __kernel_vsyscall ()
#1  0xb5827015 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb5f8d332 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb7cb0fd2 in Digikam::LoadSaveThread::run (this=0x9e1c538)
    at
    /home/paurullan/experiment/digikam-0.10.0-beta1/libs/threadimageio/loadsavethread.cpp:124
#4  0xb5f8c322 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb58234b0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#6  0xb555938e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb294ab90 (LWP 14691)):
#0  0xb7f1b424 in __kernel_vsyscall ()
#1  0xb5827015 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/cmov/libpthread.so.0
#2  0xb5f8d332 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb7cb0fd2 in Digikam::LoadSaveThread::run (this=0x9dd4130)
    at
    /home/paurullan/experiment/digikam-0.10.0-beta1/libs/threadimageio/loadsavethread.cpp:124
#4  0xb5f8c322 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb58234b0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#6  0xb555938e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4ac6720 (LWP 14672)):
#0  0xb7f1b424 in __kernel_vsyscall ()
#1  0xb5514dc6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb5514bdf in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7673936 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
#0  0xb7f1b424 in __kernel_vsyscall ()


--
"You say you are true evil? Shall I tell you what true evil is? It is to submit
to you. It is when we surrender our freedom, our dignity, instead of defying
you."
  - Captain Picard, ST:TNG 1.23 «Skin of evil»
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

>
> OK, that worked.

Applied to SVN

>
> I had to install libqt4-sql-sqlite later when I runned digikam for the
> first time.
>
> Then it crashed with this: (I am beginning to feel like a pain for you!)
>
> Application: digiKam (digikam), signal SIGSEGV
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb4ac6720 (LWP 14672)]
> [New Thread 0xb294ab90 (LWP 14691)]
> [New Thread 0xb2149b90 (LWP 14690)]
> [New Thread 0xb3478b90 (LWP 14673)]
> 0xb7f1b424 in __kernel_vsyscall ()
> [Current thread is 0 (LWP 14672)]

The other threads are only waiting, this thread seems to be crashing, but here
is no suitable backtrace.
Have you tried running digikam under gdb?
(http://www.digikam.org/drupal/contrib, "To make a backtrace with GDB use
following command: ")

Marcel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

On Fri, 11 Jul 2008, Pau [utf-8] RuÅ^@lan Ferragut wrote:

[...]

> I had to install libqt4-sql-sqlite later when I runned digikam for the first
> time.

Shouldn't this dependency be checked during the cmake step?
In other words: I think we should check this... ;-)

Could one use FindSqlite.cmake for this?
(Or will this only find a system sqlite in contrast to the QT sqlite ?)

Best, Arnd
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Fri, Jul 11, 2008 at 04:30:49PM +0200, Marcel Wiesweg wrote:

>Have you tried running digikam under gdb?

The end of the running:

System Path: ""
Plugin System Path: ""
===================
"core"  -  "/core"
Plugin Failure:  "core"  is not a valid Marble Plugin:
"The file '/core' is not a valid Qt plugin."
"initrd.img"  -  "/boot/initrd.img-2.6.25-2-686"
Plugin Failure:  "initrd.img"  is not a valid Marble Plugin:
"The file '/boot/initrd.img-2.6.25-2-686' is not a valid Qt plugin."
"initrd.img.old"  -  "/boot/initrd.img-2.6.24-1-686"
Plugin Failure:  "initrd.img.old"  is not a valid Marble Plugin:
"The file '/boot/initrd.img-2.6.24-1-686' is not a valid Qt plugin."
"vmlinuz"  -  "/boot/vmlinuz-2.6.25-2-686"
Plugin Failure:  "vmlinuz"  is not a valid Marble Plugin:
"The file '/boot/vmlinuz-2.6.25-2-686' is not a valid Qt plugin."
"vmlinuz.old"  -  "/boot/vmlinuz-2.6.24-1-686"
Plugin Failure:  "vmlinuz.old"  is not a valid Marble Plugin:
"The file '/boot/vmlinuz-2.6.24-1-686' is not a valid Qt plugin."
cannot open ""  for reading
fstat error
mmap error for input

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4ad3720 (LWP 24874)]
0xb579e8c6 in ?? () from /usr/lib/libmarblewidget.so.4


(gdb) bt
#0  0xb579e8c6 in ?? () from /usr/lib/libmarblewidget.so.4
#1  0xbfe43d50 in ?? ()
#2  0xb5813b3a in ?? () from /usr/lib/libmarblewidget.so.4
#3  0x00000001 in ?? ()
#4  0xffffffff in ?? ()
#5  0x00000000 in ?? ()


I will try to build it without marble

--
"You say you are true evil? Shall I tell you what true evil is? It is to submit
to you. It is when we surrender our freedom, our dignity, instead of defying
you."
  - Captain Picard, ST:TNG 1.23 «Skin of evil»
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> > I had to install libqt4-sql-sqlite later when I runned digikam for the
> > first time.
>
> Shouldn't this dependency be checked during the cmake step?
> In other words: I think we should check this... ;-)
>
> Could one use FindSqlite.cmake for this?
> (Or will this only find a system sqlite in contrast to the QT sqlite ?)

That's the point. You can have SQLite well installed, we need the Qt plugin.
There is no CMake file currently for that. I dont know a tool to check for the
existence of a Qt plugin.

It's a runtime dependency and we have now clear error messages.
It's clear that once distributions make packages, they must make the Qt plugin
a hard dependency, otherwise their package has a bug.

>
> Best, Arnd
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Fri, Jul 11, 2008 at 5:31 PM, Pau Ruŀlan Ferragut
<[hidden email]> wrote:
> On Fri, Jul 11, 2008 at 04:30:49PM +0200, Marcel Wiesweg wrote:

>>Have you tried running digikam under gdb?
>
> The end of the running:
>
> System Path: ""
> Plugin System Path: ""
> ===================
> "core"  -  "/core"
> Plugin Failure:  "core"  is not a valid Marble Plugin:
> "The file '/core' is not a valid Qt plugin."
> "initrd.img"  -  "/boot/initrd.img-2.6.25-2-686"
> Plugin Failure:  "initrd.img"  is not a valid Marble Plugin:
> "The file '/boot/initrd.img-2.6.25-2-686' is not a valid Qt plugin."
> "initrd.img.old"  -  "/boot/initrd.img-2.6.24-1-686"
> Plugin Failure:  "initrd.img.old"  is not a valid Marble Plugin:
> "The file '/boot/initrd.img-2.6.24-1-686' is not a valid Qt plugin."
> "vmlinuz"  -  "/boot/vmlinuz-2.6.25-2-686"
> Plugin Failure:  "vmlinuz"  is not a valid Marble Plugin:
> "The file '/boot/vmlinuz-2.6.25-2-686' is not a valid Qt plugin."
> "vmlinuz.old"  -  "/boot/vmlinuz-2.6.24-1-686"
> Plugin Failure:  "vmlinuz.old"  is not a valid Marble Plugin:
> "The file '/boot/vmlinuz-2.6.24-1-686' is not a valid Qt plugin."
> cannot open ""  for reading
> fstat error
> mmap error for input
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb4ad3720 (LWP 24874)]
> 0xb579e8c6 in ?? () from /usr/lib/libmarblewidget.so.4
>
>
> (gdb) bt
> #0  0xb579e8c6 in ?? () from /usr/lib/libmarblewidget.so.4
> #1  0xbfe43d50 in ?? ()
> #2  0xb5813b3a in ?? () from /usr/lib/libmarblewidget.so.4
> #3  0x00000001 in ?? ()
> #4  0xffffffff in ?? ()
> #5  0x00000000 in ?? ()
>
>
> I will try to build it without marble

It builds and runs without marble.

--
Do not be too quick to decide what is impossible.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

On Sat, Jul 12, 2008 at 05:52:45PM +0200, Arnd Baecker wrote:
>On Sat, 12 Jul 2008, [UTF-8] Pau Rul·lan Ferragut wrote:
>
>[...]
>> It builds and runs without marble.
>
>FWIW: I did not have any problems with building and running
>with an svn check-out of marble.
>Maybe there is some issue with the /usr/lib/libmarblewidget.so
>(is this a system provided one?)

Yes, everything but the digikam-0.10-beta1 source is from Debian.


--
"You say you are true evil? Shall I tell you what true evil is? It is to submit
to you. It is when we surrender our freedom, our dignity, instead of defying
you."
  - Captain Picard, ST:TNG 1.23 «Skin of evil»
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel