This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: wierd problem with eabi compiler and kernel 2.6.18
- From: Nicolas Pitre <nico at cam dot org>
- To: Jevgeni Zolotarjov <zhenja at zlo dot ee>
- Cc: linux-arm-kernel at lists dot arm dot linux dot org dot uk, crossgcc at sources dot redhat dot com, libc-alpha at sources dot redhat dot com
- Date: Mon, 16 Oct 2006 16:03:54 -0400 (EDT)
- Subject: Re: wierd problem with eabi compiler and kernel 2.6.18
- References: <eh0nf2$kn6$1@sea.gmane.org>
On Mon, 16 Oct 2006, Jevgeni Zolotarjov wrote:
> Hi All,
>
> We are happy users of Dan's crosstool-0.42. We have built with it following
> toolchain:
> gcc-4.0.2
> glibc-2.3.6
> binutils-2.16.1
>
> We are using it for more than a year on ARM920T processor (AT91RM9200) with
> kernel 2.6.15.4. Results are excellent and system is very stable.
>
> Now we want to migrate to new version of everything.
> First, we took toolchain from Martin Guy with arm eabi support. We have
> successfully compiled with it kernel 2.6.18 with arm eabi support. It looked
> nice from the first view. We have ported our periphery drivers for USB, IO
> and ALSA devices. Excellent! All works. But we have found one wierd problem:
> IPC shared memory does not work in a desired way. All our applications and
> some ALSA plugins, which rely on IPC, crash or give unpredicted results. We
> can write and read from shared memory and results are correct, but returned
> size of shared memory is every time different.
Did you recompile your user apps with EABI as well?
> We have traced the problem further. It turned out, that kernel returns
> correct size number. But glibc returns with every function call
> different number.
Do you have an EABI enabled glibc?
Nicolas