AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.06.28 12:37 "Problems Building libtiff under Windows XP", by Kevin Myers
2007.06.28 16:28 "Re: Problems Building libtiff under Windows XP", by Kevin Myers

2007.06.28 16:28 "Re: Problems Building libtiff under Windows XP", by Kevin Myers

As described in my previous message in this thread, I couldn't get libtiff 
to build using the MS VC compiler.  So I decided to try using MinGW instead. 
Got a lot farther with that approach, but still ran into another problem 
here:

(Note: ran ./configure prior to running make)

libtool: compile: 
 gcc -DINSTALLDIR=\"/usr/local\" -DENABLE_RELOCATABLE -DHAVE_CONFIG_H -I. -I. 
 -I. -I. -I/c/GnuWin32/include -I/c/GnuWin32/include -g -O2 -Wall -W -MT 
tif_zip.lo -MD -MP -MF .deps/tif_zip.Tpo -c tif_zip.c -o tif_zip.o 
 >/dev/null 2>&1
make[2]: *** No rule to make target `libtiff-dllversion.lo', needed by 
`libtiff.la'.  Stop.
make[2]: Leaving directory 
`/c/GnuWin32/src/tiff/3.8.2/tiff-3.8.2-src/libtiff'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/c/GnuWin32/src/tiff/3.8.2/tiff-3.8.2-src/libtiff'
make: *** [all-recursive] Error 1

And as far as I can tell, the missing rule that it complains about really is 
missing from makefile and wasn't in makefile.in either.  I would be happy to 
add the rule myself, except that I have absolutely no clue what needs to 
happen in order to built this particular module (libtiff-dllversion.lo).

Can anyone out there give me a clue on this one?

BTW, I haven't yet received any replies to my previous help request, and 
sometimes I have problems with email to my subscribed address coming 
through.  So, if you can't reach me by simply replying to this message, then 
please give me another try using KevinMyers (at) austin.rr.com .

Thanks!
Kevin M.