diff options
| author | Nitin A Kamble <nitin.a.kamble@intel.com> | 2011-12-07 21:28:22 -0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-12-12 21:50:09 +0000 |
| commit | 1a599cc822ad517f9ba70ceb0e39c5572d37a5a6 (patch) | |
| tree | 2efc3e2b2f0c5d69ea17134ddda6fe4470308235 /meta/recipes-connectivity/bluez/bluez4.inc | |
| parent | 046f7cce366bc68ec35076ffc4c6058567e5dbaf (diff) | |
| download | openembedded-core-1a599cc822ad517f9ba70ceb0e39c5572d37a5a6.tar.gz openembedded-core-1a599cc822ad517f9ba70ceb0e39c5572d37a5a6.tar.bz2 openembedded-core-1a599cc822ad517f9ba70ceb0e39c5572d37a5a6.tar.xz openembedded-core-1a599cc822ad517f9ba70ceb0e39c5572d37a5a6.zip | |
x86 tune: fix TUNE_PKGARCH definition for proper PACKAGE_ARCH
rpmbuild can not handle the PACKAGE_ARCH of these kinds:
x86_64-x32, core2-64, core2-64-x32
With these kinds of PACKAGE_ARCH the --target parameter of rpmbuild
becomes like: core2-64-x32-poky-linux-gnux32 ; And rpmbuild extracts
%_target (arch) wrongly as core2 generating these kinds of rpms with
incorrect filenames: zip-3.0-r0.core2.rpm
So this commit fixes the issue by making PACKAGE_ARCH like this:
x86_64_x32, core2_64, core2_64_x32
Now --target parameter of rpmbuild becomes like:
core2_64_x32-poky-linux-gnux32 ; And rpmbuild extracts %_target (arch)
correctly as core2_64_x32 generating these kinds of rpms with correct
filenames: zip-3.0-r0.core2_64_x32.rpm
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Diffstat (limited to 'meta/recipes-connectivity/bluez/bluez4.inc')
0 files changed, 0 insertions, 0 deletions