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: Koen Kooi <koen at dominion dot kabel dot utwente dot nl>
- To: libc-alpha at sources dot redhat dot com
- Cc: crossgcc at sources dot redhat dot com,linux-arm-kernel at lists dot arm dot linux dot org dot uk
- Cc: crossgcc at sources dot redhat dot com,libc-alpha at sources dot redhat dot com
- Date: Mon, 16 Oct 2006 22:34:32 +0200
- Subject: Re: wierd problem with eabi compiler and kernel 2.6.18
- References: <eh0nf2$kn6$1@sea.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jevgeni Zolotarjov schreef:
> 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. We have traced the problem
> further. It turned out, that kernel returns correct size number. But glibc
> returns with every function call different number.
>
> We have also tried to build toolchain ourselves with following components:
> gcc-4.1.1
> glibc-2.4
> binutils-2.17
> The same results :(
>
> Does anybody uses IPC successfuly on ARM architecture? Which toolchain do
> you use? Can anybody help to solve the problem?
gcc 4.1.1 + patches in
http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/gcc/gcc-4.1.1
binutils 2.17
glibc 2.5 + patches mentioned in
http://www.openembedded.org/repo/org.openembedded.dev/packages/glibc/glibc_2.5.bb
Are working quite well. Glibc 2.4 is simply broken for arm and shm. You can build the
toolchain yourself with openembedded.
As a side note: Martin Guy is now using a toolchain built by OpenEmbedded to bootstrap the
debian/ARM EABI port, so it's under heavy testing :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFM+zYMkyGM64RGpERAo1CAJ9R6YZ6r+kvroeCceOfsrX3nL5hCwCgk0S5
amc9RuljHEUijPIn8N5gOpo=
=EGaN
-----END PGP SIGNATURE-----