In article <mpro.qxj4o2002mgv301uf.pit...@pittdj.co.uk>, David Pitt <pit...@pittdj.co.uk> wrote: > Chris Gransden, on 3 Aug, wrote:
> [snip] > > > https://github.com/jhamby/riscos-gccsdk > > > > > You probably don't want to take the patch I made to change the default > > > GCC 10 CPU/FPU target from ARMv7-A and VFPv3 to Cortex-A53 and Neon, > > > but I've tried to make everything else reasonably generic. Now, on to > > > a few areas of difficulty that I'd like to solicit some opinions on > > > how to fix. > > > > Using your patches for 10.3.0 both the native and GCCSDK build working OK > > so far. > I am not having that much luck. > gcc10.2.0 builds just fine but gcc 10.3.0 always stalls with a patch > failure. This report is from Ubuntu 20.04 on a Parallels VM on a Mac. It > also fails, but at different points, with Ubuntu 16.04, Ubuntu 20.04 and > Debian 10 (buster) on VMware Fusion VMs. > Autobuilder: RISC OS patch: > /home/parallels/riscos-gccsdk-main/autobuilder/develop/gcc/gcc.config.gcc.p > patching file gcc/config.gcc > Hunk #1 succeeded at 806 (offset 30 lines). > Hunk #2 succeeded at 1362 (offset 30 lines). > Autobuilder: Patches failed > Package gcc: ***Failure*** > Build for package "gcc" failed Part of one of the patch files needs removing. In the libstdc++-v3.acinclude.m4.p just remove the second patch. _______________________________________________ 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
