On 2011-07-28 18:56, Jan Kiszka wrote:
> On 2011-07-27 20:49, Gilles Chanteperdrix wrote:
>> On 07/22/2011 05:04 PM, Jan Kiszka wrote:
>>> Hi Gilles,
>>>
>>> pulling assert_context.c into the common libxenomai created a problem
>>> around picking the right __wrap_clock_gettime. As libpthread_rt dep
On 2011-07-28 18:56, Jan Kiszka wrote:
> On 2011-07-27 20:49, Gilles Chanteperdrix wrote:
>> On 07/22/2011 05:04 PM, Jan Kiszka wrote:
>>> Hi Gilles,
>>>
>>> pulling assert_context.c into the common libxenomai created a problem
>>> around picking the right __wrap_clock_gettime. As libpthread_rt dep
On 2011-07-27 20:49, Gilles Chanteperdrix wrote:
> On 07/22/2011 05:04 PM, Jan Kiszka wrote:
>> Hi Gilles,
>>
>> pulling assert_context.c into the common libxenomai created a problem
>> around picking the right __wrap_clock_gettime. As libpthread_rt depends
>> on libxenomai, the latter is loaded fi
On 07/22/2011 05:04 PM, Jan Kiszka wrote:
> Hi Gilles,
>
> pulling assert_context.c into the common libxenomai created a problem
> around picking the right __wrap_clock_gettime. As libpthread_rt depends
> on libxenomai, the latter is loaded first and defines the debug version
> of __wrap_clock_get
Hi Gilles,
pulling assert_context.c into the common libxenomai created a problem
around picking the right __wrap_clock_gettime. As libpthread_rt depends
on libxenomai, the latter is loaded first and defines the debug version
of __wrap_clock_gettime as the default. There is no chance to pull the
po