On Monday, June 18, 2012, Måns Rullgård <m...@mansr.com> wrote:
> Martin Storsjö <mar...@martin.st> writes:
>
>> On Mon, 18 Jun 2012, Mans Rullgard wrote:
>>
>>> From: "Ronald S. Bultje" <rsbul...@gmail.com>
>>>
>>> ---
>>> configure | 4 +++-
>>> libavutil/mem.c | 6 ++++++
>>> 2 files changed, 9 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index a5d2787..f1f58a7 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -1049,6 +1049,7 @@ HAVE_LIST="
>>> $ARCH_EXT_LIST
>>> $HAVE_LIST_PUB
>>> $THREADS_LIST
>>> + aligned_malloc
>>> aligned_stack
>>> alsa_asoundlib_h
>>> altivec_h
>>> @@ -2834,6 +2835,7 @@ check_func ${malloc_prefix}memalign
&& enable memalign
>>> check_func mkstemp
>>> check_func mmap
>>> check_func ${malloc_prefix}posix_memalign && enable posix_memalign
>>> +check_func ${malloc_prefix}_aligned_malloc && enable
aligned_malloc
>>
>> On mingw, this function is only available if such a version of the
>> MSVCRT is targeted that contain it, controlled via the
>> headers. Currently, since this doesn't test the headers but only tests
>> linking, it will succeed regardless. A check which tries to include it
>> from the header (malloc.h) would be better in this case, I think.
>
> Do you have such a system? Could you help testing it?
Mike Kostylev controls the mingw FATE runs. Maybe ping him?
-- Sean McG
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
