On 19 August 2017 at 17:37, Lele Gaifax <l...@metapensiero.it> wrote:
> Nathaniel Smith <n...@pobox.com> writes:
> I'm still puzzled about *how* that can happen, given that I do not seem to
> have altered the source code in a way that would justify that, but even more,
> as you say, how can that glibc version be referenced, if it does not even
> exist in the context.
>
> I remain willing to try any suggestion,
While it won't answer the "how", it may be worth trying adding this to
see if you can keep it from happening:
#ifdef __GLIBC__
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
#endif
Beyond that, reading
https://github.com/joerick/cibuildwheel/blob/master/cibuildwheel/linux.py
means I share the confusion as to *how* you could be picking up a
newer glibc version (unless there's a bug in the manylinux1 docker
images themselves)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_______________________________________________
Wheel-builders mailing list
Wheel-builders@python.org
https://mail.python.org/mailman/listinfo/wheel-builders
