Re: [gccsdk] GCCSDK Raspberry Pi 3 status
On 09/01/17 13:10, alan buckley wrote: I’ve just seen something in the ROOL forums implying that the SharedULib needs updating for the Raspberry Pi 3. Is this correct? I thought that programs needed recompiling, but the SharedULib module was OK. There seems to be some confusion about what SharedULib is. There are 2 separate entities; the module, SharedUnixLibrary and the library libunixlib which exists as an ELF shared library and as a static archive. The problem with SWP on the RPi3 existed in the ELF shared library and in the static archive and has been fixed. There was no problem in the module. This means that programs linked to the static archive will have to be re-linked to the fixed version. Any programs that are dynamically linked to the ELF shared library should work correctly once libunixlib in !SharedLibs is replaced with a fixed version. What is the current status of GCCSDK for the Raspberry Pi 3? Providing you are using a recent version then GCC and any code generated by it should work on the Raspberry Pi 3. Is it worth creating a new RISC OS version of !GCC so it can be used by Raspberry Pi 3 users? Or is there more to do? The version packaged on riscos.info does not include the fixes, so could do with being updated. 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
Re: [gccsdk] GCCSDK Raspberry Pi 3 status
[Reposted as it didn't make it to the list last time] On 09/01/17 13:10, alan buckley wrote: I’ve just seen something in the ROOL forums implying that the SharedULib needs updating for the Raspberry Pi 3. Is this correct? I thought that programs needed recompiling, but the SharedULib module was OK. There seems to be some confusion about what SharedULib is. There are 2 separate entities; the module, SharedUnixLibrary and the library libunixlib which exists as an ELF shared library and as a static archive. The problem with SWP on the RPi3 existed in the ELF shared library and in the static archive and has been fixed. There was no problem in the module. This means that programs linked to the static archive will have to be re-linked to the fixed version. Any programs that are dynamically linked to the ELF shared library should work correctly once libunixlib in !SharedLibs is replaced with a fixed version. What is the current status of GCCSDK for the Raspberry Pi 3? Providing you are using a recent version then GCC and any code generated by it should work on the Raspberry Pi 3. Is it worth creating a new RISC OS version of !GCC so it can be used by Raspberry Pi 3 users? Or is there more to do? The version packaged on riscos.info does not include the fixes, so could do with being updated. 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
Re: [gccsdk] GCCSDK Raspberry Pi 3 status
alan buckley, on 16 Jan, wrote: > David Pitt wrote on 09 January 2017 15:57 > > > alan buckley, on 9 Jan, wrote: [snip] > > > What is the current status of GCCSDK for the Raspberry Pi 3? > > > I have a locally built !GCC from June 2006 that is RPi3 compatible, it > > being built after the SWP fix was checked in. The build also generated > > an updated !SharedLibs which is definitely required and a SharedUlib > > which might not be. > > > > Is it worth creating a new RISC OS version of !GCC so it can be used > > > by Raspberry Pi 3 users? Or is there more to do? > > > I have not used !GCC extensively but as far as I am aware the build that > > I have is good on the RPi3. > > I’m really trying to determine if I (or someone) should produce a new > version of !GCC for the riscos info website or if it needs something else. > > The problem on the RPi3 is more extensive than just !GCC, !PDF is > > another casualty. Again I have a local RPi3 good build. > > Did you use the GCCSDK autobuilder to build !PDF? If so did you have to > make any changes to the build scripts? The autobuilder was used. !PDF builds as is, and is good on the RPi3. Revision 7084 was required. > If any of the riscos-info stuff is failing on the RPi3 and will build OK > from the autobuilder, I can build a new version and upload it. Just let me > know what the packages are, and please test them after they are uploaded > as I don’t have a RPi3. Unless there are quick fixes to the build I won’t > have time to sort them out though. Wget and !GCC also build and are OK on my RPi3. > > All of this was discussed at the time on the ROOL forum. > > I’ve seen the ROOL forum discussions, I’m trying to get input from The > GCCSDK developers as they will have a better idea of the current state of > play. -- David Pitt ___ 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
Re: [gccsdk] GCCSDK Raspberry Pi 3 status
David Pitt wrote on 09 January 2017 15:57 > alan buckley, on 9 Jan, wrote: > > I’ve just seen something in the ROOL forums implying that the SharedULib > > needs updating for the Raspberry Pi 3. Is this correct? I thought that > > programs needed recompiling, but the SharedULib module was OK. > Hmm!! I thought that about the SharedULib module too, but others would seem > to be saying otherwise. > > What is the current status of GCCSDK for the Raspberry Pi 3? > I have a locally built !GCC from June 2006 that is RPi3 compatible, it being > built after the SWP fix was checked in. The build also generated an updated >!SharedLibs which is definitely required and a SharedUlib which might not > be. > > Is it worth creating a new RISC OS version of !GCC so it can be used by > > Raspberry Pi 3 users? Or is there more to do? > I have not used !GCC extensively but as far as I am aware the build that I > have is good on the RPi3. I’m really trying to determine if I (or someone) should produce a new version of !GCC for the riscos info website or if it needs something else. > The problem on the RPi3 is more extensive than just !GCC, !PDF is another > casualty. Again I have a local RPi3 good build. Did you use the GCCSDK autobuilder to build !PDF? If so did you have to make any changes to the build scripts? If any of the riscos-info stuff is failing on the RPi3 and will build OK from the autobuilder, I can build a new version and upload it. Just let me know what the packages are, and please test them after they are uploaded as I don’t have a RPi3. Unless there are quick fixes to the build I won’t have time to sort them out though. > All of this was discussed at the time on the ROOL forum. I’ve seen the ROOL forum discussions, I’m trying to get input from The GCCSDK developers as they will have a better idea of the current state of play. 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
Re: [gccsdk] GCCSDK Raspberry Pi 3 status
alan buckley, on 9 Jan, wrote: > I’ve just seen something in the ROOL forums implying that the SharedULib > needs updating for the Raspberry Pi 3. Is this correct? I thought that > programs needed recompiling, but the SharedULib module was OK. Hmm!! I thought that about the SharedULib module too, but others would seem to be saying otherwise. > What is the current status of GCCSDK for the Raspberry Pi 3? I have a locally built !GCC from June 2006 that is RPi3 compatible, it being built after the SWP fix was checked in. The build also generated an updated !SharedLibs which is definitely required and a SharedUlib which might not be. > Is it worth creating a new RISC OS version of !GCC so it can be used by > Raspberry Pi 3 users? Or is there more to do? I have not used !GCC extensively but as far as I am aware the build that I have is good on the RPi3. The problem on the RPi3 is more extensive than just !GCC, !PDF is another casualty. Again I have a local RPi3 good build. All of this was discussed at the time on the ROOL forum. -- David Pitt ___ 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
[gccsdk] GCCSDK Raspberry Pi 3 status
I’ve just seen something in the ROOL forums implying that the SharedULib needs updating for the Raspberry Pi 3. Is this correct? I thought that programs needed recompiling, but the SharedULib module was OK. What is the current status of GCCSDK for the Raspberry Pi 3? Is it worth creating a new RISC OS version of !GCC so it can be used by Raspberry Pi 3 users? Or is there more to do? 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
