On Fri, Mar 26, 2010 at 2:58 AM, Jussi Hakala wrote:
> Aaron Brice wrote:
>>
>> I'm on a RHEL 5 host system, using scratchbox2 and the latest 4.4
>> CodeSourcery IA32 toolchain. It seems like it's linking against the
>> host system ancient glibc (libc-2.5.so) instead of the toolchain's
>> glibc (
Han Hartgers ha scritto:
> Dear Aaron,
>
> I am not really an expert on this but I think that the problem is not
> directly Scratchbox2; for some reason is the make process asking for the
> usages of the host C-compiler and in that case is always the host libc
> is used. (Even when it is too old.)
Aaron Brice wrote:
I'm on a RHEL 5 host system, using scratchbox2 and the latest 4.4
CodeSourcery IA32 toolchain. It seems like it's linking against the
host system ancient glibc (libc-2.5.so) instead of the toolchain's
glibc (libc-2.10.1.so):
You are building the kernel inside scratchbox? May
Dear Aaron,
I am not really an expert on this but I think that the problem is not
directly Scratchbox2; for some reason is the make process asking for the
usages of the host C-compiler and in that case is always the host libc is
used. (Even when it is too old.)
On Thu, Jan 21, 2010 at 2:44 AM, A
I'm on a RHEL 5 host system, using scratchbox2 and the latest 4.4
CodeSourcery IA32 toolchain. It seems like it's linking against the
host system ancient glibc (libc-2.5.so) instead of the toolchain's
glibc (libc-2.10.1.so):
make[1]: Entering directory `/scratch/kernel/linux-2.6'
...
CC in
