asterisk users - Dec 2004 - Spandsp - Libtiff problem

Hello all,
I use Fedora 3, and I have compilation problem of SpanDsp , when
installaing spandsp, tiff warnings and errors generated and libunicall
generate "unresolved references....." 
Is the problem in my libtiff installation, spandsp.h or in tif_dir.h and
tiffiop.h? 
Are tif_dir.h and tiffiop.h  too old?
The solution provided by ?HO SIN? to ?Kaws? : 
>>> recompile libtiff from the downloaded tarball , 
When I recompile the libtiff , and execute ?rpm ?q libtiff? , it always
give the old version and the problem not resolved yet,
 
>>> so you will need to link /usr/lib/libtiff staff to
/usr/local/lib/libtiff staff.
How to link : is it ?ln /usr/lib/libtiff  /usr/local/lib/libtiff?
Or ?ln /usr/local/lib/libtiff   /usr/lib/libtiff?
Or other link method
 
Have Steve released the updated version of ?patch for new asterisk
versions? and ?L? problem for making asterisk ?
Thanks
 
Sofiane
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20041208/4950bcfb/attachment.htm

Hi,
> I use Fedora 3, and I have compilation problem of SpanDsp , when 
> installaing spandsp, tiff warnings and errors generated and libunicall 
> generate "unresolved references....."
Which is the same reason why spandsp is not packaged for Debian yet. The 
"p" in "tiffiop.h" means private, i.e. the t4.c and t30.c
files use
internal knowledge about libtiff's data structures that may (and 
actually do) change between versions. I have successfully compiled a 
working version for libtiff.so.3, however the current version is 4 and 
the tiffiop.h header shipped with that version has changed too much.

The correct solution, obviously, would be to use only public API calls. 
I am basically willing to do the work, however I lack the necessary 
insight into libtiff and the fax protocol to understand what spandsp is 
doing here (it looks to me as if a certain processing step in libtiff 
needs to be skipped).

    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 375 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20041208/734c29c8/signature.pgp

Hi
 
I think Simon's comment might be correct, but Sofiane's case seems only
a issue of inclusion and linking of libraries.
 
1. "rpm -q libtiff" does not change even after installation of new
libtiff from scratch since rpm registry tree does not affect in this case,
unless you compile a new RPM package from that tarball and install from that new
.rpm file, not by "make install".   Try to remove RPM package of
libtiff if you don't want to see the old version names.   rpm -e
libtiff<whatsoever>
 
2. make sure you compiled the correct version of libtiff.   Steve clearly
mentions that "Versions 3.5.7 and 3.6.0 seem to work OK." in his
instruction page of spandsp.
http://www.opencall.org/installing-spandsp.html
 
3. libtiff, with its default makefile, will be installed under /usr/local/lib/ ,
and spandsp's default look-in library path is /usr/lib.    so do "ln -s
/usr/local/lib/libtiff<whatsoever> 
/usr/lib/libtiff<whatsoever>".    You can either change the default
installation directory of libtiff or modify spandsp's look-in library
directory in Makefile, but I though it is easier.
 
goodluck

HOSIN

Sofiane Sakhri <ssakhri@yahoo.fr> wrote:


Hello all,

I use Fedora 3, and I have compilation problem of SpanDsp , when installaing
spandsp, tiff warnings and errors generated and libunicall generate
"unresolved references....."

Is the problem in my libtiff installation, spandsp.h or in tif_dir.h and
tiffiop.h?

Are tif_dir.h and tiffiop.h#63728; too old?

The solution provided by “HO SIN” to “Kaws” : 
>>> recompile libtiff from the downloaded tarball , 
When I recompile the libtiff , and execute “rpm –q libtiff” , it always give the
old version and the problem not resolved yet,

 
>>> so you will need to link /usr/lib/libtiff staff to
/usr/local/lib/libtiff staff.
How to link : is it “ln /usr/lib/libtiff #63728;/usr/local/lib/libtiff”

Or “ln /usr/local/lib/libtiff #63728;#63728;/usr/lib/libtiff”

Or other link method

 

Have Steve released the updated version of “patch for new asterisk versions” and
“L” problem for making asterisk ?

Thanks

 

Sofiane

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
		
---------------------------------
Do you Yahoo!?
 Meet the all-new My Yahoo! – Try it today! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20041209/9622fc66/attachment.htm