Same program as you posted earlier?
Yes. it's the same.

Can you confirm the issue with this procedure? Also make sure that your
rebuild and re-installed the Xenomai user space part cleanly ("make
clean; make install").

I installed cleanly Xenomai.

I compiled too with :
arm-linux-gcc `.../xeno-config --posix-cflags --posix-ldflags` -o
essai_mutex_rt essai_mutex.c

Here is the objdump after :

#> objdump -R essai_mutex_rt

essai_mutex_rt:     format de fichier elf32-little

DYNAMIC RELOCATION RECORDS
OFFSET   TYPE              VALUE
00011234 UNKNOWN           stderr
000111c0 UNKNOWN           __wrap_pthread_mutex_unlock
000111c4 UNKNOWN           printf
000111c8 UNKNOWN           sigemptyset
000111cc UNKNOWN           strerror
000111d0 UNKNOWN           pthread_attr_init
000111d4 UNKNOWN           pthread_exit
000111d8 UNKNOWN           puts
000111dc UNKNOWN           sleep
000111e0 UNKNOWN           sigaddset
000111e4 UNKNOWN           abort
000111e8 UNKNOWN           __wrap_pthread_setschedparam
000111ec UNKNOWN           __wrap_pthread_mutex_lock
000111f0 UNKNOWN           fprintf
000111f4 UNKNOWN           pthread_attr_setinheritsched
000111f8 UNKNOWN           signal
000111fc UNKNOWN           pthread_attr_setstacksize
00011200 UNKNOWN           pthread_sigmask
00011204 UNKNOWN           __wrap_pthread_mutex_init
00011208 UNKNOWN           __wrap_pthread_create
0001120c UNKNOWN           pthread_self
00011210 UNKNOWN           pthread_attr_setschedpolicy
00011214 UNKNOWN           __uClibc_start_main
00011218 UNKNOWN           pthread_attr_setschedparam
0001121c UNKNOWN           pthread_attr_setdetachstate
00011220 UNKNOWN           pthread_join
00011224 UNKNOWN           __wrap_pthread_mutex_destroy

I have the same problem when I want to launch it on my board.
On 5/31/07, Wolfgang Grandegger <[EMAIL PROTECTED]> wrote:

Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
>> Jan Kiszka wrote:
>>> Perrine Martignoni wrote:
>>>>> Perrine, did you happen to configure Xenomai with "configure
--host=arm
>>>>> ..."? If yes (see config.log), please use "--host=arm-linux". This
>>>>> solved all issues for me.
>>>>>
>>>>> Awaiting your feedback!
>>>> I configure Xenomai with --host=arm.
>>>> I tried to configure like this but it doesn't work :
>>>>
>>>> ./configure --build=arm-linux --host=arm-linux CC=arm-linux-gcc
>>>                       ^^^^^^^^^
>>> I guess you are not compiling Xenomai _on_ an ARM box, are you? :)
>>> Try --build=i686-linux here.
>> Or just omit it. Also CC=, CXX=, LD= ist not necessary. For PowerPC
with
>> the ELDK, I just use
>>
>>   ./configure --host=ppc-linux
>>
>> to configure Xenomai.
>
> Can we define a common ground for this in README.INSTALL, for all archs?
> The simpler, the better.

The above works for the ELDK, because the tools ppc-linux-xxx are
available in the binary path (via PATH), but this might not be true for
other tool-chains. And this method also does not work with RTnet, IIRC.
So far, I didn't realize any difference between the configuration
methods ...

> I was heavily misled by the PPC section, because I do not cross-compile
> everyday, thus had to look up the procedure again and managed to pick
> the bad example...

... but there might be some quirk with ARM and uClibc tool chains of the
ELDK.

Wolfgang.


_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to