summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* bitbake.conf/classes/gcc: Don't hardcode -nativesdkRichard Purdie2013-08-237-21/+22
| | | | | | | | | | | | | Hardcoding -nativesdk as the sdk package architecture is inflexible. We may have multiple different target OS and we need a way to be able to separate them. Turning this into a configurable value allows the flexibility we need to build different SDKMACHINEs with different OS targets. The commit should have no behaviour change, just makes things more configurable. (From OE-Core rev: a2110e86b98d646e136de9ec6b8e668079b0d4f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "nativesdk: inherit relocatable"Richard Purdie2013-08-231-2/+0
| | | | | | | | | | | | This reverts commit f93ddea31fcf18833c9bc6e93d93ad223c62eded. We never run nativesdk binaries so it doesn't make sense to use the relocatable class. The chrpath calls at packaging time will ensure the binaries are relocated in the final packages. The binaries in the sysroot are never used. (From OE-Core rev: 9f19d1b90c4fa04439b6267bda0484fd0b350373) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Merge 4.7 and 4.8 recipes into common includeRichard Purdie2013-08-233-43/+19
| | | | | | | | This removes duplication and follows the pattern of the other gcc recipes. (From OE-Core rev: 3296c896f5a5ef7dd50ab4e00ddbf1c2476462dc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian-4.8: Add missing dependency on nativesdk-zlibRichard Purdie2013-08-231-1/+1
| | | | | | (From OE-Core rev: c782bd4de511b6e603a72a00124a77be52e50dce) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian-4.8: Allow elfutils to be a configurable dependencyRichard Purdie2013-08-231-2/+3
| | | | | | | | | Some SDK platforms have elfutils support, some do not, therefore allow this to be configured. (From OE-Core rev: 717e940d2c2beccfda31dda16a2d0d6d9a495042) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop gcc-cross4.inc, its pointless nowRichard Purdie2013-08-234-5/+4
| | | | | | | | | | | The include was useful historically, its not anymore so lets remove it. This should have no functional change except on any layers directly depending on it or gcc-cross.inc but even then it would only impact sh4 and is easily fixed if there was a problem. (From OE-Core rev: e7e8fe11c34bf05179f3bbaa2fb1af7b7125696a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-configure-sdk.inc: Don't build target-libgccRichard Purdie2013-08-231-1/+1
| | | | | | | | | | | | I don't understand why we're building the target libgcc in the canadian-cross build since it should have been built elsewhere. The compiler configuration isn't correct to build a working target libgcc in all cases anyway. To avoid various weird build errors, stop building it. (From OE-Core rev: b0d1ab6242b6ce2bcdd0e4e3e61600344fcd2907) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-sdk.inc: Allow executable extension to be overriddenRichard Purdie2013-08-231-2/+5
| | | | | | | | | | | | | On platforms like windows, executables have extensions. Whilst I'm not proposing we wholesale support windows extensions, this small tweak allows a cross compiler targetting mingw to be built which does seem like a good use case. The patch therefore adds an EXEEXT which the mingw layer can set for the libexec symlinks. (From OE-Core rev: 8dcf0d95b654fa6cc56193168aaa744052ad8ffc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-package-sdk.inc: Use relative symlinks in libexec dirRichard Purdie2013-08-231-1/+4
| | | | | | | | | | We already use relative links for other gcc libexec links, this changes the sdk do_install to match elsewhere and use relative symlinks too. This makes things slightly easier in the SDK installation process and standardises. (From OE-Core rev: ecfa1141e731224cc5a099f8dfd22878f23359ec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian-4.8: Enable PARALLEL_MAKERichard Purdie2013-08-231-2/+0
| | | | | | | | | | | | | This disabling of PARALLEL_MAKE has been forward ported for gcc-cross-canadian since at least 2009-09 and gcc 4.3.3, probably older. I've tested this with high values of parallel make and it all seems to work and we usually build gcc with parallel make so it seems unlikely there are issues. Lets therefore enable it. (From OE-Core rev: cee90d230899eb1255d586e6ee4fad0d94348cfd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libiconv: Extend to nativesdk and support non-linux targetsRichard Purdie2013-08-231-0/+4
| | | | | | | | | | | | | This library is currently only available when targeting non-libc. This patch also makes it available when targetting non-linux since it is likely of use then. It also adds a BBCLASSEXTEND for nativesdk since again, it can be useful in that context. (From OE-Core rev: af8c5adc71dc9bab57504d5a9dbf9e863fd4bf7b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianRichard Purdie2013-08-237-5/+14
| | | | | | | | | | | | | | | | The gettext handling of USE_NLS has become a bit tricky to understand, or alter from the SDK context. This patch introduces a SDKUSE_NLS which can be set to configure a given SDK/ADT to use NLS or not. This is independent of the target system NLS usage. The code in gettext.bbclass is therefore simplified and the classes themselves now set USE_NLS to appropriate values. No NLS is used for native, cross and crosssdk since it is never used there and would just increase build time. (From OE-Core rev: fe634d47449899f7424adb77ff5bc7ddf8a07a47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base: Allow sdk tar options to be overriddenRichard Purdie2013-08-231-1/+3
| | | | | | | | | It can be useful to override or append options to the SDK tarball creation command so add a variable to allow this. (From OE-Core rev: ae86a46c1b255e7c2833eb6d48ed46eba440e95a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* crosssdk: Construct target_exec_prefix from prefix_nativesdkRichard Purdie2013-08-231-1/+1
| | | | | | | | | ${exec_prefix_nativesdk} doesn't exist so use prefix_nativesdk instead. This resolves issues for code which attepts to use target_exec_prefix. (From OE-Core rev: cd1ac8257ed2701cbe3802870183e8e1cd3b0418) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Fix handling of symlinks in debug packagesRichard Purdie2013-08-231-0/+6
| | | | | | | | | | | | | | | | | | When copying the sources for the debug source package we use cpio -Ll which means to copy files as hardlinks and to dereference symlinks. It appears there is a bug in cpio since -Ll will copy symlinks and not dereference them. We therefore do a second pass over copied symlinks resolving them into files. Ideally we would copy these as hardlinks as well however it doesn't seem worth the extra code and effort for what amounts to a corner case for a minor space improvement. This means that the -dbg packages no longer contain broken symlinks. [YOCTO #5020] (From OE-Core rev: 2ca2c4747f645a0d478c2171fff4c65752188285) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkfontscale: This no longer needs a full libx11, xproto sufficesRichard Purdie2013-08-221-1/+1
| | | | | | | | | | configure just looks for xproto so we can drop the libx11 dependency and reduce the amount we build for some small performance improvements and less of the -native stack. (From OE-Core rev: e473e60d5572f36829068f6d3db9ce9ba9633d71) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg: Update to 2.0.21Saul Wold2013-08-221-2/+2
| | | | | | | (From OE-Core rev: d7481ee36f6bd0416eb35d8c40cb3ed9f2395a2f) 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-07-04 22:26:33 +0000