1 |
One option is to copy the glibc version you want to some other directory |
2 |
and set LD_LIBRARY_PATH before starting the executable. Running "ldd" on |
3 |
all the executables/shared libraries in question should give you a list of |
4 |
all the shared libraries you might need to copy to a safe place. |
5 |
|
6 |
|
7 |
On Mon, Aug 18, 2014 at 11:06 AM, Timur Aydin <ta@××××××.org> wrote: |
8 |
|
9 |
> Hi, |
10 |
> |
11 |
> I am using a closed source software package on my 64 bit gentoo linux |
12 |
> system. The software package is "beyond compare" by scooter soft. Because |
13 |
> of the way this package is built, it needs a specially patched version of |
14 |
> glibc. I have patched my existing glibc version (2.18) and have been |
15 |
> avoiding updating my glibc since. Now I am wondering whether the latest |
16 |
> update of bcompare will work with the latest glibc (2.19). |
17 |
> |
18 |
> So, if I upgrade to 2.19 and the package doesn't work, how can I go back |
19 |
> to the working, patched 2.18? I know that portage issues the most scary |
20 |
> warnings when you try to downgrade glibc. So what does the community |
21 |
> recommend? |
22 |
> |
23 |
> -- |
24 |
> Timur |
25 |
> |
26 |
> |
27 |
|
28 |
|
29 |
-- |
30 |
Manuel A. McLure WW1FA <manuel@××××××.org> <http://www.mclure.org> |
31 |
...for in Ulthar, according to an ancient and significant law, |
32 |
no man may kill a cat. -- H.P. Lovecraft |