This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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? Thanks in advance! -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |