1 |
On 04/06/10 01:25, Fabian Groffen wrote: |
2 |
> On 05-04-2010 23:18:35 -0500, Johan Hattne wrote: |
3 |
>> On 30 Mar 2010, at 03:13, Fabian Groffen wrote: |
4 |
>> |
5 |
>>> On 30-03-2010 07:19:02 +0200, Markus Duft wrote: |
6 |
>>>> just to chime in on the movability: i successfully moved whole prefix |
7 |
>>>> installations to other directories, and they worked fine (hint: i used |
8 |
>>>> chpathtool to adjust paths) the only limitation is, that the path has to |
9 |
>>>> be the exact same length (or less long, but that one didn't work for me |
10 |
>>>> yet, but that could be fixable). of course this is not really |
11 |
>>>> convenient, but it should be possibly for you to create |
12 |
>>>> |
13 |
>>>> "/home/user/prefix-with-long-path1" |
14 |
>>>> and |
15 |
>>>> "/cluster/disk25/user/prefix-short" |
16 |
>>>> |
17 |
>>>> those would be exchangeable. Of course chpathtool is possibly still not |
18 |
>>>> perfect, and i observed the one or the other segfault with certain files |
19 |
>>>> (none of those lately though). However you're free to fix it ;) |
20 |
>>> |
21 |
>>> That could match chpathtool's changes that it got recently. Instead of |
22 |
>>> trying to shorten paths, it now pads them with leading slashes, e.g.: |
23 |
>>> |
24 |
>>> original prefix: /path/to/my/long/prefix |
25 |
>>> target prefix: ////////my/short/prefix |
26 |
>>> |
27 |
>>> As a result, the target prefix is always as long as the original prefix, |
28 |
>>> be it somewhat ugly. We found that this solves misc issues that you get |
29 |
>>> when you suddenly make a string smaller ;) |
30 |
>> |
31 |
>> Apologies for resurrecting this topic, and I just realised I've |
32 |
>> probably been confusing chpathtool with chrpath during all previous |
33 |
>> discussions, but I haven't seen any mention of patchelf. I got the |
34 |
>> Intel compiler running in a Linux-prefixed-portage last week. |
35 |
> |
36 |
> What can patchelf do that you needed to get it going? |
37 |
|
38 |
It can set (grow or shrink) the rpath. It can also set the run-time |
39 |
linker, but I didn't seem to need that for this exercise. ebuild attached. |
40 |
|
41 |
// Cheers; Johan |