compile from svn problem

[Arnd Baecker-2]

Hi,

my usual install from svn
(using the script from http://www.digikam.org/?q=download/svn)
does not work.

The problem seems to be libjasper:

checking for jas_init in -ljasper... no
configure: WARNING: digiKam requires libjasper >= 1.7.0
configure: WARNING: digiKam requires libjasper >= 1.7.0; digiKam will not
be compiled.
configure: creating ./config.status
wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1261.
config.status: creating digikam/utilities/hotplug/digikam-download.desktop

However, libjasper is installed
digikam/lib $ ls -l | grep jasper
-rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
-rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la

and does contain jas_init:

nm libjasper.a | grep jas_init
jas_init.o:
00000010 T jas_init
[ptpcp3] /home/scratch/abaecker/SOFTWARE/digikam/lib $

What puzzles me is:
- all the other stuff (like exiv2) is in the same directory
  and is recognized by configure.
- this did not happen a few days ago
  (hmm, I did a small update on my machine, but this should not
   affect this ...)

How can I debug such configure problem in a systematic way?

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

[Fabien-5]

Hi,

Arnd Baecker wrote:

> my usual install from svn
> (using the script from http://www.digikam.org/?q=download/svn)
> does not work.
>
> The problem seems to be libjasper:
>
> checking for jas_init in -ljasper... no
> configure: WARNING: digiKam requires libjasper >= 1.7.0
> configure: WARNING: digiKam requires libjasper >= 1.7.0; digiKam will not
> be compiled.
> configure: creating ./config.status
> wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1261.
> config.status: creating digikam/utilities/hotplug/digikam-download.desktop
>
> However, libjasper is installed
> digikam/lib $ ls -l | grep jasper
> -rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
> -rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la
>
> and does contain jas_init:
>
> nm libjasper.a | grep jas_init
> jas_init.o:
> 00000010 T jas_init
> [ptpcp3] /home/scratch/abaecker/SOFTWARE/digikam/lib $
>
>
> How can I debug such configure problem in a systematic way?

Have you checked config.log ?

This is what I have on a fresh compile :

<<
configure:36358: checking for jas_init in -ljasper
configure:36388: gcc -o conftest -std=iso9899:1990 -W -Wall
-Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes
-Wwrite-strings -D_XOP
EN_SOURCE=500 -D_BSD_SOURCE -O2   -Wformat-security
-Wmissing-format-attribute  -DQT_THREAD_SUPPORT  -D_REENTRANT
-L/usr/lib -L/usr/share/qt3/lib
  -L/usr/X11R6/lib    -L/opt/digikam091/lib conftest.c -ljasper -ljasper
  >&5
configure:36394: $? = 0
configure:36397: test -z                         || test ! -s conftest.err
configure:36400: $? = 0
configure:36403: test -s conftest
configure:36406: $? = 0
configure:36419: result: yes
 >>

Maybe you should try manually the gcc to see what's wrong...

You can extract the small source code that is used (conftest.c) in
configure script.

I tried and gcc compiled fine in my case :)

Good luck.

--
Fabien

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

[Arnd Baecker]

On Thu, 1 Mar 2007, Fabien wrote:

> Hi,
>
> Arnd Baecker wrote:
> > my usual install from svn
> > (using the script from http://www.digikam.org/?q=download/svn)
> > does not work.
> >
> > The problem seems to be libjasper:
> >
> > checking for jas_init in -ljasper... no
> > configure: WARNING: digiKam requires libjasper >= 1.7.0
> > configure: WARNING: digiKam requires libjasper >= 1.7.0; digiKam will not
> > be compiled.
> > configure: creating ./config.status
> > wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1261.
> > config.status: creating digikam/utilities/hotplug/digikam-download.desktop
> >
> > However, libjasper is installed
> > digikam/lib $ ls -l | grep jasper
> > -rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
> > -rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la
> >
> > and does contain jas_init:
> >
> > nm libjasper.a | grep jas_init
> > jas_init.o:
> > 00000010 T jas_init
> > [ptpcp3] /home/scratch/abaecker/SOFTWARE/digikam/lib $
> >
> >
> > How can I debug such configure problem in a systematic way?

In the meantime I went for the brutal solution
and overrode configure's decision,
by adding after the check for jasper in `configure`

  have_jasper=yes
  LIB_JASPER="-ljasper"
  DO_NOT_COMPILE=""

Not nice, but the compile went fine after this
and digikam runs fine now ... ;-)

> Have you checked config.log ?

yes, I did ;-) -  however, thanks for mentioning it, after
the above worked, it was definitively
worth a second, *proper*, look:

configure:36873: checking for jas_init in -ljasper
configure:36908: gcc -o conftest -std=iso9899:1990 -W -Wall
-Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes
-Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2   -Wformat-security
-Wmissing-format-attribute  -DQT_THREAD_SUPPORT  -D_REENTRANT
-L/usr/share/qt3/lib     -L/home/abaecker/NBB/SOFTWARE/digikam/lib
conftest.c -ljasper -ljasper  >&5
/home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jas_stream.o): In
function `jas_stream_tmpfile':
/tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/base/jas_stream.c:368:
warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jpc_util.o): In
function `jpc_seq_norm':
/tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/jpc/jpc_util.c:164:
undefined reference to `sqrt'
/home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jpg_dec.o): In
function `jpg_decode':
/tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/jpg/jpg_dec.c:158:
undefined reference to `jpeg_std_error'
[...]
undefined reference to `ceil'
/home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jas_cm.o): In function
`gammafn':
/tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/base/jas_cm.c:881:
undefined reference to `pow'
collect2: ld returned 1 exit status
configure:36914: $? = 1
configure: failed program was:


> Maybe you should try manually the gcc to see what's wrong...
>
> You can extract the small source code that is used (conftest.c) in
> configure script.

Good point:
Adding  `-lm -ljpeg` to the end of the gcc statement
does cure the problem.

> I tried and gcc compiled fine in my case :)
>
> Good luck.

Thanks - this was very helpful!

So, what to do with this? Of course it is no problem
for me to add the `-lm -ljpeg` to the
 LIBS="-ljasper -ljasper $LIBS"
line in configure (Haven't tried this yet, though).
Maybe this is even the clean way,
but why did it work all the compiles before for me
and also right now for you?
(I am not sure if I really want to delve into the depths
of configure, so I will leave it at this.
Anyway, we have it archived here, if the problem comes up again
for some other user ...)

Thanks a lot,

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

On Thursday, 1. March 2007, Arnd Baecker wrote:

>
> On Thu, 1 Mar 2007, Fabien wrote:
>
> > Hi,
> >
> > Arnd Baecker wrote:
> > > my usual install from svn
> > > (using the script from http://www.digikam.org/?q=download/svn)
> > > does not work.
> > >
> > > The problem seems to be libjasper:
> > >
> > > checking for jas_init in -ljasper... no
> > > configure: WARNING: digiKam requires libjasper >= 1.7.0
> > > configure: WARNING: digiKam requires libjasper >= 1.7.0; digiKam will not
> > > be compiled.
> > > configure: creating ./config.status
> > > wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1261.
> > > config.status: creating digikam/utilities/hotplug/digikam-download.desktop
> > >
> > > However, libjasper is installed
> > > digikam/lib $ ls -l | grep jasper
> > > -rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
> > > -rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la

Your problem is here.  You only have a static version off libjasper
Install/build the shared one.

Achim

> > >
> > > and does contain jas_init:
> > >
> > > nm libjasper.a | grep jas_init
> > > jas_init.o:
> > > 00000010 T jas_init
> > > [ptpcp3] /home/scratch/abaecker/SOFTWARE/digikam/lib $
> > >
> > >
> > > How can I debug such configure problem in a systematic way?
>
> In the meantime I went for the brutal solution
> and overrode configure's decision,
> by adding after the check for jasper in `configure`
>
>   have_jasper=yes
>   LIB_JASPER="-ljasper"
>   DO_NOT_COMPILE=""
>
> Not nice, but the compile went fine after this
> and digikam runs fine now ... ;-)
>
> > Have you checked config.log ?
>
> yes, I did ;-) -  however, thanks for mentioning it, after
> the above worked, it was definitively
> worth a second, *proper*, look:
>
> configure:36873: checking for jas_init in -ljasper
> configure:36908: gcc -o conftest -std=iso9899:1990 -W -Wall
> -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes
> -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2   -Wformat-security
> -Wmissing-format-attribute  -DQT_THREAD_SUPPORT  -D_REENTRANT
> -L/usr/share/qt3/lib     -L/home/abaecker/NBB/SOFTWARE/digikam/lib
> conftest.c -ljasper -ljasper  >&5
> /home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jas_stream.o): In
> function `jas_stream_tmpfile':
> /tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/base/jas_stream.c:368:
> warning: the use of `tmpnam' is dangerous, better use `mkstemp'
> /home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jpc_util.o): In
> function `jpc_seq_norm':
> /tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/jpc/jpc_util.c:164:
> undefined reference to `sqrt'
> /home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jpg_dec.o): In
> function `jpg_decode':
> /tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/jpg/jpg_dec.c:158:
> undefined reference to `jpeg_std_error'
> [...]
> undefined reference to `ceil'
> /home/abaecker/NBB/SOFTWARE/digikam/lib/libjasper.a(jas_cm.o): In function
> `gammafn':
> /tmp/NEWTRYSVNALL/jasper-1.900.0/src/libjasper/base/jas_cm.c:881:
> undefined reference to `pow'
> collect2: ld returned 1 exit status
> configure:36914: $? = 1
> configure: failed program was:
>
>
> > Maybe you should try manually the gcc to see what's wrong...
> >
> > You can extract the small source code that is used (conftest.c) in
> > configure script.
>
> Good point:
> Adding  `-lm -ljpeg` to the end of the gcc statement
> does cure the problem.
>
> > I tried and gcc compiled fine in my case :)
> >
> > Good luck.
>
> Thanks - this was very helpful!
>
> So, what to do with this? Of course it is no problem
> for me to add the `-lm -ljpeg` to the
>  LIBS="-ljasper -ljasper $LIBS"
> line in configure (Haven't tried this yet, though).
> Maybe this is even the clean way,
> but why did it work all the compiles before for me
> and also right now for you?
> (I am not sure if I really want to delve into the depths
> of configure, so I will leave it at this.
> Anyway, we have it archived here, if the problem comes up again
> for some other user ...)
>
> Thanks a lot,
>
> Arnd
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>

--
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- [hidden email]
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

On Thu, 1 Mar 2007, Achim Bohnet wrote:

[...]

> > > > However, libjasper is installed
> > > > digikam/lib $ ls -l | grep jasper
> > > > -rw-r--r-- 1 abaecker abaecker 1266404 Mar  1 14:51 libjasper.a
> > > > -rwxr-xr-x 1 abaecker abaecker     817 Mar  1 14:51 libjasper.la
>
> Your problem is here.  You only have a static version off libjasper
> Install/build the shared one.

OK.
But why did I never have any problems before?
(I.e., the last months, since jasper was required
I happily ran svn with the above library ;-)

BTW, by default, the shared library is not built
(I use jasper-1.900.0.zip),  and one has to use
  ./configure --prefix=$DIGIKAMDEST --enable-shared
which will then lead to libjasper.so.1.0.0 + symbolic links.

Many thanks,

Arnd


P.S.: This reminds me, that the text at
http://www.digikam.org/?q=download/svn
should be updated.

Suggestion, after the "(download compile_exiv2.sh script)" block:

"""
Installation of
<a href="http://www.ece.uvic.ca/~mdadams/jasper/">libjasper</a>
(don't forget to replace DIGIKAMDEST value)

wget http://www.ece.uvic.ca/~mdadams/jasper/software/jasper-1.900.1.zip
unzip jasper-1.900.1.zip
cd jasper-1.900.1
export DIGIKAMDEST=/home/fabien/myopt
./configure --prefix=$DIGIKAMDEST --enable-shared
make
make install
cd ..
"""

Fabien, could you maybe add the above?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Fabien-5]

Hi,

Arnd Baecker wrote:
 >
> [...]
 >
> BTW, by default, the shared library is not built
> (I use jasper-1.900.0.zip),  and one has to use
>   ./configure --prefix=$DIGIKAMDEST --enable-shared
> which will then lead to libjasper.so.1.0.0 + symbolic links.

>
> P.S.: This reminds me, that the text at
> http://www.digikam.org/?q=download/svn
> should be updated.
>
> Suggestion, after the "(download compile_exiv2.sh script)" block:
 > [...]
> Fabien, could you maybe add the above?

Well, libjasper is not the only dependency of digiKam. So I added a new
"dependencies" page in download section with a note about the
"--enable-shared".

PS: I don't know what's wrong with drupal, but I have to fight each time
I want to edit the website : once I'm logged, half pages don't have the
edit button or sometime it disappears/reappears after a few minutes. The
problem is the same with all browsers :(

--
Fabien

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

[Gilles Caulier-4]

same problem here with M$ IE from vista.

Try to contact Tom...

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

[Arnd Baecker]

On Mon, 5 Mar 2007, Fabien wrote:

> Hi,
>
> Arnd Baecker wrote:
>  >
> > [...]
>  >
> > BTW, by default, the shared library is not built
> > (I use jasper-1.900.0.zip),  and one has to use
> >   ./configure --prefix=$DIGIKAMDEST --enable-shared
> > which will then lead to libjasper.so.1.0.0 + symbolic links.
>
> >
> > P.S.: This reminds me, that the text at
> > http://www.digikam.org/?q=download/svn
> > should be updated.
> >
> > Suggestion, after the "(download compile_exiv2.sh script)" block:
>  > [...]
> > Fabien, could you maybe add the above?
>
> Well, libjasper is not the only dependency of digiKam. So I added a new
> "dependencies" page in download section with a note about the
> "--enable-shared".

Very nice - thanks!

Still it might be helpful (also for users less experienced
in compiling) to have the full version I
suggested also at http://www.digikam.org/?q=download/svn
? Then it is more or less a straightforward sequence
of copy-and-paste + running the provided scripts.

Best, Arnd

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

[Fabien-5]

Hello,

Arnd Baecker wrote:
> On Mon, 5 Mar 2007, Fabien wrote:
>
> Very nice - thanks!
>
> Still it might be helpful (also for users less experienced
> in compiling) to have the full version I
> suggested also at http://www.digikam.org/?q=download/svn
> ? Then it is more or less a straightforward sequence
> of copy-and-paste + running the provided scripts.

Well, the fact is there are a lot of dependencies (more than 10 libs).
So, why this one and not all others ?

I put exiv2 because its evolution is important in digiKam. Other libs
can be installed once, or they are even provided with the distribution...

But, I added a notice at the top of the page about the dependencies.

--
Fabien

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

[Gilles Caulier-4]

Fabien,

I have just add the libkdcraw today. Libkdcraw is hosted into extragear/libs like libkexiv2

Gilles

2007/3/6, Fabien <[hidden email]>:

Hello,

Arnd Baecker wrote:
> On Mon, 5 Mar 2007, Fabien wrote:
>
> Very nice - thanks!
>
> Still it might be helpful (also for users less experienced
> in compiling) to have the full version I
> suggested also at http://www.digikam.org/?q=download/svn
> ? Then it is more or less a straightforward sequence
> of copy-and-paste + running the provided scripts.

Well, the fact is there are a lot of dependencies (more than 10 libs).
So, why this one and not all others ?

I put exiv2 because its evolution is important in digiKam. Other libs
can be installed once, or they are even provided with the distribution...

But, I added a notice at the top of the page about the dependencies.

--
Fabien

_______________________________________________
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

[Arnd Baecker]

On Tue, 6 Mar 2007, Fabien wrote:

> Hello,
>
> Arnd Baecker wrote:
> > On Mon, 5 Mar 2007, Fabien wrote:
> >
> > Very nice - thanks!
> >
> > Still it might be helpful (also for users less experienced
> > in compiling) to have the full version I
> > suggested also at http://www.digikam.org/?q=download/svn
> > ? Then it is more or less a straightforward sequence
> > of copy-and-paste + running the provided scripts.
>
> Well, the fact is there are a lot of dependencies (more than 10 libs).
> So, why this one and not all others ?

I perfectly understand, the only reason
is the unusual need for the "--shared-libs" option.
(which you do mention at http://www.digikam.org/?q=download/dependencies)

> I put exiv2 because its evolution is important in digiKam. Other libs
> can be installed once, or they are even provided with the distribution...
>
> But, I added a notice at the top of the page about the dependencies.

OK, that should do, I guess...

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