summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* linux-libc-headers: ptrace.h: remove ptrace_peeksiginfo_argsBruce Ashfield2013-08-262-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The addition of ptrace_peeksiginfo_args to the uapi in kernel commit 84c751bd [ptrace: add ability to retrieve signals without removing from a queue (v4)] means that existing applications using glibc versions that define ptrace_peeksiginfo_args in sys/ptrace.h will get duplicate structure definitions like: | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:66:0: | /poky-master/build/tmp/sysroots/qemux86/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args' | struct ptrace_peeksiginfo_args { | ^ | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/defs.h:159:0, | from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:37: | /poky-master/build/tmp/sysroots/qemux86/usr/include/sys/ptrace.h:191:8: note: originally defined here | struct ptrace_peeksiginfo_args | ^ | make[2]: *** [process.o] Error 1 Reverting to the previous status of not exporting this structure temporarily fixes applications, until they can be adjusted to not mix sys/ptrace.h and linux/ptrace.h includes. (From OE-Core rev: 7c207e4c3c0e3b575c67a302b97b0dc700a8fc15) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v3.10Bruce Ashfield2013-08-263-9/+8
| | | | | | | | | | | | Now that the 3.10 kernel has been released we can bump the libc-headers to that version and remove the 3.8 variant. Userspace compatibility is maintained through kernel versions, we also make the single 3.10 version the toolchain default. (From OE-Core rev: 4e79a46254e778f85c00efd4b0085cbaeb6e0d4d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* guilt: update to latest git versionBruce Ashfield2013-08-2614-869/+26
| | | | | | | | | | | | | | | | | Uprev guilt to the latest guilt version from its upstream repository. As part of the uprev all of the previous changes required for the yocto kernel tools to use git to manipulate series files have been dropped. These changes were specific to circumventing parts of guilt's internal santiy checking to allow specific Yocto kernel manipluation of sub-series files. Since the kernel tools no longer need guilt, we can use an up to date and nearly pure upstream version of guilt. (From OE-Core rev: 595c4469adc36d88ba2403915fc6c1d355014a58) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: usability, bug fixes and no guiltBruce Ashfield2013-08-262-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the kern-tools SRCREV to pick up the following fixes: 60a894e kgit-s2q: add proper commit ID handling for mixed am/apply usage 3b08257 kgit-s2q: delete pruning of path support. c5868b4 kgit-s2q: Restore implicit exit status to "git apply" section 1bd00b9 kgit-scc: mask warnings from cleanup phase 5 bb75299 kgit-s2q: fix commit warp when running "git am --abort" ef9571b kgit-scc: cleanup git rebase-apply dir fdb7d21 kgit-scc: ensure treegen stops if a meta series fails 008987b config: add kconfig cleaning options 69ff569 kgit-s2q: strip blank lines and comments e7b4540 kgit-init: disable garbage collection on a new tree 417eaed kgit-s2q: delete old LTSI patch dir finding code 21f2200 kgit-scc: better error checking on resume ad5084c kern-tools: use .meta as meta data container 1deb5d8 kgit-meta: don't push patches without a series file eb431a1 kgit-s2q: aid patch reject resolution via helper scripts f859c40 kgit-s2q: only use patch annotations when explicitly asked 333ae18 kgit: speed patch application by batching patches bf6991d kgit: teach tools about non-default meta dirs bcfc712 kgit-s2q: usability improvements cb28803 kgit-s2q: fix patch prefix stripping. 37f40e1 kgit-s2q: warn/exit with error if patch not in series f4704d2 kgit-s2q: consistent rm usage e11819c kgit-s2q: standardize on use of git mailinfo 36a5eda kgit: remove guilt dependency c461a4f spp/scc: export mark commands to meta-series 5311162 updateme: ensure that generated features are only used once 4f7a263 kgit-checkpoint: clear .gitignore for meta branch 21ee6f2 updateme: enforce a matching machine b08749d kgit-scc: remove -meta files after consruction These are bug fixes, usability changes as well as the removal of the guilt dependency. During the uprev of the guilt package, the amount of circumvention of the typical guilt workflow and checks meant that using it as a series -> branch manager was no longer appropriate. As a result a new tools kgit-s2q (series 2 queue) was created based on git-quiltimport, git am, and the LTSI tree generation scripts. The result is better series to branch validation, faster application and a simpler management model. This tool is backwards compatible with any tree previously constructed with guilt. We are now "guilt free" (From OE-Core rev: 983bff587b60fdd0244ad00f238df5ed50cc1e1a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add memory resident bitbake scriptRichard Purdie2013-08-261-0/+55
| | | | | | | | | | | | | | | | | | | | | | | | This adds an init script which instead of the standard bitbake, launches a memory resident bitbake, defaulting to port 12345. It expects a port number to use as the first option. Right now this is experimental but I think its probably worth wrapping up in a form people can more easily experiment with it. There are some known issues: a) It throws some debug output due to the lack of a UI which we need to clean up b) It should probably be able to auto select a free port c) You get a nice backtrace if you specify a build directory but not a port number I'd also highlight there are security issues here if you don't trust users who can connect into localhost. We might need to look at named pipes or something similar for something limited to the current user. (From OE-Core rev: 52c7f8bba86a43b89f24a23d545c99d75b67555f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: Updated figure for conf/compile detailsScott Rifenbark2013-08-262-0/+0
| | | | | | | | | | | | Fixes [YOCTO #2808] Updated the figure per Paul Eggleton's feedback to be clearer. The figure resides in both the ref-manual and the mega-manual. (From yocto-docs rev: 8a0f391c9404582b3b7f62d740d5c0488a6220be) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-project-qs, adt-manual: Updates to toolchain installer scriptScott Rifenbark2013-08-262-26/+51
| | | | | | | | | | | The way in which the toolchain installer scripts are named has changed. I have updated two sections that describe this so that the new naming scheme is used. (From yocto-docs rev: 71b70a12c72bca7cad565b5d6f44b2c6b311844d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Reset the toolchain variable.Scott Rifenbark2013-08-261-1/+1
| | | | | | | | | | I had to undo this change. The variable that points to the toolchains still needs to be in place. (From yocto-docs rev: 56382d447ef838ec50bae476d026016dabb4663b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Changed the toolchain variableScott Rifenbark2013-08-261-1/+1
| | | | | | | | | | | | Updated the YOCTO_TOOLCHAIN_DL_URL variable to be set to "&YOCTO_RELEASE_DL_URL;/buildtools/". This variable used to be set to "&YOCTO_RELEASE_DL_URL;/toolchains/". The naming scheme has changed for where toolchain installers are now built. (From yocto-docs rev: 376cce752784da6fbb1bdbf655c7f40d9766e9e4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Makefile: Added new figure for package creation.Scott Rifenbark2013-08-261-2/+4
| | | | | | | | | | | | | Fixes [YOCTO #2808] The new section on package creation required a new figure. I added the figure to the TARBALL creation part for both the ref-manual and the mega-manual. (From yocto-docs rev: 3e752dd95659282833519bff866adc940a156ba7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: New section on package creationScott Rifenbark2013-08-263-0/+54
| | | | | | | | | | | | | | Fixes [YOCTO #2808] Added a new section to the expanded discussion on how builds are done. This section is on package creation. A new figure was added to both the ref-manual and mega-manual figures directories. (From yocto-docs rev: e31e5aeb7d93f3cfa4fc9c12e324f03a27b5f8ed) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Makefile: Added figure to the ref-manual and mega-manualScott Rifenbark2013-08-261-2/+2
| | | | | | | | | | | | | | Fixes [YOCTO #2808] A new figure named configuration-compile-autoreconf.png was introduced in a new section. Thus, the figure had to be added to the tarball creation for both the ref-manual and the mega-manual. (From yocto-docs rev: aa0967ee49fa5d8053e14e0cc229b47a0e65b1f9) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: new section on config/compile for expanded buildScott Rifenbark2013-08-263-0/+59
| | | | | | | | | | | | | | Fixes [YOCTO #2808] Added a new section on configuration and compilation for the expanded discussion for the build process. This involved a new figure that had to be added to both the ref-manual and mega-manual figures directories. (From yocto-docs rev: 9ba90c79990b79226d6e95e4a01ddedeccb94b35) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: Updated figuresScott Rifenbark2013-08-262-0/+0
| | | | | | | | | | | | Fixes [YOCTO #2808] Updated a couple figures to be consistent for how directories and their contents are displayed. (From yocto-docs rev: 5a3d08b2543c5ea1f76d65d67bf8a5615f6b5a0e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Makefile: Updated with new figure.Scott Rifenbark2013-08-261-2/+3
| | | | | | | | | | | | Fixes [YOCTO #2808] Had to add the patching.png figure to the TARBALL for the mega-manual and the ref-manual. (From yocto-docs rev: fe51c2c76f364956683c484527e245a745920dc1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: New section on patching for expanded build processScott Rifenbark2013-08-263-0/+35
| | | | | | | | | | | | | | Fixes [YOCTO #2808] Added a new sub-section to the BitBake section that takes a closer look at the build process. Part of the requirements was a new figure that had to be added to both the ref-manual and the mega-manual figures directories. (From yocto-docs rev: c40476b079cf5765b8228502f0ef33072f8b2b85) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, Makefile: New section on BitBake for expanded buildScott Rifenbark2013-08-264-2/+74
| | | | | | | | | | | | | | | | | | Fixes [YOCTO #2808] Created a new section called "BitBake" that will provide an expanded discussion of the basic YP build process. The "BitBake" section has a new sub-section called "Source Fetching." Part of the new section is a new figure named source-fetching.png. The figure must reside in the "figures" directory in both the ref-manual and the mega-manual. It must also be listed for each of these manuals in the TARBALL statement in the Makefile. (From yocto-docs rev: 41eff3e755a98ff31cadccfb1cd7dfcf569b4d9e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed syntax in the S variable.Scott Rifenbark2013-08-261-1/+1
| | | | | | | (From yocto-docs rev: 00fc96c2b5a03e4a32972b5f295fb70411a4e08f) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-manual: Removed the gmae stuffScott Rifenbark2013-08-261-7/+4
| | | | | | | | | | | According to Ross, we are not going to have gmae as part of the toolchain installers. So, I removed a couple instances of the filenames and then the mentioning of it when building the installer. (From yocto-docs rev: 70407feda9382fa8226142881e18f282764638be) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, adt-manual: Minor edits from review.Scott Rifenbark2013-08-262-11/+13
| | | | | | | | | | | | | | | | | Fixed some wordings in the ADT manual to remove "Intel-based" so as not to be biased. Added "x86" to qualify the types of systems in the toolchain examples. Added minor wording to the IMAGE_TYPES variable. Changed some wording for the IPK_FEED_URIS varilable. (From yocto-docs rev: 1fa7e0000591bec7e3d0b682df02b95dbee3d4f1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: updated the note about what distros we supportScott Rifenbark2013-08-261-1/+2
| | | | | | | | | | | | Fixes [YOCTO #4927] Added some minor wording to the note to indicate that we currently have no plans to support rolling releases. (From yocto-docs rev: d3b7b4791c01ce01ac9e50c78e9223955eb9b3f2) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: minor edit to the PKGDEST variable.Scott Rifenbark2013-08-261-1/+1
| | | | | | | (From yocto-docs rev: 027b73857c76dd34b1559eda9705531d531c806b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mpc8315e-rdb: Set PREFFERED_VERSION to a version thats known workingSaul Wold2013-08-261-1/+1
| | | | | | | | | | | While adding the last version, the 2012.04 version was accidently removed, it was not noticed becuase the 2011.06 version also works correctly. When we next have a tested u-boot against this core bsp, we can either drop or update this setting (From meta-yocto rev: 79a8960aa43964ebf3f3cb4621ce10c872807cc9) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: switch genericx86 to use common-pcRoss Burton2013-08-241-1/+3
| | | | | | | | | The common-pc machine is now more featureful, so switch from atom-pc to common-pc. (From meta-yocto rev: 98fb095f97fa73ef458977cac4e83c802a5a1044) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: remove genericx86 support from 3.4Ross Burton2013-08-241-2/+0
| | | | | | | | | 3.4 doesn't actually support genericx86, so remove any mention of it. (From meta-yocto rev: 3efb25d4a9a42591e9f92acad7339bb4e28e27e8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv/serv: Fix pid file removalRichard Purdie2013-08-231-1/+1
| | | | | | | | | | Mark Hatle spotted there were pid files being left around. This patch fixes things so the removal function is called correctly, the code contained a typo. (Bitbake rev: c696a16c8200c31c52750037eeafe07e065b6517) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: event/msg: Add primitive server side UI log record filteringRichard Purdie2013-08-232-2/+30
| | | | | | | | | | | | | | | | | | | | Currently one of the bigger bottlenecks in bitbake is passing all the log messages over IPC to the UI. This is worthwhile if the UI is going to use them, pointless otherwise. The memory resident bitbake suffers from this performance issue particularly badly. This patch filters the log events on the server side with the global log levels and hence reduces the traffic. This speeds up parsing (18.5s down to 17s) and bitbake general command overhead is reduced (7.3s for a NOP to 6.2s). What isn't added here is general event filtering or the ability to change the log levels once set. Provision is made for adding this in a follow up patch though. (Bitbake rev: 1bf0e88f57ba0bca62532e81d0d62cf88e2abcbb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: build.py: create symlink for run.do_xxx scriptsNicolas Dechesne2013-08-231-0/+14
| | | | | | | | | | | | | | | | | | | | | | The 'courtesy' symlink for log.do_xxx are quite useful when debugging, so with this commit, we now get similar 'courtesy' symlink for run.do_xxx scripts. We only create symlink for tasks, not individual functions. The symlink is create right before the actual runfile is created, indeed we cannot create the symlink right after running the task since a failure or execption can happen, in which case the symlink wouldn't be created, and symlink are particularely useful when the task failed! Another option would be create the symlink after the runfile is created, and before the script is executed, but that means we need to duplicate the code in case of Shell vs Python task. (Bitbake rev: a672b39c5d529ba85d72eee8fef4c4273eaa5397) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Fix the relative symlink replacement codeRichard Purdie2013-08-231-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | ant reported on irc that the sstate absolute to relative symlink creation code wasn't working in klibc. He was correct although the level of breakage is rather surprising since it only worked for one level of symlink (usr/include) with everything else being broken. The reason is probably that nothing really uses absolute paths, we use relative paths where at all possible already. Nothing in the target sysroot should use absolute paths for a start. In this regard, the klibc-dev package is broken and needs fixing. It will currently break when building for one machine, then switching to another of the same TUNE_PKGARCH and installing from sstate but that is a separate issue. This patch fixes the symlink creation code by firstly passing in the correct value we need (where the symlink will end up) and seccondly, actually using it. I've also tweaked the debug message to contain appropriate information and got right of the double "//" value the existing code created in favour of the form './..' which looks neater. (From OE-Core rev: 9b05c65450526522d7358d0c0901b594de546748) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xdg-utils: add runtime dependency on xpropCristian Iorga2013-08-231-0/+1
| | | | | | | | | xprop is called by xdg-utils scripts. (From OE-Core rev: 58d05c817cf3be071c66c7e4dbbb9942fd7a0752) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-self-hosted: pcmanfm and xdg-utils integrationCristian Iorga2013-08-231-0/+2
| | | | | | | | | | | PCManFm file manager is integrated in Build Appliance; xdg-utils is also integrated for file association support. (From OE-Core rev: a031523eb072df8f04dbae296a44ad51268acdf4) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes-graphics/builder: fix wrong user nameCristian Iorga2013-08-231-1/+1
| | | | | | | | | | | Fix wrong inclusion of local username. The right "builder" user is now used in builder_hob_start shell script. (From OE-Core rev: 0b0d48a4b8af310d1f6eabf2c4d459cda1c2b4bb) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-self-hosted: Add the sato icon themeCristian Iorga2013-08-231-0/+2
| | | | | | | | | | | | | Hicolor icon theme does not properly displays icons for folders in Build Appliance. Sato icon theme is working correctly. Also, settings-daemon needs to be added to image in order to properly display folder icons. (From OE-Core rev: a5188962c4ce6312fd625c2ab9601c24765255ed) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc-options.inc: Fix string optionsAndrei Gherzan2013-08-231-2/+2
| | | | | | | | | | Add quotation marks for OPTION_EGLIBC_NSSWITCH_FIXED* options. If not, Kconfig will ignore the value and will use the default one which is "". (From OE-Core rev: 53f48a7aadc807a75c34fe72de7497790ba19ee5) Signed-off-by: Andrei Gherzan <andrei.gherzan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc.inc: Remove quotation marks from OPTION_EGLIBC_NSSWITCH_FIXED_*Andrei Gherzan2013-08-231-0/+4
| | | | | | | | | | | | | Kconfig outputs strings with quotation marks. When eglibc tries to see if the paths exists, uses wildcard make function which doesn't strip out the quotation marks - checking for path fails. So strip out the quotation marks from OPTION_EGLIBC_NSSWITCH_FIXED_* option-groups.config. (see nss/Makefile) (From OE-Core rev: eacf0f3ed15eccb52eb6b98e20b75f0aa26b6e81) Signed-off-by: Andrei Gherzan <andrei.gherzan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Set the preferred provider for bluezCristian Iorga2013-08-231-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a need for a default provider for bluez now that bluez5 recipe is also present. After the introduction of bluez5 recipe, the following warnings are displayed: "NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez" Upon debug, bitbake shows: DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5'] Bitbake is faced with the question "what should provide libasound-module-bluez?" which is a runtime name. It needs to try and find a PREFERRED_PROVIDER entry which matches this but those use *build time* naming. So it converts "libasound-module-bluez" into the canonical ${PN} of bluez4 and bluez5 and then tries to look those up. What it actually should do is go one step further of mapping bluez4/bluez5 into the virtual/bluez but that does not happen. Bug opened on this issue: YB5044 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044 [YOCTO #5030] (From OE-Core rev: 6f07d066074b1e01ff3c16408812e6b6d5e531ac) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-4.8: Add two patches to deal with cross-canadian build failuresRichard Purdie2013-08-233-0/+139
| | | | | | | | | See the patch headers for more information about the cross-canadian build failures these patches avoid. (From OE-Core rev: 2bae60b8a3cb7783c06e35a2962e56110e876957) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* chrpath: Add support for relocating darwin binariesRichard Purdie2013-08-231-50/+88
| | | | | | | | | | On darwin, install_name_tool can be used to relocate binaries/libraries. This adds support for adjusting them with relative paths rather than hardcoded ones. The Linux code is factored out into a function but is otherwise unchanged. (From OE-Core rev: ed5ace3437eb0f751172e6b93399639c94b89e59) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop darwin8/darwin9 usageRichard Purdie2013-08-233-6/+1
| | | | | | | | | | | There were darwin8/darwin9 overrides spinkled in the code from times gone by. Lets settle on the darwin override and remove the others since its pointless duplication. We always inject darwin into OVERRIDES if needed in the darwin8/9 cases. (From OE-Core rev: 8d5e6eed7802a6056f9eaa50a85e3eee00fe2742) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Work around dev symlink problems on darwinRichard Purdie2013-08-231-6/+9
| | | | | | | | | | | | | | | | | | | | | | On darwin, we have: libxxx.dylib -> libxxx.Y.dylib compared to Linux which has: libxxx.so -> libxxx.so.Y Our ordering of PACKAGES with -dev first and then ${PN} makes it impossible to match the files correctly using simple globbing. This makes darwin targets completely broken since both the libs and the dev symlinks end up in ${PN}-dev. Whilst this commit is a hack, it at least puts the files into ${PN} and allows the builds to be used. Symlinks don't take up much space so this isn't the end of the world. I'm open to better solutions to this. (From OE-Core rev: 51c3dbe2df45096bbd7866adabb08e114952ff13) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-common.inc: Drop unused LIBGCCS_VAR variableRichard Purdie2013-08-231-3/+0
| | | | | | (From OE-Core rev: b1449f6e5be13a8c58bf38302236091d046f0215) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross.inc: Clean up after mergeRichard Purdie2013-08-231-30/+18
| | | | | | | | | | * Remove the duplicate EXTRA_OECONF_PATHS that is overwritten * Merge the do_compile and do_compile_prepend * Group dependency and configuration variables together (From OE-Core rev: 430b1d6fcbf60df35036fe5bbf8e55f7fb8f5341) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fold configure-sdk and package-sdk into the main .incRichard Purdie2013-08-233-127/+125
| | | | | | | | | This also has the advantage of removing the confusing sdk naming which has been purged everywhere else in favour of cross-canadian. (From OE-Core rev: cbb63ca9e7e6d397198808e862f812f1012c74a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-*-runtime.inc: Fold configuration into gcc-runtime.incRichard Purdie2013-08-234-68/+67
| | | | | | (From OE-Core rev: 9cdfd55de8dbdea3d5e5ed25fbc67d1f198a069a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-*-cross.inc: Fold common configuration into gcc-cross.incRichard Purdie2013-08-233-82/+81
| | | | | | (From OE-Core rev: 8f6df85ca90c038316ca1ed22e9c54f937f21406) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: Combine gcc-target-configure.inc, gcc-target-package.inc and ↵Richard Purdie2013-08-234-16/+13
| | | | | | | | other common code (From OE-Core rev: 86bbe5b7b8e8f0c6ee88888fa083053ae14765c4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcc: Move common code to libgcc.incRichard Purdie2013-08-233-287/+145
| | | | | | (From OE-Core rev: 3b627b0a8e91a08a3e2a44c71d312ae303fb5d62) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Fold common configuration into gcc-configure-runtime.incRichard Purdie2013-08-233-8/+5
| | | | | | (From OE-Core rev: 17ba68f9ae09ae20eb11dfb03bcaa99428b74bf6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-initial: Fold common configuration into gcc-cross-initial.incRichard Purdie2013-08-233-2/+2
| | | | | | (From OE-Core rev: 7a9202d0478f0021b0ecd03b8d4af8d56c8e3265) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: Fold common configuration into gcc-cross.incRichard Purdie2013-08-233-22/+12
| | | | | | (From OE-Core rev: a77a8011e56f7cddf22adc63270aa9f44c86062a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-27 14:26:08 +0000