Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001083
--- Comment #3 from Sergei Gavrikov <[email protected]> 2011-01-01 19:18:10 GMT --- (In reply to comment #1) > Sergei, your proposed change looks good to me. It matches the use of > ACTUAL_CFLAGS in some other architectural HALs (arm, m68k, etc). John, my check: Have no issue: $ grep target.ld -A3 hal/*/arch/current/cdl/hal_*cdl| grep '$(ACTUAL_CFLAGS)'|cut -d- -f1 hal/arm/arch/current/cdl/hal_arm.cdl hal/coldfire/arch/current/cdl/hal_coldfire.cdl hal/m68k/arch/current/cdl/hal_m68k.cdl hal/synth/arch/current/cdl/hal_synth.cdl Expectant: $ grep target.ld -A3 hal/*/arch/current/cdl/hal_*cdl| grep '$(CFLAGS)'|cut -d- -f1 hal/cortexm/arch/current/cdl/hal_cortexm.cdl hal/frv/arch/current/cdl/hal_frv.cdl hal/i386/arch/current/cdl/hal_i386.cdl hal/openrisc/arch/current/cdl/hal_openrisc.cdl hal/powerpc/arch/current/cdl/hal_powerpc.cdl hal/sh/arch/current/cdl/hal_sh.cdl hal/sparc/arch/current/cdl/hal_sparc.cdl hal/sparclite/arch/current/cdl/hal_sparclite.cdl I was able to verify builds for next architectures: 'cortexm', 'powerpc' and 'sh' (I have no other toolchains). Unfortunately, the compilers need substitution s/CFLAGS/ACTUAL_CFLAGS/ and in other places for those archs, i.e. on preprocessing stages (where compilers generate dependencies). There are more such places for 'powerpc' and 'sh' (sh2, sh3, ...) archs. My workaround just decrements the compiler's claims and does not calm builds there. Can I take risks and make all corrections without the ability to test all? It is safe for me is to apply the fix only for 'i386' and 'cortexm' archs. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
