[gccsdk] New SharedLibs incompatibility

David Pitt pittdj at pittdj.co.uk
Thu Jul 23 12:19:13 PDT 2020


In message <cad908a1-72cd-ba2a-348d-60dd77fe365c at sky.com>
  Lee Noar <lee.noar at sky.com> wrote:

> On 23/07/2020 16:05, Chris Johns wrote:
>> I'd better get compiling.
>> 
>> However, if I build it again the new libs I assume it won't work with
>> the older ones?

[snip]

> In hind sight, I should have placed "clock_id" *after* "waiting". The
> code in python is attempting to access "waiting", but getting "clock_id"
> instead, hence the value of 1 being used as an address. A rebuild
> against the new pthread.h will fix this but not for old libraries.

> I will swap the order of "clock_id" and "waiting" now.

> If python is then compiled against this new pthread.h and run using an
> old unixlib, then it will allocate an object larger than necessary
> (which is OK) and "waiting" will be in the right place.

To confirm that the current python38a6, built with GCCSDK GCC 4.7.4 
Release 3, does start up with SharedLibs built from r7348.

-- 
David Pitt
Titanium



More information about the gcc mailing list