On Sun, 30 Jun 2002 02:11:55 +0200 Henning Meier-Geinitz <henn...@meier-geinitz.de> wrote:
> Try something like > export LD_LIBRARY_PATH=/usr/local/lib > > (Untested). It worked! Now I can scan correctly using xsane if before I give that cmd, thank you!!! :-) But, if you don't mind, I have some more questions because I think we are just dodging the problem, while I'd like to solve it (also to share the solution with the other guys of alt.os.linux.mandrake). Question 1: where does the export cmd you gave me write the path for 1.0.8 libraries? I'd like to modify some config file so that I don't need everytime to give this cmd before launching xsane. Question 2: backends 1.0.8 compiled and installed by me is virtually stuck in /usr/local as I don't see anywhere its uninstall script! Where do I find it? I didnt find it Question 3: Now I have a weird sane file composition: libraries 1.0.5 and both 1.0.5 + 1.0.8 backends. With your trick I make xsane call 1.0.8 libs in /usr/local/lib instead of 1.0.5 of /usr/lib. What if someday I want to completely remove 1.0.5 and start from scratch installing 1.0.8? Just do it, you might say, but it's not so easy as installing the 1.0.8 rpms requests 1.0.5 files anyway! It's crazy! I have ALL the 1.0.8 sane rpms I need, but I'm unable to start a 'clean' install of this latest release. Maybe there is on order to install these rpms? Like first libsane, then libsane-devel, then the backends and so on. Generally speaking, do you suggest working on tarballs rather than rpms? In my newbie experience I found that rpms often are confusing ... In any case thanks again for your help and your patience! ;) Ciao! ============================ Turn on, tune in, drop out [Timothy Leary] Journeyman of 666, Inc. Sorso su Ranocchia Triple, mod. Y2K
