Re: [Xenomai-help] Xenomai with µClibc

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 2361 bytes --]

Wolfgang Grandegger wrote:
> Jan Kiszka wrote:
>> Wolfgang Grandegger 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.
>>>>
>>>> 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...
>>> I had a closer look and realized, that passing just CC, CXX and LD to
>>> the configure script is not enough. There should at least also AR and
>>> RANLIB, otherwise the corresponding host tools are used. Then I think,
>>> it should be equivalent to automatic tool assignment via --host.
>>>
>>> Also note, that "--host=arm" will also work with the ELDK, because there
>>> are links arm-* to the tools arm-linux-*. I Perrine's configure examples
>>> above, arm-ar and arm-ranlib will then be used.
>>
>> But the issue is that in this case configure is unable to find the
>> target OS and fails to detect that shared libs are supported for the
>> target. Non-shared build fails with ELDK for unknown reasons.
> 
> Why it is unable to find the target OS. Can you provide an example? And

Look at the configure script. :o) [This is how I found the reason for
the non-shared build.]

> non-shared builds only fail with the ARM uClibc toolchain from the ELDK.
> It builds fine with the normal ARM tool-chain.

OK, good to know that the issue is confined.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]