[lttng-dev] urcu AC_FUNC_MALLOC fails for cross-compile
Mathieu Desnoyers
mathieu.desnoyers at efficios.com
Tue Jun 14 16:33:19 UTC 2016
----- On Jun 14, 2016, at 12:26 PM, Luke K D'Alessandro ldalessa at indiana.edu wrote:
>> On Jun 14, 2016, at 12:21 PM, Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>> wrote:
>>
>> ----- On Jun 14, 2016, at 12:12 PM, Luke K D'Alessandro ldalessa at indiana.edu
>> wrote:
>>
>>> The AC_FUNC_MALLOC depends on some runtime results which doesn't work when cross
>>> compiling. Google has a bit to say about this and basically the fix is to stop
>>> using the macro. Is there a specific purpose for this check, or could it just
>>> be eliminated from configure.ac?
>>
>> If we remove this check, we need to ensure that URCU does not depend
>> on malloc(0) returning non-NULL anywhere.
>
> Okay, I’m not sure what the implications are this for you. We have a test
> infrastructure that tries to download, build, and link liburcu using a cross
> compiler for 32-bit arm platforms, but it fails because of this check. I will
> try and figure out how to get a binary version of liburcu installed permanently
> somewhere that the cross compiler toolchain can find.
Can you give us some details on how it fails ?
configure output and config.log
Thanks,
Mathieu
>
> Thanks,
> Luke
>
>>
>> Thanks,
>>
>> Mathieu
>>
>>>
>>> Thanks,
>>> Luke
>>>
>>> _______________________________________________
>>> lttng-dev mailing list
>>> lttng-dev at lists.lttng.org
>>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>> --
>> Mathieu Desnoyers
>> EfficiOS Inc.
> > http://www.efficios.com
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
More information about the lttng-dev
mailing list