summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* documentation.conf: sync with the Yocto Project reference manualBelen Barros Pena2014-03-071-9/+124
| | | | | | | | | | | | Make sure variables listed in the Glossary section of the reference manual are listed here. There are still some listed here that aren't in the manual; this should be fixed in the manual. (From OE-Core rev: 954e7050f602acf3dd401ca84a1b9a3b78b0ca28) Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: drop obsolete variablesPaul Eggleton2014-03-071-7/+0
| | | | | | | | | | These haven't been used for some time (and DESTDIR was never a BitBake variable at all). (From OE-Core rev: a78f6b1454598e74bdd229b0a26bbdcdfa991aa2) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add new vardepvalueexclude varflag to BB_SIGNATURE_EXCLUDE_FLAGSPaul Eggleton2014-03-071-2/+2
| | | | | | | | | | | | | We don't want the value of this varflag itself entering any signatures, ever. Part of the fix for [YOCTO #5897]. (From OE-Core rev: 1497d3d4b10844aa19ce6dcceed25aa36454160f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: update LAYERVERSION_core for core-image-full-cmdlinePaul Eggleton2014-03-071-1/+1
| | | | | | | | | | LAYERVERSION_core change to 4 means rename of core-image-basic to core-image-full-cmdline. (From OE-Core rev: d87585385bfe00dd5e7448ae7d5bc5dc7f9ac782) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Update to correctly link X modulesSaul Wold2014-03-051-0/+9
| | | | | | | | | | | Remove the -z,now flag from linking [YOCTO #5885] (From OE-Core rev: 545986bfbfe20f2b6e8a46e88e2cc3007ca344e6) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop -fpermissiveRichard Purdie2014-03-051-2/+2
| | | | | | | | | | | | Drop the -fpermissive C++ compiler flag. We've had this around for years, most code should have been fixed long ago. Its possible some recipes may fail however we can (and should) just use the flag where needed. An OE-Core world build seems to work just fine with this change. (From OE-Core rev: 24dd8e129447013ee98609f3892ec414b1b21340) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security-flags: Avoid lttng-tools issue on armRichard Purdie2014-02-261-0/+3
| | | | | | (From OE-Core rev: 010d5b437413156c3f4dc90a14698231bb195c2e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security-flags: Deal with powerpc build issuesRichard Purdie2014-02-261-0/+8
| | | | | | | | | | Building powerpc machines with the standard security flags generated numerous build failures. Use a reduced set of flags for now to avoid linker issues and other compile failures. (From OE-Core rev: 4ef8f658874282ead0c46352474fdb03ad1f1038) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: disable PIE flags for cups buildsSaul Wold2014-02-261-0/+1
| | | | | | | (From OE-Core rev: c564bffe7a32470578a22b70e868e7bec2da0a69) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro/defaultsetup: Add seperatebuildddir.incRichard Purdie2014-02-251-0/+1
| | | | | | | | | This has been in testing for long enough in various distros and setups, lets make it the default. (From OE-Core rev: 875d8d076bf7678321b847425590bbe06765bb84) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: add a few missing task descriptionsPaul Eggleton2014-02-251-0/+4
| | | | | | | | | | | We didn't really need these when the task descriptions were only used for Toaster, but now we're showing them in -c listtasks they are useful to have. (From OE-Core rev: f9d04fcab577d1f48329a4cfe51b1e73fa5d9ba2) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues (part 2)Matthieu Crapet2014-02-201-1/+1
| | | | | | | | | | | | | | | | | | Completes previous commit b5292d4115a4555a66b5e35acdc67dd71fb8577f. Updates SUMMARY[doc] (meta/conf/documentation.conf). Changes: - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR (From OE-Core rev: ad17dfd31a2b97b3e610a0ea0889f5ecb2a63b97) Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc: Upgrade from 2.18 -> 2.19Khem Raj2014-02-181-1/+1
| | | | | | | | | | | | | | | | License formatting and address for FSF in the COPYING and COPYING.LIB has changed. Dropped patched already upstream and patches that were workarounds for older glibc and busybox for e500 we have should pass --without-fp to eglibc/glibc 2.19 onwards the code is merged from eglibc into glibc upstream under nofpu/ pretext (From OE-Core rev: 875df27e56b82fcf970410b6d78e3672471c336a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add BBINCLUDED and BB_INVALIDCONF to config hash whitelistPaul Eggleton2014-02-171-1/+1
| | | | | | | | | | These variables should not influence the config hash, i.e. changing them shouldn't trigger a reparse of the metadata, so whitelist them. (From OE-Core rev: 8feb51267647d0760f5bec3a8b6f95f4481d9b0d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/bitbake.conf: default HOMEPAGE to blank instead of unknownPaul Eggleton2014-02-111-1/+1
| | | | | | | | | | | | | | | | The default value for HOMEPAGE of "unknown" has been in place since the early OE-Classic days, but it doesn't really make sense - "unknown" is not a valid URL and it just means we have to explicitly check for this hardcoded string if we're displaying the value in some form of UI, such as Toaster. This has required some changes to the packaging classes as they previously did not expect the value to be blank. (From OE-Core rev: 244e1d73ef58e92d73c098044c66bd784644b933) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.24Khem Raj2014-02-021-1/+1
| | | | | | | | | This builds and runs images for all qemu machines (From OE-Core rev: 015eca84f1b0f25868b47d2480bb60cea698f70e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add Cortex A7 support for NEONv2 & FPv4Kristof Robot2014-02-024-4/+19
| | | | | | | | | | | | | | [YOCTO #5710] Add tuning options for Cortex-A7 with NEONv2 & FPv4: - cortexa7hf-neon-vfpv4 - cortexa7thf-neon-vfpv4 (From OE-Core rev: e97d152ca13556b41a236c1a4cfb11e77ff857d7) Signed-off-by: Kristof Robot <krirobo@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: update task descriptionsBarros Pena, Belen2014-01-291-54/+107
| | | | | | | | | | | This patch updates the task descriptions in documentation.conf It also has a bunch of grammar fixes for the variable descriptions. (From OE-Core rev: 3f96e97b65bfb2505fb0127a4d6a585e9b14a3e4) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3: Fix dependencies and allow target buildsJason Wessel2014-01-291-4/+3
| | | | | | | | | | | | | | | | Fixed in this patch: * All patches marked as submitted to the upstream * Remove the pseudo dependency because unfs3 can fully stand alone or be used with pseudo and it does not link against pseudo * Dependencies to flex for nativesdk and target builds are fixed such that unfs3 can be deployed into an image * Add unfs3 references in separatebuilddir.inc because unfs3 works correctly with autotools. (From OE-Core rev: 7d8075c64bd0734cb70d16acef36c1a17276b359) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3, unfs-server: Replace all instances of unfs-server with unfs3Jason Wessel2014-01-281-2/+2
| | | | | | | | | | | | | | | Other recipes dependencies and even some comments need to be updated for the removal of unfs-server and the replacement with unfs3. The unfs3 is a complete drop in replacement providing all the prior functionality of NFSv2 but also adding NFSv3. [YOCTO #5639] (From OE-Core rev: d577c56519a448b142da5b43e46d5bd9d3a3b4bd) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* feature-arm-thumb: Fix missing t2 suffix for armv7a MACHINEsMartin Jansa2014-01-281-2/+1
| | | | | | | | | | | | | | | | | | | | | * unfortunatelly that note about armv7 matching also armv7a is no longer valid since armv7 include in armv7 was replaced with armv6+neon in this commit: commit 75b8adbc042e0f65fb1286bc550d02becd3b6aea Author: Khem Raj <raj.khem@gmail.com> Date: Tue Mar 27 18:37:45 2012 -0700 tune/armv7: Delete since then thumb and arm feeds had the same architecture * be aware that this will rename lots of feeds (From OE-Core rev: 8e8839215032b57763a07363a560c3fd9d6f8e01) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86_64: Use the core2-64 tuneDarren Hart2014-01-281-1/+2
| | | | | | | | | | | | | | | | | As x86_64 has been "demoted" to an ABI definition rather than a concrete tune file, replace it with core2-64 for the qemux86-64 machine. (From OE-Core rev: 65c1ba225a410d2ee1913d55c6f986db9f54cc8e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Typographical correctionsDarren Hart2014-01-281-3/+3
| | | | | | | | | | | | | | | | No new content, just correcting a few typographical errors. (From OE-Core rev: 8df13f5013d92954ee76943dad58db75704c3cc5) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Document best practiceDarren Hart2014-01-281-0/+19
| | | | | | | | | | | | | | | | | Describe the expected usage of base architecture tune files and arch-specific files, specifically the stacking of generations. (From OE-Core rev: 282735d7c8fcbd7e354f544c45461b095700fb77) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: README: Whitespace cleanupDarren Hart2014-01-281-44/+44
| | | | | | | | | | | | | | | | | Before making content changes, cleanup the various whitespace errors in this file. Mostly end-of-line whitepsace. (From OE-Core rev: 112e291c14ce4c3b8d074b71e63500dce609784e) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: Remove tune-x86_64.incDarren Hart2014-01-281-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tune-x86_64.inc file is conceptually flawed. x86_64 is more akin to the x86 and x86-32 ABIs defined in arch-x86.inc than it is a concrete tune file, such as i586 or core2 - to the extent that everything but the default tune is defined in the arch-x86.inc file. This becomes very apparant when attempting to include tune-x86_64.inc in the x86 tune hierarchy. Remove the tune-x86_64.inc tune file in favor of it being an ABI definition in arch-x86.inc and relying on the linear hierarchy of concrete cpu-types in tune-i586, tune-core2, and tune-corei7. core2_64 should suffice in lieu of x86_64 for all but a couple esoteric corner cases involving older pre-core2 CPUs. In these cases, if they exist at all, the BSP can replace the include tune-x86_64.inc with arch-x86.inc and set the default tune to x86_64. (From OE-Core rev: d8884649b2b3e76519bc10f5908f98d940a9c0cb) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-corei7: Add support for cpu-type corei7Darren Hart2014-01-281-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | corei7 offers a significant advancement since the previous core2 cpu-type described in the tune-core2 file. From the GCC(1): Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1 and SSE4.2 instruction set support. This offers optimizations for Nehalem and Silvermont (e.g. Bay Trail) CPUs (and beyond). (From OE-Core rev: 21f8ce2a4b94034284eb74b9c3b4c9cc638511d6) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune: Make 32b or 64b explicit in tune name for core2Darren Hart2014-01-281-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | Core2 has both a 32b and a 64b variant. Currently, core2 implies 32b, while core2_64 is the 64b version. This implicit 32b mode will become confusing in later architectures, such as corei7, where it would be natural for people to assume "corei7" meant 64 bit. Rather than carrying forward an implicit 32b mode and rather than changing the naming scheme part way through the architecture hiearchy, make the 32b and 64b variant explicit in the tune name by changing core2 to core2-32. This patch also standardises on using '-' in the names. (From OE-Core rev: 69e6395b8d11e2940892a6293ecbbe645c2a478b) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2: Only add the current ARCH to PACKAGE_EXTRA_ARCHSDarren Hart2014-01-281-1/+2
| | | | | | | | | | | | | | | | | Inherit the PACKAGE_EXTRA_ARCHS from i586 and only explicitly add core2 here. (From OE-Core rev: 2a10d570560c37eb1d23cf853c0e541bc08a2878) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2: Replace -mtune=generic with -mtune=core2Darren Hart2014-01-281-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | -march specifies which ISA to use. -mtune specifies which cpu-type to optimize instruction ordering for, but not which ISA to use. There are times when it may make sense to specify mtune=generic and use a more specific march, such as core2, but the opposite makes little sense at all: use cpu-type specific ISA, but order the instructions generically. While the -mtune is implied by -march, gcc does not verify it is using -mtune=core2 with: gcc -Q -march=core2 --help=target Explicitly specify -mtune=core2 to be sure. Add a comment header describing the CPUs targeted by this tune file. (From OE-Core rev: 4cd33193b2db6c281275db2fb5cc169181955217) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* i586: Only add the current tune to PACKAGE_EXTRA_ARCHSDarren Hart2014-01-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The generic x86 build supports i586 by default, so this specific tune file technically doesn't add any specific ARCHes to PACKAGE_EXTRA_ARCHS. For consistency, append the current tune to PACKAGE_EXTRA_ARCHS. Since we do not have specific tune files for i386 and i486, just drop them. These could be added to tune-x86 version if there is a need to maintain them, but they really do not belong here. (From OE-Core rev: 1ff914118bdfb19d7f3d794a92ba3735c06ab97b) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x86: Replace ia32 with x86 when referring to the generic architectureDarren Hart2014-01-286-16/+16
| | | | | | | | | | | | | | | | | | | ia32 implies 32bit, while these files provide descriptions for IA32, X86_64, and X32 architectures. The term "x86" fits this used better without resorting to using the term "Intel" which isn't quite right as it excludes things like the tune-c3 file describing a Via CPU. (From OE-Core rev: f5e0a574d87b7dc6466bfe01593fab5aa13464ff) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Change update-alternatives provider to opkg-utilsPaul Barker2014-01-191-3/+3
| | | | | | | | | | | | | | This allows dependencies to be added to the opkg recipe without causing circular dependency loops. As opkg-utils has minimal dependencies it is the best recipe to provide update-alternatives. This partially solves Yocto Project issue 4836. More work is still needed for a complete solution. (From OE-Core rev: 2f18289493f9c2c67ba343fb8e16743bf5dfee24) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: db can't use pie flags from gcc for security buildSaul Wold2014-01-141-0/+1
| | | | | | | | | [YOCTO #5721] (From OE-Core rev: 0cfe254e7eafed27f512216cccfb7fee76fc0be7) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* separatebuilddir: Drop cmake lines since cmake class has this as default nowRichard Purdie2014-01-141-2/+0
| | | | | | | | The changes to cmake make this unneeded now. (From OE-Core rev: 92472980b816ee9ada502c1965976cb6eedc0a27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* separatebuilddir: build libproxy and taglib out of the source treeRoss Burton2014-01-141-2/+2
| | | | | | | | (From OE-Core rev: 706084cedc73612af4feb5dd9075f1efb1b7d58c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: add the rest of the grub-efi related packagesSaul Wold2014-01-061-0/+4
| | | | | | | | | [YOCTO #5515] (From OE-Core rev: 840fd855a47b0a557911ae0542ed24a047af6d7b) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add full stop to default DESCRIPTIONPaul Eggleton2014-01-021-1/+1
| | | | | | | | | | | | | SUMMARY should not end with a full stop; however if DESCRIPTION is not set in a recipe and thus defaulted from SUMMARY, the additional DESCRIPTION values for other standard packages e.g. ${PN}-dev look a bit odd without a full stop separating the SUMMARY value and the rest of the text. Add a full stop to avoid this. (From OE-Core rev: 4b022399815f32166c402d458a40afa6470fc776) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: set a default for MACHINE_FEATURESPaul Eggleton2014-01-021-0/+1
| | | | | | | | | | | | | | Ensure that if MACHINE_FEATURES is not set by the machine config that we don't end up with expansion errors during parsing. Technically since the introduction of MACHINE_FEATURES_BACKFILL = "rtc" this is unlikely to be a problem unless "rtc" is also added to MACHINE_FEATURES_BACKFILL_CONSIDERED, however we should be consistent with DISTRO_FEATURES which is defaulted in bitbake.conf. (From OE-Core rev: bf2c8946d96524aaa91ab43762c963ea38ccc342) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude WORKDIR changes from sstate checksumsRichard Purdie2013-12-201-1/+1
| | | | | | | | | | | | | | | The layout of stamp files ensures that changes to WORKDIR mean recipes get rebuilt correctly. Since WORKDIR usually contains MULTIMACH_TARGET_SYS and that depends on tune variables, including WORKDIR in sstate checksums adds a lot of noise to the system for what amounts to no gain. On the other hand, removing it reduces noise, reduces the size of the siginfo files and reduces the amount of processing bitbake has to do. It therefore seems like dropping it from the checksums is an all around win. (From OE-Core rev: 453353e05d027c6a505d1e13a7982718a13bca8b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf-notes: remove meta-toolchain-sdk referencesSaul Wold2013-12-201-1/+0
| | | | | | | | | | | [YOCTO #5676] (From OE-Core rev: 4c81f743eb15604eb389f3ceafe7af7567a02e0d) (From OE-Core rev: 987802907ef702bfec65507b276e166f0aee59ec) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Require bitbake 1.21.1 as a minumum version for deltask ↵Richard Purdie2013-12-201-1/+1
| | | | | | | | functionality (From OE-Core rev: cdc6dfd497c7a96f8ccd666fe0b8970d5b906786) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: more relocation issuesSaul Wold2013-12-181-0/+6
| | | | | | | | | | | | These are similar relocation R_X86_64_PC32 issues that are solved by removing the -pie flags. [YOCTO #5515] (From OE-Core rev: cd94dd3d9bba32c3fd55959586128b236d1d4e34) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pointercal-xinput: Mark as SIGGEN_EXCLUDERECIPES_ABISAFEOtavio Salvador2013-12-181-0/+1
| | | | | | | | | | | | When including xinput-calibrator, in commit "xinput-calibrator: move it from meta-oe to oe-core" the pointercal-xinput has not been added to the SIGGEN_EXCLUDERECIPES_ABISAFE. This changes adds it to the meta/conf/layer.conf's file list. (From OE-Core rev: 9582ed663d12e635c02c59bff8665c929fa35656) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-sourcery-toolchain: removePaul Eggleton2013-12-124-238/+1
| | | | | | | | | | | | | | | | | As per discussion on the mailing list [1], remove this largely unmaintained external toolchain support in favour of the maintained version in meta-sourcery [2]. Also correct the example and documentation.conf entries for TCMODE to match up with this change. [1] http://lists.openembedded.org/pipermail/openembedded-core/2013-December/087133.html [2] https://github.com/MentorEmbedded/meta-sourcery/ (From OE-Core rev: 7603b15415301679bccbcb89af688c211704a43a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh scriptMartin Jansa2013-12-101-0/+2
| | | | | | | | | | | | | | | | | | * ltp installs 2 different runtests_noltp.sh files from different directories into /opt/ltp/testcases/bin/runtests_noltp.sh last one installed wins and causes unexpected changes in buildhistory's files-in-image.txt report, rename them to have unique name as other ltp scripts have. * also define PREFERRED_PROVIDER to resolve note shown when building with meta-oe layer: NOTE: multiple providers are available for ltp (ltp, ltp-ddt) NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp (From OE-Core rev: ec3bb2c2203b2e8bafc1a631f623f858779e20b7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: update for new image testing variablesRoss Burton2013-12-091-3/+1
| | | | | | | | | | | IMAGETEST is now TEST_IMAGE, and TEST_SCEN and TEST_SERIALIZE don't exist anymore. (From OE-Core rev: ce0b1ea834ee3ab2256b55fcd8b4092e091cf556) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/native.bbclass: Use FC instead of F77 for fortranRichard Purdie2013-12-051-2/+2
| | | | | | | | | | | | | gcc tooling appears to be standardising around the FC variable naming. This patch changes the F77 namespace to FC instead and use the default gfortran compiler. If anyone needs the F77 variables or tools, those can still be made on a case by case basis. Also updates local.conf.sample.extended accordingly. (From OE-Core rev: ae8c17be2845eff2be8394a5d9a45e6aa321c33d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add entry for opensslSaul Wold2013-12-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | It seems we might be stumbling over an obscure linkage issues possibly similar to http://marc.info/?l=openssl-dev&m=130132183118768&w=2 This issue appears for x86-64 systems with the PIE related compiler flags. libcrypto.a(cryptlib.o): relocation R_X86_64_PC32 against symbol `OPENSSL_showfatal' can not be used when making a shared object; recompile with -fPIC The error suggests recompiling with -fPIC, but it is already compiled that way. Disable the PIE flags makes it work for now, I have posted to openssl ML [YOCTO #5515] (From OE-Core rev: 55e1c0e66fd16612016b3e415cbfa4e3051e5a8f) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: grub-efi-natve does not build with flags enabledSaul Wold2013-11-241-0/+2
| | | | | | | | | [YOCTO #5505] (From OE-Core rev: db628ccad9db49d0e83fb534ddfb05a57132f2fa) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-15 10:22:31 +0000