| 1 |
On Mon, 16 Aug 2010 21:08:52 +0800, Galaxy <galaxy001@×××××.com> wrote: |
| 2 |
> I am doing on two servers with |
| 3 |
> "2.6.9-55.0.2.ELsmp,/lib64/tls/libc-2.3.4.so" and |
| 4 |
> "2.6.18-164.6.1.el5,/lib64/libc-2.5.so" that mount a same NFS disk. |
| 5 |
> (In fact, they are 2 clusters with different linux on them and the |
| 6 |
> administrators are not going to make those nodes same.) |
| 7 |
> |
| 8 |
> When I first encounter some errors that googled towarding to glibc, I |
| 9 |
> found glibc is not in the portage gentoo-prefix, |
| 10 |
|
| 11 |
Correct, Gentoo Prefix relies on the host's libc. |
| 12 |
|
| 13 |
> so I thought it might be better to build the prefix under my own |
| 14 |
> machine, which runs Gentoo. |
| 15 |
> After I done this on my machine and rsync back to the same path on |
| 16 |
> the server, I found everything linking on glibc cannot work since the |
| 17 |
> libc there is too old. |
| 18 |
|
| 19 |
You have to build the packages on the host that has the older glibc. |
| 20 |
|
| 21 |
> So, How can I make a prefix that works on both these 2 servers? |
| 22 |
> I think what I need is to make a glibc-2.11 with kernel 2.6.9-55, the |
| 23 |
> lower one. |
| 24 |
> |
| 25 |
> Any note on prefix the glibc? Such as, what glibc depands on. |
| 26 |
> |
| 27 |
> And In fact I am not so sure which linux distributions are on those |
| 28 |
> server, I just find there are 'rpm' but no 'apt-get' and no 'deb' . |
| 29 |
> From other informations, it should be some CentOS. But I am not sure. |
| 30 |
|
| 31 |
There should be an /etc/*release* file that contains such info. |
| 32 |
|
| 33 |
-Jeremy |
Archives