[gccsdk] New SharedLibs incompatibility

alan buckley alan_baa at hotmail.com
Wed Jul 22 08:57:33 PDT 2020

Lee Noar<mailto:lee.noar at sky.com> wrote on 22 July 2020 11:30:

> > On 22/07/2020 08:04, alan buckley wrote:
> > The new version of the shared C libraries I�ve just released alongside
> > the new GCC release for RISC OS seem to be incompatible with programs
> > compiled against the previous version of GCC.
> >
> > I tried the Python3 download yesterday against the new shared libs and
> > it crashed complaining about pthread_cond.
> >
> > Any ideas why this may be? Has the abi changed? or is it something more
> > subtle?

> The good news is that this is nothing to do with dynamic linking. The
> (mildly) bad news is that I made a mistake in r7252. I must have misread
> the spec for pthread_cond_init and changed it to reject a NULL
> attribute. In fact a NULL attribute is valid and means use the default
> values.

> > How should this be fixed?

> Fortunately, it's a fairly easy fix, and I'll have it fixed shortly.
> It effects both the shared and static Unixlib libraries, but nothing
> else.

Thanks for that Lee. How to I go about getting this into the wild?
svn update and then ./build-world?
I assume I’ll have to create GCC 4.7.4 release 5 packages as I assume
I can’t get away with just updating the shared c library package.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.riscos.info/pipermail/gcc/attachments/20200722/0d369e2c/attachment.html>

More information about the gcc mailing list