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.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Wednesday, 22 July 2020
[gccsdk] New SharedLibs incompatibility
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?
How should this be fixed?
I'm wondering about asking the few people who are shipping things that use the shared libraries to update there apps to use the new versions, but this may be asking too much.
If not, we need to ship a new version of the Shared libraries with a new version number and in a new package. Will we need new shared libraries for everything that depends on them (like Qt) as well?
Regards,
Alan
Wednesday, 15 July 2020
Re: [gccsdk] Can someone fix libsdl-mixer1.2?
On 14/07/2020 19:34, Alan wrote:
> I have been trying to get libsdl-mixer1.2 to build in the autobuilder
> without success.
>
> The problem seems to be that it won't build the VFP version of the
> shared libraries. I've looked about but couldn't see any obvious problems.
>
> Can someone else have a look and see what the problem is and fix it please?
Hi Alan,
Make sure you have RO_SHAREDLIBS=yes in the build-setvars file in your
build directory. If not, then a lot of the libraries will not build
with shared libraries. Having just started from scratch to look at
your problem, I made the mistake of forgetting it and experienced
the same issue as you. Now that I've added it, libsdl-mixer1.2 builds
successfully (you'll have to rebuild all its dependent libraries as
well).
For libtiff, I also had to remove the AB_CONFLAGS='--disable-static'
line from setvars otherwise it fails to build with the error "Unable
to stat dummy.o". I haven't committed it because I don't know why that
line was added in the first place.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> I have been trying to get libsdl-mixer1.2 to build in the autobuilder
> without success.
>
> The problem seems to be that it won't build the VFP version of the
> shared libraries. I've looked about but couldn't see any obvious problems.
>
> Can someone else have a look and see what the problem is and fix it please?
Hi Alan,
Make sure you have RO_SHAREDLIBS=yes in the build-setvars file in your
build directory. If not, then a lot of the libraries will not build
with shared libraries. Having just started from scratch to look at
your problem, I made the mistake of forgetting it and experienced
the same issue as you. Now that I've added it, libsdl-mixer1.2 builds
successfully (you'll have to rebuild all its dependent libraries as
well).
For libtiff, I also had to remove the AB_CONFLAGS='--disable-static'
line from setvars otherwise it fails to build with the error "Unable
to stat dummy.o". I haven't committed it because I don't know why that
line was added in the first place.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Tuesday, 14 July 2020
[gccsdk] Can someone fix libsdl-mixer1.2?
I have been trying to get libsdl-mixer1.2 to build in the autobuilder
without success.
The problem seems to be that it won't build the VFP version of the
shared libraries. I've looked about but couldn't see any obvious problems.
Can someone else have a look and see what the problem is and fix it please?
Thanks,
Alan
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
without success.
The problem seems to be that it won't build the VFP version of the
shared libraries. I've looked about but couldn't see any obvious problems.
Can someone else have a look and see what the problem is and fix it please?
Thanks,
Alan
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Monday, 13 July 2020
Re: [gccsdk] RISC OS GCC 4.7.4 release 4 has been released
Lee Noar wrote on 12 July 2020 12:32:
> There is a native RISC OS version of GCC 8 now (autobuilder/develop/gcc),
> so perhaps we could look at doing a release of that. It produces a
> skeleton !SharedLibs with just the new runtime libraries and this is
> merged into to the GCC 4 !SharedLibs (so not standalone).
> The two !GCCs would need to be kept separate though I think,
> I've not looked at how to run two different versions of the
> compiler from the same !GCC.
I wonder if we should just have a !GCC8 and it's expected the user will
boot the correct one or double click on it before compiling to switch
the tools used.
The shared library packaging won't be a problem. I think we just need
a package with the GCC8 shared libraries that depends on the basic
SharedLibs package.
Regards,
Alan
Sunday, 12 July 2020
Re: [gccsdk] RISC OS GCC 4.7.4 release 4 has been released
Lee
Many thanks for all your support of GCC, it will be great to have Fortran back on RISCOS once again. Norman
On Mon., 13 Jul. 2020, 02:35 Lee Noar, <lee.noar@sky.com> wrote:
On 12/07/2020 13:57, Norman Lawrence wrote:
> Hi Lee
> I understood that the GCC 4.7.2 also has Fortran, is that not the case?
> I know that the Linux version comes with Fortran.
Yes, I will try and enable it it GCC4, if it builds as well as it did in
GCC8, then it shouldn't be a problem.
Sorry about the mix up, looking back I can see we were talking about
different GCC versions.
Lee.
Re: [gccsdk] RISC OS GCC 4.7.4 release 4 has been released
On 12/07/2020 13:57, Norman Lawrence wrote:
> Hi Lee
> I understood that the GCC 4.7.2 also has Fortran, is that not the case?
> I know that the Linux version comes with Fortran.
Yes, I will try and enable it it GCC4, if it builds as well as it did in
GCC8, then it shouldn't be a problem.
Sorry about the mix up, looking back I can see we were talking about
different GCC versions.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> Hi Lee
> I understood that the GCC 4.7.2 also has Fortran, is that not the case?
> I know that the Linux version comes with Fortran.
Yes, I will try and enable it it GCC4, if it builds as well as it did in
GCC8, then it shouldn't be a problem.
Sorry about the mix up, looking back I can see we were talking about
different GCC versions.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Subscribe to:
Posts (Atom)