Re: [Xenomai] Xenomai 3 - no skin detected in program

[Philippe Gerum <rpm@xenomai.org>]

On 02/04/2015 12:40 PM, Huy Cong Vu wrote:
> 
> 
> ----- Mail original -----
>> De: "Huy Cong Vu" <huy-cong.vu@wandercraft.eu>
>> À: "Philippe Gerum" <rpm@xenomai.org>
>> Cc: xenomai@xenomai.org
>> Envoyé: Mercredi 4 Février 2015 12:07:54
>> Objet: Re: [Xenomai] Xenomai 3 - no skin detected in program
> 
>> ----- Mail original -----
>>> De: "Philippe Gerum" <rpm@xenomai.org>
>>> À: "Huy Cong Vu" <huy-cong.vu@wandercraft.eu>, xenomai@xenomai.org
>>> Envoyé: Mercredi 4 Février 2015 10:13:14
>>> Objet: Re: [Xenomai] Xenomai 3 - no skin detected in program
>>
>>> On 02/04/2015 09:55 AM, Huy Cong Vu wrote:
>>>> Hello everyone,
>>>> I recently try to run an application compiled in native skin of Xenomai 3. When
>>>> trying to run the binary, these line appeared:
>>>> WARNING: [main] no skin detected in program
>>>> BUG: [main] initialization failed, EINVAL
>>>> I know that this is a cooperplate_init() warning when trying to initialize
>>>> native skin, but I don't understand the reason why:
>>>> if (pvlist_empty(&skins)){
>>>> warning("no skin detected in program");
>>>> ret = -EINVAL;
>>>> goto fail;
>>>> }
>>>
>>> It seems that your application was not linked against libalchemy.so.
>>> When API libraries are properly linked in, internal constructor routines
>>> populate this list. POSIX support is built-in within the Cobalt
>>> interface, so it won't appear here though.
>>>
> I change the order of the linker flags, now my app is linked against libalchemy.so, but this message shown up:
> symbol lookup error: /usr/xenomai/lib/libcopperplate.so.0: undefined symbol: main
> 
> I guess that it stills a problem due to the linker flag, am I right? 
> 

Yes. You seem to be using a set of flags with fine-grained tuning, some
of which might have an adverse effect on your linking stage. You should
start with the set output by xeno-config --ldflags --alchemy which are
known to work, then tune gradually as appropriate.

-- 
Philippe.