Your message dated Sat, 07 Jun 2008 11:15:52 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#469454: libicu-dev: should also provide libicuuc.a etc
has caused the Debian Bug report #469454,
regarding libicu-dev: should also provide libicuuc.a etc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
469454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469454
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libicu-dev
Version: 3.8.1-1
Severity: normal
Hello,
I wanted to link my program statically, and was surprised to get
/usr/bin/ld: cannot find -licuuc
indeed, /usr/lib contains libsicuuc.a, not libicuuc.a. Is there a
reason for this? If the intent is just to include libicu statically
even when linking a program dynamically, then instead there should a
symlink libsicuuc.a pointing to libicuuc.a
Samuel
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages libicu-dev depends on:
ii libc6-dev [libc-dev] 2.7-6 GNU C Library: Development Librari
ii libicu38 3.8.1-1 International Components for Unico
libicu-dev recommends no packages.
-- no debconf information
--
Samuel
Who wants to remember that escape-x-alt-control-left shift-b puts you into
super-edit-debug-compile mode?
(Discussion in comp.os.linux.misc on the intuitiveness of commands, especially
Emacs.)
--- End Message ---
--- Begin Message ---
Samuel Thibault <[EMAIL PROTECTED]> wrote:
> I wanted to link my program statically, and was surprised to get
> /usr/bin/ld: cannot find -licuuc
> indeed, /usr/lib contains libsicuuc.a, not libicuuc.a. Is there a
> reason for this? If the intent is just to include libicu statically
> even when linking a program dynamically, then instead there should a
> symlink libsicuuc.a pointing to libicuuc.a
>
> Samuel
Look into this a little bit, it appears that all the static libraries
are called libs* and all the dynamic ones are named the same without
the s. So if you want to link statically, you have to link with
-lsicuuc insead of -licuuc. If you have a reason to believe
otherwise, please let me know. Otherwise, I'm considering this issue
resolved. Thanks for the report, and sorry it took me so long to
investigate.
--Jay
--- End Message ---
