>From my understanding, ldconfig is supposed to be taking care of the symlinks for the libxxxx.so files. My thoughts on this are that when the install of the libraries in question happen, it doesn't run an ldconfig to update the links. There could be a number of reasons for this, so I'm not pointing the finger at the Makefile.
One thing to try is, if you notice the links are missing, try running an ldconfig. I'd do it but the builds I've tried from CVS don't build their RPMS right yet. Some stuff hasn't been properly converted to the new "auto-f'ck" setup. I'll probably be investigating this more this weekend though, even if for my own edumacation. > Sorry to bug again. I got this compilation error when compiling > evas: > [SNIP] > > well it seems that it's looking for libeet.so and libedb.so, while > the packages eet and edb install libeet.so.0.9.9 and libedb.so.1.0.5. > > Now from previous experience, I know if I symlink (ln -s blah blah) > everything would be ok since we're probably talking about the same > files. > > But should I do that each time? Is it possible to make the subsequent > packages search for the exact name of the libraries or if you have > other ways of handling this, it would be most welcome? ;-) Thanks. > -- Jason Williams Lead Developer Gaim Assistant <[EMAIL PROTECTED]> ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
