On Friday, September 8, 2017 at 3:16:12 AM UTC+2, Fetchinson . wrote:
> On 9/7/17, Thomas Jollans wrote:
> > On 2017-09-06 16:14, Fetchinson . via Python-list wrote:
> >> Hi folks,
> >>
> >> I'm trying to install a binary package (tensorflow) which contains
> >> some binary C extensions. Now
On 9/7/17, Thomas Jollans wrote:
> On 2017-09-06 16:14, Fetchinson . via Python-list wrote:
>> Hi folks,
>>
>> I'm trying to install a binary package (tensorflow) which contains
>> some binary C extensions. Now my system glibc is 2.15 but the binaries
>> in the C extensions were created (apparentl
On 2017-09-06 16:14, Fetchinson . via Python-list wrote:
> Hi folks,
>
> I'm trying to install a binary package (tensorflow) which contains
> some binary C extensions. Now my system glibc is 2.15 but the binaries
> in the C extensions were created (apparently) with glibc 2.17. So I
> thought no pr
"Fetchinson . via Python-list" writes:
> I'm trying to install a binary package (tensorflow) which contains
> some binary C extensions. Now my system glibc is 2.15 but the binaries
> in the C extensions were created (apparently) with glibc 2.17. So I
> thought no problemo I installed glibc 2.17 t
Hi folks,
I'm trying to install a binary package (tensorflow) which contains
some binary C extensions. Now my system glibc is 2.15 but the binaries
in the C extensions were created (apparently) with glibc 2.17. So I
thought no problemo I installed glibc 2.17 to a custom location, built
python2.7 f
