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