Bug#360780: build: powerpc problem with sign of char
Jorg, I want to clear up a few things in this bug report: 1. It's completely pointless Debian enabling -Wextra in the packaging when the number of false positives is so incredibly large. 2. Discriminating between false positives and real bugs needs someone to go through the entire codebase, normally upstream. 3. upstream always build with -Werror and -Wall. Adding -Wextra will halt the build until every false positive is "handled" with large numbers of spurious compiler flags and workarounds that add nothing to the codebase or functionality. All these false cases have to be hidden before the true number of real bugs even becomes clear. Breaking the build in that way will simply not be tolerated upstream. 4. Before -Wextra is used, -Wunused MUST be disabled, simply because Gtk prototypes commonly involve passing unused arguments in order to reduce the total number of prototype declarations required. Result? -Wextra is simply not useful to gnucash, upstream, and is also unhelpful to Debian. Until someone convinces upstream that it is worth using -Wextra, nothing is going to change. I am not going to be the one to get shot down for suggesting it. :-) If you are willing to undertake this task and you are willing to spend the time creating patches for the real bugs WITHOUT enabling -Wextra for everyone else upstream, then those patches would be welcome upstream. >> >> -Wextra DOES generate errors under -Werror >> > >> > Who enabled -Werror? >> >> Upstream - sometime during the gnome2 transition. > > No. That's not true. Look at > http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=2.0.1-1&arch=powerpc&stamp=1155098349&file=log&as=raw That's the Debian build - the problems you report can only realistically be addressed upstream and upstream will not accept building without -Werror. You can try and build SVN without -Werror but upstream will usually reject patches that are created from a build made without -Werror. > >> One final comment: Check out the use of a more specific combination of >> -W options that highlight the real issues as compared to the pointless >> warnings. In particular, look at -Wsign-compare with -Wconversion >> *without* using -Wunused. > > I did not enable -Wunused. That's a default option. Same source as above. It still needs to be removed. -Wsign-compare is STILL a better solution than -Wextra too. > One final comment: > ,[ Debian policy 10.1 ]--- > By default, when a package is being built, any binaries created should > include debugging information, as well as being compiled with > optimization. You should also turn on as many reasonable compilation > warnings as possible; this makes life easier for porters, who can then > look at build logs for possible problems. For the C programming You omitted the rest of that line: For the C programming language, this means the following compilation parameters should be used: CC = gcc CFLAGS = -O2 -g -Wall # sane warning options vary between programs LDFLAGS = # none INSTALL = install -s # (or use strip on the files in debian/tmp) The point is that -Wextra is not specified there, even as an example, and that policy clearly notes that SANE warning options vary between programs. GnuCash does build with -Wall. My point is that -Wextra is NOT a sane option for gnucash - it probably isn't a sane option for many Gtk applications. The only solution is for you to either convince upstream to use it or supply patches to upstream that fix all the real bugs without adding bloat to handle false positives. > BTW: You build without optimization. And you do not support > DEB_BUILD_OPTIONS. Should I send a new bugreport? Yes. FYI I have used -Wextra with -Werror and -Wall on a different project and I found that it highlighted no real bugs and a dozen or more false positives. I have since removed -Wextra from the upstream build for that project. Instead, I use -Wunused (it's not a Gtk project) and a few other specific warnings which -Werror promotes to errors, should they occur. IMHO, -Wextra is just that - extra. It is sometimes useful during upstream development but not an option I would remotely consider introducing into any upstream build. Using -Wextra locally is fine if it helps identify a few real bugs but it is just too unreliable to be made a permanent component of an upstream (or Debian) build configuration. I strongly recommend that any real bugs in gnucash are identified using other, more specific, warnings like -Wsign-compare. I propose that this bug report should be marked "won't fix". If you identify real bugs with other options (like -Wsign-compare), please submit new bug reports with patches. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Bug#360780: build: powerpc problem with sign of char
Hello Neil, Neil Williams schrieb am Tue 15. Aug, 19:36 (+0100): > Jörg Sommer wrote: > > Neil Williams schrieb am Mon 14. Aug, 14:38 (+0100): > >> Jörg Sommer wrote: > >>> Hello Neil, > 2. -Wextra is *not supported* by gnucash and errors are to be expected. > Don't use it. > >>> -Wextra does not generate any errors. It warns about common cases where > >>> errors can araise. > >> -Wextra DOES generate errors under -Werror > > > > Who enabled -Werror? > > Upstream - sometime during the gnome2 transition. No. That's not true. Look at http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=2.0.1-1&arch=powerpc&stamp=1155098349&file=log&as=raw > One final comment: Check out the use of a more specific combination of > -W options that highlight the real issues as compared to the pointless > warnings. In particular, look at -Wsign-compare with -Wconversion > *without* using -Wunused. I did not enable -Wunused. That's a default option. Same source as above. One final comment: ,[ Debian policy 10.1 ]--- | By default, when a package is being built, any binaries created should | include debugging information, as well as being compiled with | optimization. You should also turn on as many reasonable compilation | warnings as possible; this makes life easier for porters, who can then | look at build logs for possible problems. For the C programming ` And the same was suggested in the announcement of GCC 4.1 at beginning of June. BTW: You build without optimization. And you do not support DEB_BUILD_OPTIONS. Should I send a new bugreport? Bye, Jörg. -- [dpkg] We are the apt. Resistance is futile. You will be packaged. pgpusA3GLUuP8.pgp Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
Jörg Sommer wrote: > Neil Williams schrieb am Mon 14. Aug, 14:38 (+0100): >> Jörg Sommer wrote: >>> Hello Neil, 2. -Wextra is *not supported* by gnucash and errors are to be expected. Don't use it. >>> -Wextra does not generate any errors. It warns about common cases where >>> errors can araise. >> -Wextra DOES generate errors under -Werror > > Who enabled -Werror? Upstream - sometime during the gnome2 transition. >> I'd also recommend broaching this directly with gnucash upstream over >> IRC or the gnucash-devel mailing list. > > I will do that. Thanks - let me know how you get on. > Thanks for telling me your thoughts about this issue. Close this bugs as > you like. It's OK to leave for now. >> -Wextra is fine, IMHO, for small utilities and small libraries, like >> libqof1. Having reviewed it in that situation, I would not be willing to >> recommend adopting it for a large app like gnucash. YMMV. > > I think tons of lines of code are not an excuse to lower code quality and > ignore minor issues. But these are two opinions of two different people. I agree it's not excuse for lower code quality - I disagree that -Wextra is a *reliable* indicator, especially when it concerns applications that use a lot of function prototypes where one or more arguments may often be unused. Not using a provided variable is *not* an indicator of lower code quality. One final comment: Check out the use of a more specific combination of -W options that highlight the real issues as compared to the pointless warnings. In particular, look at -Wsign-compare with -Wconversion *without* using -Wunused. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Bug#360780: build: powerpc problem with sign of char
Jörg Sommer <[EMAIL PROTECTED]> writes: > Do you know why Thomas do not build with these libs? Are there any > problems? It was not an intentional decision, and I plan to build with them on the next upload. Thomas
Bug#360780: build: powerpc problem with sign of char
Hello Neil, Neil Williams schrieb am Mon 14. Aug, 14:38 (+0100): > Jörg Sommer wrote: > > Hello Neil, > >> 2. -Wextra is *not supported* by gnucash and errors are to be expected. > >> Don't use it. > > > > -Wextra does not generate any errors. It warns about common cases where > > errors can araise. > > -Wextra DOES generate errors under -Werror Who enabled -Werror? > I'd also recommend broaching this directly with gnucash upstream over > IRC or the gnucash-devel mailing list. I will do that. Thanks for telling me your thoughts about this issue. Close this bugs as you like. > -Wextra is fine, IMHO, for small utilities and small libraries, like > libqof1. Having reviewed it in that situation, I would not be willing to > recommend adopting it for a large app like gnucash. YMMV. I think tons of lines of code are not an excuse to lower code quality and ignore minor issues. But these are two opinions of two different people. Bye bye, Jörg. -- Real programmers don't comment their code. It was hard to write, it should be hard to understand. pgpEvm4Avzl4M.pgp Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
Jörg Sommer wrote: > Hello Neil, >> 2. -Wextra is *not supported* by gnucash and errors are to be expected. >> Don't use it. > > -Wextra does not generate any errors. It warns about common cases where > errors can araise. That doesn't change the fact that upstream does not support it. :-) -Wextra DOES generate errors under -Werror because the warnings from -Wextra are promoted. Some of these "errors" are spurious, others require *large* amounts of changes to the codebase to prevent. I, for one, don't fancy the idea of recommending to upstream that hundreds of __attribute__ ((unused)) markers are added to the upstream code. ;-) >> You only have a problem because of extra compiler flags > > I don't have a problem. I point out some sources of problems before they > arise. But -Wextra is just that: extra. It is *not* a reliable indicator of problems, it just raises possibles and whereas some are worth changing, many are simply spurious (like unused above). A common case for unused is when a library defines a prototype for a callback but the specific instance doesn't use one or more of the prototype variables. We can't change the prototype, so the above unused kludge would be needed for -Wextra. Lines and lines of extra code making the codebase even less readable. Hmm, don't think upstream would like that. Stop using -Wextra and everything is fine. It's your choice but you haven't convinced me, yet, that it's worth getting flamed by upstream for suggesting it! -Wextra is *not* a Debian concern. It can only be implemented upstream because of the immense number of changes required. > For example, look at gnc-date.c:234. The function name timespec_abs() > suggests the value should be made a positive value, if it's negative. But > the comparison "retval.tv_sec < 0" is always false, due to tv_sec is > unsigned according gnc-date.h: Maybe, but is it worth the rest of the problems? I can only recommend that you isolate the *real* errors from the spurious warnings promoted to errors and create some patches. I can't see upstream implementing -Wextra for everyone. I'd also recommend broaching this directly with gnucash upstream over IRC or the gnucash-devel mailing list. PS gnc-date only now exists in gncqof, libqof1 has overhauled all date and time handling. I'm experimenting with -Wextra for libqof1. I'm not doubting it raises a few useful points, but applications like gnucash are not going to like it. -Wextra is fine, IMHO, for small utilities and small libraries, like libqof1. Having reviewed it in that situation, I would not be willing to recommend adopting it for a large app like gnucash. YMMV. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Bug#360780: build: powerpc problem with sign of char
Hello Neil,
Neil Williams schrieb am Sun 13. Aug, 22:56 (+0100):
> Jörg Sommer wrote:
>
> I see now you mentioned originally:
> > compiling gnucash with -Wall and -Wextra brings some warnings like this:
>
> So, here's a new start for this bug:
> 1. -Wall is already set, don't set it again.
OK, but this should not change anything.
> 2. -Wextra is *not supported* by gnucash and errors are to be expected.
> Don't use it.
-Wextra does not generate any errors. It warns about common cases where
errors can araise.
> > Because the build log is really big (3.7MB) I put it at
> > http://www.minet.uni-jena.de/~joergs/gc.build.log
>
> Compare with the Debian build log for powerpc:
>
> http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=2.0.1-1&arch=powerpc&stamp=1155098349&file=log&as=raw
>
> You only have a problem because of extra compiler flags
I don't have a problem. I point out some sources of problems before they
arise.
For example, look at gnc-date.c:234. The function name timespec_abs()
suggests the value should be made a positive value, if it's negative. But
the comparison "retval.tv_sec < 0" is always false, due to tv_sec is
unsigned according gnc-date.h:
,
| * struct timespec64 is just like the unix 'struct timespec' except
| * that we use a 64-bit
| * unsigned int to store the seconds. This should adequately cover
| …
| typedef struct timespec64 Timespec;
`
So, somehere you assign an negative value to tv_sec of type (unsigned)
int. The timespec_abs() function interprets this (signed) negativ value
as (unsigned) positiv value—you know, (unsigned int)-1 == UINT_MAX. This
function, except of the call of timespec_normalize()—which also makes
mistakes—is a big noop.
Or look at fin.c:1212
,
| static double
| rnd (double x, unsigned places)
| {
| …
| if (places >= 0)
| {
| sprintf (buf, "%.*f", (int) places, x);
| …
| else
`
Isn't it stupid to check a non‐negativ value, if it is greater or equal
zero? This holds everytime.
This may not lead to an error and gcc removes such unreachable parts, but
somewhere might be an assignment of an negative value to this
variable/parameter, which than results in a really curious call of
sprintf()—the case that should be prevented with the check.
Bye, Jörg.
--
Fuchs' Paradoxon (http://www.bruhaha.de/laws.html):
Wer eine allgemeine Frage beliebigen Themas nach de.alt.arnooo postet und
eine ernsthafte Antwort erwartet, ist dort eigentlich ziemlich ontopic.
pgppq7k7gRRtm.pgp
Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
Jörg Sommer wrote: > Neil Williams schrieb am Sat 12. Aug, 11:49 (+0100): >> GnuCash will >> automatically detect libgoffice-1-dev and libgsf-1-dev installations and >> use the associated libraries instead of building the code in >> lib/goffice* and lib/libgsf*. > > Is this valid for libqof-dev, true? I've installed it, but it configure > says: "configure: External QOF Disabled. Using Internal QOF Code." No. That is an old message, I guess it should read: "configure: External QOF is incompatible with internal fork. Ignoring." GnuCash no longer keeps up to date with libqof1 and instead gnc upstream maintain a separate fork of the code (libgncqof) that has been modified to be incompatible with libqof1 without causing a conflict when the two are installed together. At some point, upstream will cease checking for external QOF. > I've build GC 2.0.1 (note: GC can easily be confused with gcc, use 'gnc' to abbreviate gnucash) > Are these gnc* files external files? I found them in src/. No, but your build messages are non-standard. Why have you got so many flags set? CFLAGS ... : -O2 -Wall -Wformat=2 -Wunused -Wundef -Wextra -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 You should have: CFLAGS ... : -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 You've got -Wall twice, you've got -Wundef -Wextra, -Wunused twice. I see now you mentioned originally: > compiling gnucash with -Wall and -Wextra brings some warnings like this: So, here's a new start for this bug: 1. -Wall is already set, don't set it again. 2. -Wextra is *not supported* by gnucash and errors are to be expected. Don't use it. > Because the build log is really big (3.7MB) I put it at > http://www.minet.uni-jena.de/~joergs/gc.build.log Compare with the Debian build log for powerpc: http://buildd.debian.org/fetch.php?&pkg=gnucash&ver=2.0.1-1&arch=powerpc&stamp=1155098349&file=log&as=raw I'd recommend using the default gnc build environment - especially the compiler flags - and talking to gnucash-devel if you have a particular need for extra compiler options. You only have a problem because of extra compiler flags that are *not supported* upstream. Please explain, in detail, why you must have these compiler flags and I will forward this bug upstream to see what response it gets. Without such reasoning, I'm going to have to close this bug as "wontfix". -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Bug#360780: build: powerpc problem with sign of char
Hello Neil, Neil Williams schrieb am Sat 12. Aug, 11:49 (+0100): > Hi Jorg: > > Note: If the errors you report are in files prefixed with go- or in the > lib/goffice* or lib/libgsf* directories, these are *not* gnucash errors, > they are upstream GOffice issues. As such, you could rebuild with the > goffice development libraries installed and use the upstream code (which > is more recent than the code included in gnucash). GnuCash will > automatically detect libgoffice-1-dev and libgsf-1-dev installations and > use the associated libraries instead of building the code in > lib/goffice* and lib/libgsf*. Is this valid for libqof-dev, true? I've installed it, but it configure says: "configure: External QOF Disabled. Using Internal QOF Code." I've build GC 2.0.1 and I get still warnings about comparison between signed and unsigned values: gnctreemodelsort.c:1213: warning: comparison between signed and unsigned gnctreemodelsort.c:1672: warning: comparison between signed and unsigned gnctreemodelsort.c:1718: warning: comparison between signed and unsigned gnctreemodelsort.c:1764: warning: comparison between signed and unsigned gnctreemodelsort.c:1913: warning: comparison between signed and unsigned gnctreemodelsort.c:1927: warning: comparison between signed and unsigned gnc-date-delta.c:381: warning: comparison of unsigned expression >= 0 is always true gnc-date-delta.c:415: warning: comparison of unsigned expression >= 0 is always true gnc-associate-account.c:216: warning: comparison of unsigned expression >= 0 is always true gnc-associate-account.c:256: warning: comparison of unsigned expression >= 0 is always true gnc-associate-account.c:289: warning: comparison of unsigned expression >= 0 is always true Are these gnc* files external files? I found them in src/. Because the build log is really big (3.7MB) I put it at http://www.minet.uni-jena.de/~joergs/gc.build.log Bye, Jörg. -- Macht besitzen und nicht ausüben ist wahre Größe. (Friedl Beutelrock) pgpMpymtkqYj5.pgp Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
Hello Neil, Neil Williams schrieb am Sat 12. Aug, 11:49 (+0100): > As such, you could rebuild with the goffice development libraries > installed and use the upstream code (which is more recent than the code > included in gnucash). GnuCash will automatically detect > libgoffice-1-dev and libgsf-1-dev installations and use the associated > libraries instead of building the code in lib/goffice* and lib/libgsf*. Really interesting. I will try it. Do you know why Thomas do not build with these libs? Are there any problems? Bye, Jörg. -- Die meisten Menschen wollen lieber durch Lob ruiniert als durch Kritik gerettet werden. pgpm4grDNiJG4.pgp Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
Hi Jorg: Note: If the errors you report are in files prefixed with go- or in the lib/goffice* or lib/libgsf* directories, these are *not* gnucash errors, they are upstream GOffice issues. As such, you could rebuild with the goffice development libraries installed and use the upstream code (which is more recent than the code included in gnucash). GnuCash will automatically detect libgoffice-1-dev and libgsf-1-dev installations and use the associated libraries instead of building the code in lib/goffice* and lib/libgsf*. Other instances of this issue *have* been addressed upstream and if you still find issues during the build of the latest 2.0.1 release, please could you report the names of all files below src/ which are affected. Thanks. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Bug#360780: build: powerpc problem with sign of char
Jörg Sommer <[EMAIL PROTECTED]> writes: > Are you interessted in a patch? Yep, always.
Bug#360780: build: powerpc problem with sign of char
Hello Thomas, Thomas Bushnell BSG schrieb am Tue 04. Apr, 13:11 (-0700): > Jörg Sommer <[EMAIL PROTECTED]> writes: > > > Package: gnucash > > Version: 1.9.3-1hbci1 > > Severity: normal > > What's that version? It's 1.9.3-1 rebuild with HBCI support. > > compiling gnucash with -Wall and -Wextra brings some warnings like this: > > > > go-gradient.c:67: warning: comparison of unsigned expression < 0 is always > > false > > These might be bugs, but they also might not be. You have to look at > each case to know. Are you interessted in a patch? Bye, Jörg. -- $ cat /dev/random #!/usr/bin/perl -WT print "hello world\n"; pgpEHMZqLiHMm.pgp Description: PGP signature
Bug#360780: build: powerpc problem with sign of char
severity 360780 wishlist thanks Jörg Sommer <[EMAIL PROTECTED]> writes: > Package: gnucash > Version: 1.9.3-1hbci1 > Severity: normal What's that version? > compiling gnucash with -Wall and -Wextra brings some warnings like this: > > go-gradient.c:67: warning: comparison of unsigned expression < 0 is always > false These might be bugs, but they also might not be. You have to look at each case to know.
Bug#360780: build: powerpc problem with sign of char
Package: gnucash Version: 1.9.3-1hbci1 Severity: normal Hi, compiling gnucash with -Wall and -Wextra brings some warnings like this: go-gradient.c:67: warning: comparison of unsigned expression < 0 is always false They might come from the fact that a char is by default unsigned on PowerPC. This means if you write char i; if (i < 0) the comparison is _alway_ false. You must explicitly state that you want a "signed char". Often a negative value is used as an error code. This might prevent error detection and lead to strange crashes. I can send you the output produced while building, if you are interested. Bye, Jörg. -- System Information: Debian Release: unstable/experimental APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15.4 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages gnucash depends on: ii gnucash-common 1.9.3-1hbci1A personal finance tracking progra ii guile-1.6-libs 1.6.7-2 Main Guile libraries ii guile-1.6-slib 1.6.7-2 Guile SLIB support ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libatk1.0-0 1.10.3-1The ATK accessibility toolkit ii libaudiofile00.2.6-6 Open-source version of SGI's audio ii libavahi-client3 0.6.9-2 Avahi client library ii libavahi-common3 0.6.9-2 Avahi common library ii libavahi-compat-howl00.6.9-5 Avahi Howl compatibility library ii libavahi-glib1 0.6.9-5 Avahi glib integration library ii libbonobo2-0 2.14.0-1Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-1The Bonobo UI library ii libbz2-1.0 1.0.3-2 high-quality block-sorting file co ii libc62.3.6-3 GNU C Library: Shared libraries an ii libcairo21.0.2-3 The Cairo 2D vector graphics libra ii libdate-manip-perl 5.44-2 a perl library for manipulating da ii libdbus-1-2 0.61-4 simple interprocess messaging syst ii libesd0 0.2.36-3Enlightened Sound Daemon - Shared ii libffi4 4.1.0-1 Foreign Function Interface library ii libfinance-quote-perl1.11-0.1Perl module for retrieving stock q ii libfontconfig1 2.3.2-2 generic font configuration library ii libfreetype6 2.1.10-1.1 FreeType 2 font engine, shared lib ii libgconf11 1.0.9-7.1 GNOME configuration database syste ii libgconf2-4 2.14.0-1GNOME configuration database syste ii libgcrypt11 1.2.2-1 LGPL Crypto library - runtime libr ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.10.1-2The GLib library of C routines ii libgnome-keyring00.4.9-1 GNOME keyring services library ii libgnome2-0 2.14.0-2The GNOME 2 library - runtime file ii libgnomecanvas2-02.14.0-1A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-3The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-2GNOME 2.2 print architecture User ii libgnomeui-0 2.14.0-1The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.0-1GNOME virtual file-system (runtime ii libgnutls11 1.0.16-14 GNU TLS library - runtime library ii libgpg-error01.2-1 library for common error values an ii libgsf-1-114 1.14.0-1Structured File Library - runtime ii libgsf-gnome-1-114 1.14.0-1Structured File Library - runtime ii libgtk2.0-0 2.8.16-1The GTK+ graphical user interface ii libgtkhtml3.8-15 3.8.1-1.1 HTML rendering/editing library - r ii libguile-ltdl-1 1.6.7-2 Guile's patched version of libtool ii libgwrap-runtime01.9.6-3 scripting interface generator for ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libjpeg626b-12 The Independent JPEG Group's JPEG ii libltdl3 1.5.22-2A system independent dlopen wrappe ii libofx2c2a 1:0.8.0-10+b1 library to support Open Financial ii liborbit21:2.14.0-1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-01.12.0-2Layout and rendering of internatio ii libpng12-0 1.2.8rel-5 PNG library - runtime ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm6 6.9.0.dfsg.1-4 X Window System Session Management ii libtasn1-2 0.2.17-1Manage ASN.1 structures (runtime)
