summaryrefslogtreecommitdiffstats
path: root/package/postgresql
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-04-21 09:57:00 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-04-21 09:57:00 +0200
commite3de3ae58e830729bde1fcdc7da634567f4f3fa2 (patch)
treeef0b6b1ed94556627855586d618a5b74b6a05518 /package/postgresql
parent95264cc0ca88944501f73b4b19f731003997251a (diff)
downloadbuildroot-e3de3ae58e830729bde1fcdc7da634567f4f3fa2.tar.gz
buildroot-e3de3ae58e830729bde1fcdc7da634567f4f3fa2.zip
mplayer: fix ARM floating point related build failures
This commit fixes two separate, but related build failures: * A failure that was happening when the ARM CPU supports NEON, floating point is enabled, but not with the NEON FPU. In this case, the NEON ARM assembly is rejected by the assembler, with messages like "Error: selected FPU does not support instruction -- `vmul.f32 q0,q0,q1'". To fix this, we pass -mfpu=neon when we build mplayer with NEON support. Fixes: http://autobuild.buildroot.org/results/257/257a10e9cb5022bb09e0c6a03844be5b5b3e0bd4/ * A failure that was happening when the ARM CPU supports NEON, but the configuration is anyway using soft-float. In this case, mplayer attempts to compile NEON floating point instructions, but this obviously fail in a soft-float context, with errors such as 'Error: selected processor does not support ARM mode `vmov d0,r7,r8''. To fix this, we do not allow NEON to be enabled when we are in a soft-float configuration. Fixes: http://autobuild.buildroot.org/results/7b3/7b3c89fcd496c0bc80063f63ecd58c827e8077ea/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/postgresql')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud