On 28 Apr, Dmitry Yaitskov shouted:
-> On Tuesday, Apr 28, [EMAIL PROTECTED] ([EMAIL PROTECTED]) spake thusly:
-> > On 27 Apr, Dmitry Yaitskov shouted:
-> > -> Hi guys,
-> > ->
-> > -> I dunno about rpms, but those who compile their own probably know that
-> > -> there are some problems when linking with imlib, at least with 1.3 (I
-> > -> don't remember about older versions)... the problem being that if you
-> > -> link with imlib, you have to 'manually' add -ltiff -lgif etc. to the
-> > -> command that links the final executable... because the shared imlib
-> > -> library itself is linked *without* those other libraries that it
-> > -> actually needs. That is, the command that creates the imlib so file
-> > -> looks like this:
-> >
-> > of course it doesn't.. because only linux supports libs linked to other
-> > libs.. you have to link the APP (program) using imlib to libtiff,
-> > libgif etc.
->
-> I see... (I didn't know that because Linux is the only unix that I've
-> ever seen.)
ahh - that's something I try and remain aware of and not make a "Linux
only" program - if I did that I'd be making full use of everything in
/proc to work out system stats (ie mem usage etc.) and have E
dynamically adjust to it where possible, as well as system load etc.
I may develop on linux, but I like to make sure my stuf works for other
main unicies.
-> <snip>
-> > thew inter-lib dependanicies was disabled in libtool due to bugs in
-> > libtool. This is old-hat :)
->
-> Yes, that's what its (libtool's) page says... which brings me back to
-> my question - if it *is* broken, why use it?... but according to what
-> you say (that shared libs should not be linked to other libs) it is
-> not broken? or is it?
It has some problems where on some systems that don't support linke
libs it tries linking or somehting like that.. so to make sure it
doesn't barf it won't link libs to eachother at all until it's fixed. :)
-> >
-> > -> 'Many people have been sending bug reports to me because libtool
-> > -> doesn't do inter-library dependencies'
-> > ->
-> > -> Oops... so what I'm trying to say... it is all well and nice to
-> > -> acknowledge the fact (that it is broken), but it still *is* broken. I
-> > -> mean, the net result is that imlib is linked wrongly, and other things
-> >
-> > no - imlib need not be linked at all.. the thing to do is make sure the
-> > apps using imlib are linked correctly :)
->
-> You may be right, but if so at least two other apps have broken
-> installs - e (which does not link explicitly to all those other
E requires you to edit tihe Imake stuff to tel it what libs to use.
-> graphical libs), and eplus (its config script tries to check for
-> imlib, and fails if imlib is not linked with the libs it
-> needs)... As I said, I have no experience with libtool nor with any
-> unix except linux, so what I'm writing is not a flame, but rather an
-> attempt to understand *what* is broken (and needs fixing). Because
-> something definitely is (and does).
Yup. I know.. don't worry :) In future it will be simple E will REQUIRE
libpng, libtiff, libgif and libjpeg - without them E will refuse to
compile.
--
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
[EMAIL PROTECTED] /\___ /\ ___/||\___ ____/|/\___ [EMAIL PROTECTED]
Carsten Haitzler | _ //__\\ __||_ __\\ ___|| _ / Red Hat Advanced
218/21 Conner Drive || // __ \\_ \ | | \ _/_|| / Development Labs
Chapel Hill NC 27514 USA ||\\\/ \//__/ |_| /___/||\\ 919 547 0012 ext 282
+1 (919) 929 9443, 801 4392 For pure Enlightenmenthttp://www.rasterman.com/
-
To unsubscribe from this list send mail to: [EMAIL PROTECTED]
with the message contents: unsubscribe e-develop
