| 1 |
I was in a similar position some years ago - grab a copy of the needed |
| 2 |
libs from somewhere and use "ldpreload" to load them into memory before |
| 3 |
running the application. Google will help. |
| 4 |
|
| 5 |
In some cases, you can symlink the needed lib names to existing later |
| 6 |
libs and run ldconfig before trying to run the app. This does work |
| 7 |
sometimes, but success varies ... |
| 8 |
|
| 9 |
BillK |
| 10 |
|
| 11 |
|
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
On Fri, 2009-10-30 at 19:27 -0400, Albert Hopkins wrote: |
| 16 |
> On Fri, 2009-10-30 at 14:52 -0700, Kyle Bader wrote: |
| 17 |
> > I dunno how |
| 18 |
> > flexible the vendor is but its worth asking :) |
| 19 |
> |
| 20 |
> They only support RHEL4. RHEL4 was released nearly 5 years ago and uses |
| 21 |
> the 2.6.9 kernel. I think that shows how flexible they are. :) |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
-- |
| 26 |
William Kenworthy <billk@×××××××××.au> |
| 27 |
Home in Perth! |
Archives