Comment 3 for bug 2036757

Revision history for this message
Paul Mars (upils) wrote (last edit ):

On Mantic, with gcc (Ubuntu 13.2.0-3ubuntu1) 13.2.0 I was able to determine that the -fcf-protection flag os only working with -march=i686, and not previous x86 arch with:

- gcc -dM -E -x c -fcf-protection -m32 -march=i686 /dev/null

no error

- gcc -dM -E -x c -fcf-protection -m32 -march=i386 /dev/null

cc1: error: '-fcf-protection' is not compatible with this target

At this point I see 2 possible solutions:

- patch syslinux to set -fcf-protection flag to none. But I need to understand why this flag end up in the gcc command line in the first place.
- patch gcc to exclude -fcf-protection when targeting anything lower than i686. But I understand that was the goal of the patch to solve LP: #1940029. So I may miss something.