Closed GoogleCodeExporter closed 9 years ago
Original comment by pascal.m...@gmail.com
on 10 Jul 2012 at 4:43
Can you attach your config.log for reference? I assume this has to do with an
implicit dependency of libtiff(5?) as the binary does not directly reference
the library.
A base cygwin without libpng/libjpeg/libtiff compiles, but I haven't yet tried
to get a more complete version setup.
Original comment by jz...@google.com
on 10 Jul 2012 at 10:07
This seems to come from libtiff.la; cygwin's libtiff5 requires libjbig2, but no
dependency appears for libtiff-devel which contains a reference to libjbig in
/usr/lib/libtiff.la.
I'm not sure how to test the link done by libtool rather than the more direct
-ltiff currently being done in configure; there doesn't appear to be a
pkg-config file included in the cygwin config.
The workaround is straightforward enough, install libjbig-devel. I'll leave
this open, but lower the priority for now.
Original comment by jz...@google.com
on 10 Jul 2012 at 11:50
Here is the config.log file from the successul compilation after installation
of libjbig-devel from yesterday morning.
Original comment by mathias.schindler
on 11 Jul 2012 at 6:43
Attachments:
So based on the comment from jz, is this something that cygwin should fix
rather than webp's configuration file?
Original comment by mathias.schindler
on 11 Jul 2012 at 6:58
> So based on the comment from jz, is this something that cygwin should fix
rather than webp's configuration file?
Yes, I believe the main problem is with the cygwin package. If it's possible to
emulate the libtool link in the test then the configure could be made more
robust.
I didn't see any reports on the cygwin mailing lists about this. If I get a
chance I can try to prepare a bug report for cygwin-apps.
Below I added the test which succeeds from the configure test:
configure:11753: checking for TIFFGetVersion in -ltiff
configure:11778: gcc -o conftest.exe -g -O2 conftest.c -ltiff >&5
configure:11778: $? = 0
configure:11787: result: yes
Original comment by jz...@google.com
on 11 Jul 2012 at 5:59
I reported this to cygwin-apps [1].
[1] http://cygwin.com/ml/cygwin-apps/2012-08/msg00081.html
Original comment by jz...@google.com
on 22 Aug 2012 at 2:21
I can confirm that this is indeed a Cygwin packaging issue.
Original comment by yselkow...@gmail.com
on 22 Aug 2012 at 2:56
This has been fixed on the Cygwin side.
Original comment by jz...@google.com
on 23 Aug 2012 at 12:26
Thank you.
Original comment by mathias.schindler
on 23 Aug 2012 at 7:01
Original issue reported on code.google.com by
mathias.schindler
on 10 Jul 2012 at 10:00