In article <5636098b....@aaug.net>,
   John Tytgat <john.tyt...@aaug.net> wrote:

> However, the __FUNCTION__ vs __func__ isn't a problem at all. During the 
> build you get a lot of warnings that __FUNCTION__ is not ISO C and 
> that's because of the -Wpedantic compile option.  Those are warnings, 
> not errors.  So I don't see a reason for the __FUNCTION__ to __func__ 
> rename.

> I didn't followup on the toolchain-riscos.cmake nor autobuilder project 
> changes.  Could someone else have a loop at that ?

Everything is done apart from the warning ones and oslib. Best to change
oslib upstream?


_______________________________________________
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

Reply via email to