openembedded-core.git/meta/conf/machine/include/ia32, branch danny

conf/machine: Clean up configuration values.

2012-05-06T08:54:45+00:00

This cleans up and/or corrects a few values from machine includes
for consistency with future toolchain sanity checks, and also adds
the TUNEVALID and TUNECONFLICTS to documentation.conf.

Signed-off-by: Peter Seebach 
Signed-off-by: Richard Purdie

conf/machine/include: Cleanup IA tunings to match README

2012-04-04T16:01:30+00:00

We perform a basic cleanup of the IA32 architecture and related
tunings in order to match the rules and descriptions within the
new tuning README file.

A number of small issues were corrected in the "c3" tuning to
bring it inline with the README.

Signed-off-by: Mark Hatle

x86 tune: fix TUNE_PKGARCH definition for proper PACKAGE_ARCH

2011-12-12T21:50:09+00:00

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

x86 tune files: set baselib for x32 tune as libx32

2011-10-20T12:06:39+00:00

This ensures that on a multilib system the two executable formats
don't conflict.

Signed-off-by: Nitin A Kamble

arch-ia32: Add a generic x86 override (instead of i{3|4|5|6}86 and so on)

2011-10-14T23:41:00+00:00

Signed-off-by: Richard Purdie

x86 tune inc files: add x32 abi tune parameters

2011-08-08T17:05:02+00:00

Signed-off-by: Nitin A Kamble

arch-ia32.inc: Fix up TUNE_ARCH variable conflicts

2011-07-26T21:39:49+00:00

The current approach causes duplicate values to appear in the TUNE_ARCH
field and this patch addresses that.

Signed-off-by: Richard Purdie

conf/machine/include: Start to fill out architecture specific tune include files and tune features

2011-07-25T13:19:54+00:00

These changes revolve around the idea of tune features. These are represented by
'flag' strings that are included in the TUNE_FEATURES variable.

Any string included in TUNE_FEATURES should also add a TUNEVALID[] entry so
we can know which flags are available in TUNE_FEATURES and have documentation about
what the flags do. We will add sanity code to error if flags are listed in
TUNE_FEATURES but are not documented in TUNEVALID.

A given tune configuration will want to define one or more predetermined sets of
_FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-.
For defined tune configuation,  should be added to the AVAILTUNE list so that
we can determine what tune configurations are available. Flags cannot be used in this
case as with TUNEVALID since its useful to be able to build up tune lists from other
TUNE_FEATURES_tune-yyy options.

A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune- and
BASE_LIB_tune- to control the multilib location. All options can be overridden
by the distro or local user configuration.

Signed-off-by: Richard Purdie