It's possible - the amount allocated to GCC has been set to the maximum Sourcery allows (16Mb) - with plenty of RAM left.
It's possible that it is no longer compatible with RISCOS 5 (or some part of the emulator) - the author has stated that a bug which stops compilation every so often is present, but won't be fixed as it is not being updated. Sent from my Android mobile On 12 May 2016 7:03 p.m., "Lee Noar" <leen...@sky.com> wrote: > On 12/05/16 09:28, TheReal GamePlayer wrote: > >> The generated command line is : >> >> Setting target as '26 / 32 bit independent' for 'Triority' >> >> gcc -c -MD -fPIC -O2 -Wunused -Wuninitialized -Wall -mthrowback - I >> HostHS::HostFS.$.Public.Programming.C.Triority.Source - I >> HostFS::HostFS.$.Apps.Library.!SDL.SDL - I >> HostFS::HostFS.$.Apps.Library.!SDLGFX.SDL -I <Sourcery$LibPrefix0> -o >> @.o.Triority @.cc.Triority >> >> Failed to init stdio >> gcc: internal compiler error: hangup (program cc1plus) >> >> I suspect that Sourcery isnt really compatible with the latest version >> of GCC... >> > > I wonder if it's a memory problem. Memory exhaustion seems the most > likely reason that stdin, etc, would fail to initialise. If Sourcery is > in charge of allocating memory to the process, is it giving it enough? > I realise that GCC should complain if it doesn't have enough memory, > but it might be worth checking. > > 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 >
_______________________________________________ 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
