summaryrefslogtreecommitdiffstats
path: root/package/postgresql/S50postgresql
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-05-24 21:59:37 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-05-24 23:26:25 +0200
commitb71bdd68562f82db9d5515de1ca4a33789c05cb9 (patch)
tree099076b144bf6029be52e5146df76bc0887cb664 /package/postgresql/S50postgresql
parent8bf947e0ef62362cda991537520b94a090a652ca (diff)
downloadbuildroot-b71bdd68562f82db9d5515de1ca4a33789c05cb9.tar.gz
buildroot-b71bdd68562f82db9d5515de1ca4a33789c05cb9.zip
oprofile: not available on Microblaze
Commit c45979c732cb610ad5d54e23dd7d4d49e519d45b marked OProfile as not available on the Xtensa architecture, due to the lack of memory barrier operations. This commit does the same for the Microblaze architecture, for the same reason, which allows to fix the following autobuilder failure: http://autobuild.buildroot.org/results/9a872ddc906e9d552d30762e849a1b537b4e5095/ It is worth mentioning that most likely Xtensa and Microblaze are architectures implementing a strongly-ordered memory model, in which case we could define the memory barriers as no-ops. But until someone who actually cares about OProfile on Xtensa and Microblaze shows up, it's probably better to disable the package on those architectures. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/postgresql/S50postgresql')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud