Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2240 - Curl Installation Lacks libidn.so Dependency

Attached to Project: Arch Linux
Opened by Clinton L. Warren (justdoro) - Sunday, 20 February 2005, 22:16 GMT
Last edited by Dale Blount (dale) - Monday, 21 February 2005, 12:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

After updating curl 7.13.0-1 via pacman -Suy, running curl from the command line produced the following error:

curl: error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory.

After running pacman -S libidn from the command line, curl produced the following output:

curl: try 'curl --help' or 'curl --manual' for more information.
This task depends upon

Closed by  dorphell (dorphell)
Tuesday, 22 February 2005, 16:57 GMT
Reason for closing:  Fixed
Comment by Ben Curry (beniro) - Monday, 21 February 2005, 17:42 GMT
Also, (I think it's the same problem) this effects apache in that it won't allow httpd to start up if you have the load php5 module line uncommented in httpd's config. It gives the following error:

Cannot load /usr/lib/apache/libphp5.so into server: libidn.so.11: cannot open shared object file: No such file or directory.

I fixed it by manually pacmanning libidn.
Comment by Daniel Butler (prune) - Monday, 21 February 2005, 22:20 GMT
It also affects clamav (freshclam in particular)
Comment by eliott (cactus) - Tuesday, 22 February 2005, 04:36 GMT
Yes, this is a nasty one.
Any reason why the curl update broke php curl support?
Why is libidn causing a problem when it never used to?
Comment by Jan de Groot (JGC) - Tuesday, 22 February 2005, 09:58 GMT
The maintainer that built the new curl has libidn on his system and didn't namcap the stuff before checking it in the repositories. Installing libidn by hand will fix all the problems.
Comment by dorphell (dorphell) - Tuesday, 22 February 2005, 16:49 GMT
Judd is to blame =) He has libidn installed and curl wrapped onto it like a leech. I'll recompile without libidn support

Loading...