On Sat, Sep 15, 2012 at 08:27:14PM +0100, Martin Bazley wrote: > The problem with collaborative projects like GCC (currently marked > 'Seems OK') is that it's difficult to know who to ask, or indeed if > there is anybody to ask. (The response I got from the NetSurf team was > that "you have just as much right as anyone else to declare it > compatible".) Hence this post.
Generally everything GCC-related is tagged 'GCC developers', with the email address of this list. So this is the best place to ask. > So, from someone who feels qualified to answer, would it be OK to change > GCC's status to 'ARMv7 OK' and 'Supported'? Also, which is the earliest > version of GCC which is ARMv7 compatible? The question is more complex than you might expect, because the compiler may run on an ARMv7 system but still generate code that isn't ARMv7 compatible. John Tytgat is the person to give you a definitive answer and he'll probably be along in a minute, but AIUI it's GCC 4.1.2 release 1 which both runs and generates suitable code. > And finally, since I'm not sure where the best place to ask about this > is either, what's the status of the riscos.info packages of ported > software, such as wget, DosBox, etc.? Are they compatible, are they > supported? Is there any way of finding out for a given package who's > responsible for fixing the software? I'm gradually working my way through rebuilding them (nontrivial for various reasons). To a first approximation, if you look at the filesystem: http://www.riscos.info/packages/arm/ anything with a date of 2012 is likely to work, but earlier builds are unlikely. As for responsibility for maintenance, it's collectively 'GCC developers' again. Which is both everyone and, worst case, no-one. You can look into the SVN logs[1] to see who committed the original package and they might have more motivation to fix it, but generally the first place to complain if something's broken is here. Theo [1] http://www.riscos.info/websvn/listing.php?repname=gccsdk&path=/trunk/autobuilder/ _______________________________________________ GCCSDK mailing list [email protected] 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
