Package: libcurl3-dev
Version: 7.13.1-1
Severity: normal

For some reason (which I haven't tracked down), the latest libcurl3-dev has
broken the curl behavior.  Below is the error message I get.  A brief
googling suggests that 'tld_strerror' and 'idna_strerror' ought to be in
libidn.  Might it be that libcurl is compiled with an ABI-incompatible
version of libidn11-dev?

configure:4606: checking for curl_global_init in -lcurl
configure:4636: gcc -o conftest  -O2   conftest.c -lcurl  -L/usr/lib -lcurl 
-lidn -lssl -lcrypto -ldl 
-lssl -lcrypto -ldl -lz  >&5
/usr/lib/libcurl.so: undefined reference to `tld_strerror'
/usr/lib/libcurl.so: undefined reference to `idna_strerror'
collect2: ld returned 1 exit status
configure:4642: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| 
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
| 
| /* Override any gcc2 internal prototype to avoid an error.  */
| #ifdef __cplusplus
| extern "C"
| #endif
| /* We use char because int might match the return type of a gcc2
|    builtin and then its argument prototype would still apply.  */
| char curl_global_init ();
| int
| main ()
| {
| curl_global_init ();
|   ;
|   return 0;
| }


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libcurl3-dev depends on:
ii  libc6-dev [libc-dev]        2.3.2.ds1-20 GNU C Library: Development Librari
ii  libcurl3                    7.13.1-1     Multi-protocol file transfer libra
ii  libidn11-dev                0.5.2-3      Development files GNU libidn, impl
ii  libssl-dev                  0.9.7e-2     SSL development libraries, header 
ii  zlib1g-dev                  1:1.2.2-3    compression library - development

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to