diff options
| author | Joseph Myers <joseph@codesourcery.com> | 2017-12-19 00:08:49 +0000 |
|---|---|---|
| committer | Joseph Myers <joseph@codesourcery.com> | 2017-12-19 00:08:49 +0000 |
| commit | 8e52f573a1e0c2c39968051bcf683805540deb03 (patch) | |
| tree | 03c07d8f0085b30e69cf1fd3da04142dbac898ec /scripts/merge-test-results.sh | |
| parent | 40c4162df6766fb1e8ede875ca8df25d8075d3a5 (diff) | |
| download | glibc-8e52f573a1e0c2c39968051bcf683805540deb03.tar.gz glibc-8e52f573a1e0c2c39968051bcf683805540deb03.tar.xz glibc-8e52f573a1e0c2c39968051bcf683805540deb03.zip | |
Fix build-many-glibcs.py arm-linux-gnueabihf builds with mainline GCC.
My fix to make the arm-linux-gnueabihf build-many-glibcs.py builds actually use the hard-float ABI as intended showed up another issue when building with mainline GCC: GCC now determines an FPU based on the selected CPU or architecture and gives an error for -mfloat-abi=hard when the CPU does not imply a choice of FPU. This patch fixes all the affected configurations to specify a suitable --with-cpu, --with-fpu or -mfpu option explicitly to avoid that error from GCC. Tested the relevant configurations with build-many-glibcs.py with mainline GCC. * scripts/build-many-glibcs.py (Context.add_all_configs): Specify CPU or FPU for ARM hard-float configurations.
Diffstat (limited to 'scripts/merge-test-results.sh')
0 files changed, 0 insertions, 0 deletions