On Thursday 27 September 2007, Theppitak Karoonboonyanan wrote: > Package: kdelibs > Version: 4:3.5.7.dfsg.1-7 > Severity: wishlist > So far, libthai has secretly served Thai KDE users through the latter > method. However, this requires users to install libthai-dev, although > they don't want to compile any program against libthai and its > dependency. This is because the KLibLoader used to dlopen() it requires > *.la file. And this has just been removed in the lastest libthai, as it's > not so desirable to ship it, and none of libthai's reverse dependencies > require it any more. We have recently patched klibloader to also be able to dlopen so-files. Does it also work in the libthai case ? > To continue serving Thai KDE users, I think it should be explicitly > linked, by having kdelibs build-depend on libthai-dev, and passing > --with-libthai=yes it its configure options. If we could avoid libthai dependency, it would be preferred. > -- System Information: > Debian Release: lenny/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=th_TH.UTF-8, LC_CTYPE=th_TH.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash -- Do you know how can I do for booting the firewall from AutoCAD 4.8.5? You neither can install the memory of a DVD sendmail, nor must cancel a system for installing a controller to the FPU.
Attachment:
signature.asc
Description: This is a digitally signed message part.