| 1 |
Mike, |
| 2 |
|
| 3 |
sorry for my unclear email. |
| 4 |
|
| 5 |
Of course I am looking for the tools which are created for this explicit |
| 6 |
purpose and I like to use them. |
| 7 |
|
| 8 |
I had the suspicion that cross-fix-root and lafilefixer are such tools, |
| 9 |
but I only know their help text and their source code. I would like to |
| 10 |
know more about them, before I call them logged in as root. I don't want |
| 11 |
to corrupt my system by calling it at the wrong time, with the wrong |
| 12 |
command arguments or with the wrong environment variables. |
| 13 |
|
| 14 |
1. Are there any docs or discussions on the web which further describe |
| 15 |
their purpose and their usage? |
| 16 |
|
| 17 |
2. How should I have used these tools in order to prevent the problems with |
| 18 |
$ROOT/usr/lib/libgmp.la and |
| 19 |
$ROOT/usr/lib/libcrack.so |
| 20 |
which I have described in my previous email? |
| 21 |
|
| 22 |
3. Which tools should be called when? |
| 23 |
After each emerge? |
| 24 |
Are these tools already called by emerge or other system tools? |
| 25 |
|
| 26 |
4. When I cross compile the root file system in |
| 27 |
/usr/armv4tl-softfloat-linux-gnueabi, |
| 28 |
libdir needs to be |
| 29 |
libdir='/usr/armv4tl-softfloat-linux-gnueabi/usr/lib'. |
| 30 |
|
| 31 |
When the target system (ARM) mounts this root fs through NFS, then |
| 32 |
libdir needs to be again libdir='/usr/lib'. |
| 33 |
|
| 34 |
May I call cross-fix-root or lafilefixer on the target or host system |
| 35 |
again, in order to change the paths forth and back? |
| 36 |
|
| 37 |
Best regards |
| 38 |
|
| 39 |
Jan |
Archives