summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* bash: use /bin/bash as default shell when bash is includedKevin Tian2011-01-283-2/+7
| | | | | | | though bash is included in LSB profile, it doesn't use update-alternative to take effect and thus it's still busybox behaving as /bin/sh. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
* base-files: remove ending colon from default $PATH for root userKevin Tian2011-01-282-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | now the PATH for root user defined in a problematic way PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin: from eglibc: /* Two adjacent colons, or a colon at the beginning or the end of `PATH' means to search the current directory. */ that means current directory is always searched as the last path, which could generate undesired behavior. One example is found in LTP cron_deny01 test, which always complains "sh: cron_deny01 not found" cron_deny01 is a shell script which setups the initial test preparation and then invokes itself for real test under a different user: su $TEST_USER1 -c "$0" 'su' doesn't inherit PATH into the sub-shell, and thus $0 has to be an absolute path to have right script found. ltp appends the path of cron_deny01 to $PATH before running the test: export PATH="${PATH}:${LTPROOT}/testcases/bin" In ideal way "${LTPROOT}/testcases/bin/cron_deny01" is found and becomes $0, which works well. However due to the ending colon in original PATH: PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::${LTPROOT}/testcases/bin $0 becomes 'cron_deny01' w/o leading path which makes sub-shell under 'su' failed to locate cron_deny01. remove ending colon then fixes this problem. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
* matchbox: Convert all the matchbox components' repo from svn to git including:Zhai Edwin2011-01-2814-122/+55
| | | | | | | | | | | | | | | | | matchbox-wm matchbox-panel-2 matchbox-terminal matchbox-config-gtk matchbox-stroke matchbox-desktop matchbox-keyboard matchbox-themes-extra libfakekey settings-daemon Also remove some old recipes. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* distro tracking: Add info after upgrading gtk+, libuser and leafpadZhai Edwin2011-01-281-9/+9
| | | | Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* libuser: Upgrade from 0.56.18 to 0.57.1Zhai Edwin2011-01-282-2/+2
| | | | | | This can fix the vulnerable issue @ http://secunia.com/advisories/42891/ Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* leafpad: Upgrade from 0.8.17 to 0.8.18.1Zhai Edwin2011-01-281-2/+2
| | | | Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* scripts/bitbake: If pseudo isn't in staging for some reason, force a build ↵Richard Purdie2011-01-281-7/+17
| | | | | | of it directly Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: We only need pseudo-native in the sysroot, we can ignore ↵Richard Purdie2011-01-281-1/+1
| | | | | | any other pieces of the dependency tree Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Only clean out the sysroot if we rerun configure, not at ↵Richard Purdie2011-01-282-2/+6
| | | | | | setscene time Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure stale stamp files are removed as part of sstate_clean()Richard Purdie2011-01-281-2/+6
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/runqueue.py: Avoid starvation of events to the serverRichard Purdie2011-01-281-1/+1
| | | | | | | | | | | | | | The server UI was reading 1024 bytes, then sleeping for 0.25 seconds. Since most new LogRecord events are larger than this it leads to a build up of data which is only processed slowly, leading to a bottleneck and a slow down of all bitbake processes. Thanks to Dongxiao Xu <dongxiao.xu@intel.com> for the great work in debugging this. A large value has been left in for the read() command just to ensure some fairness amongst process handling if a task tries to log truly huge amounts of data to the server, or goes crazy and ensures the main loop doesn't stall. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Fix stupid typoRichard Purdie2011-01-271-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: No need to dump the contents of the sstate package to stdoutRichard Purdie2011-01-271-2/+2
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Handle whitespace in the list of files to 'fixup' to resolve ↵Richard Purdie2011-01-271-0/+2
| | | | | | log warning Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* BerkleyDB: Uprev db from 4.2 to 5.1.19Mark Hatle2011-01-275-168/+63
| | | | | | | The latest version of Berkley DB (5.1.19) is required by RPM. This version is backwards compatible with the 4.2 version that was enabled previously. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* ofono: Fix missing dependency on udevSaul Wold2011-01-271-1/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* iputils: upgrade to s20101006Yu Ke2011-01-272-25/+2
| | | | | | | - change the src_uri md5/sha256 checksum - remove the CVE patch, since it is already in upstream Signed-off-by: Yu Ke <ke.yu@intel.com>
* webkit-gtk: upgrade to 1.3.7Zhai Edwin2011-01-277-703/+183
| | | | | | Also update some local files from upstream, and add nodolt.patch to fix build error. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* eds-dbus: Do not disable old API after upgrading gtk+Zhai Edwin2011-01-272-0/+18
| | | | | | This avoid build error due to defination missing. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* gtk+: Update to 2.22.1Zhai Edwin2011-01-2713-143/+33
| | | | | | | | | Remove disable-gio-png-sniff-test.diff as it alreay in upstream. gdk-pixbuf in gtk+ is separated as another stand-alone package, so remove it. In future need only pick up stable version(even number like 2.20.x, 2.22.x). Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* sstate.bbclass: Optimise to check if the manifest exists without taking locksRichard Purdie2011-01-271-3/+3
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-python-tarball: include multiprocessing moduleJoshua Lock2011-01-271-0/+1
| | | | Signed-off-by: Joshua Lock <josh@linux.intel.com>
* perl: Remove ${MACHINE} dependency in compile and package.Dongxiao Xu2011-01-271-23/+19
| | | | | | | The judgement on ${MACHINE} is meaningless, remove it in order to avoid being rebuild on second machine. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
* bitbake/build.py: When looking up extra stamp info for setscene tasks, use ↵Richard Purdie2011-01-271-2/+6
| | | | | | | | the real taskname (Fixed based on a bug reported by Dongxiao Xu <dongxiao.xu@intel.com>) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rm_work.bbclass: Update to convert stamps to setscene stampsRichard Purdie2011-01-271-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to manipulate the stamps when removing WORKDIR to indicte that tasks like compile or install can't just rerun. The most effective method to do this is to convert the layout to match that which would have been the case had the system been build from sstate packages. For example, we'd task stamps like: xxx-1.4.7-r3.do_compile xxx-1.4.7-r3.do_configure xxx-1.4.7-r3.do_fetch xxx-1.4.7-r3.do_generate_toolchain_file xxx-1.4.7-r3.do_install xxx-1.4.7-r3.do_package.emenlow xxx-1.4.7-r3.do_package_write xxx-1.4.7-r3.do_package_write_ipk xxx-1.4.7-r3.do_package_write_rpm xxx-1.4.7-r3.do_patch xxx-1.4.7-r3.do_populate_sysroot.emenlow xxx-1.4.7-r3.do_setscene xxx-1.4.7-r3.do_unpack and after rm_work, we'd have stamps of: xxx-1.4.7-r3.do_package_setscene.emenlow xxx-1.4.7-r3.do_package_write_ipk_setscene xxx-1.4.7-r3.do_package_write_rpm_setscene xxx-1.4.7-r3.do_populate_sysroot_setscene.emenlow We also need to handle stamps in the form xxx-1.4.7-r3.do_package.MACHINE.TASKHASH as used by some signature generators. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: Drop unused autotools_stage_dir dummy functionRichard Purdie2011-01-271-4/+0
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools.bbclass: Only include aclocal directories if the exist, no point ↵Richard Purdie2011-01-271-3/+6
| | | | | | in creating them Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* send-pull-request: ensure a proper FROM header is includedDarren Hart2011-01-261-3/+26
| | | | | | | | | | | | | | | | | | | Commit 94629f2521711055b412f954af19e48b9bda6e50 removes the FROM header when sending via sendmail to avoid sending mail as the original change committer (as opposed to the local user). This resulted in mail going out without any FROM header, which some mailing lists correct by adding the *bounce address as the FROM. Correct this by reading FROM from the environment, from a new -f argument, or from the git user.name and user.email config settings, in that order of preference. Also display the FROM that will be used prior to the send confirmation. This has no effect if the -g (send via git) argument is specified, other than printing the git sendemail.from config setting. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Reported-by: Saul Wold <saul.wold@intel.com>
* meta-toolchain: Fix tar commandRichard Purdie2011-01-261-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/unlockfile: Fix exception handlingRichard Purdie2011-01-261-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* crosssdk: Drop PACKAGES setting as its set in cross.bbclass alreadyRichard Purdie2011-01-261-2/+0
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Correctly handle empty sstate packagesRichard Purdie2011-01-261-1/+6
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross.bbclass: Move sysroot_stage_all function to the only place that uses ↵Richard Purdie2011-01-262-13/+12
| | | | | | it now (gcc-cross-intermediate) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: No need to create these directories any more, also remove ↵Richard Purdie2011-01-261-9/+2
| | | | | | invalid comment Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-toolchain: Use --owner and --group options instead of using pseudo's ↵Richard Purdie2011-01-261-1/+1
| | | | | | overhead for a simple task Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: Remove MACHINE reference in do_configure, it causes perl to be rebuild ↵Richard Purdie2011-01-261-7/+5
| | | | | | many times Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: update to the new repositoryBruce Ashfield2011-01-251-3/+3
| | | | | | | | | | As the first of several changes to the kern-tools coupled to the branch management in the yocto kernels the repository is being renamed to it proper name. This change switches us to that newly created repo. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* documentation/yocto-project-qs/yocto-project-qs.xml: Added note to ↵Scott Rifenbark2011-01-251-2/+13
| | | | | | | | | | | poky-qemu command Depending on the architecture you are booting and the profile of the filesystem image QEMU might come up in a new shell, and existing shell, have a GUI, or be in command-line mode. I added a note indicating this behavior. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/yocto-project-qs/yocto-project-qs.xml: Updated <arch> value ↵Scott Rifenbark2011-01-251-23/+23
| | | | | | | | | for environment setup command The value for the 64-bit architecture was "x86-64" and not "x86_64". Changed it to be correct. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/yocto-project-qs/yocto-project-qs.xml: Updated list ↵Scott Rifenbark2011-01-251-2/+9
| | | | | | | | | | introducing pre-built section The section that introduces the using a pre-built binary section needed more items in the list. I added text for setting up the environment and for starting QEMU. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/yocto-project-qs/yocto-project-qs.xml: Added sub-sections to ↵Scott Rifenbark2011-01-251-15/+27
| | | | | | | | | | pre-built image section The pre-built image section was one long section that naturally broke into several areas. I inserted some sub-sections for better organization. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* documentation/yocto-project-qs/yocto-project-qs.xml: Corrected environment ↵Scott Rifenbark2011-01-251-2/+5
| | | | | | | | | | setup command I added the exact architecture strings for each of the five supported architectures as part of the /opt/poky/environment-setup.... commands resulting from installing the toolchain tarballs. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
* linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHOBruce Ashfield2011-01-251-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | Updating SRCREVs to reflect: perf: hard-code NO_LIBPERL/NO_LIBPYTHON ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently. This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL. It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet. This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* util-linux.inc: Fix DEPENDS on gettext for native caseRichard Purdie2011-01-252-1/+2
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_tracking: Update for poky-image-sdk renamingSaul Wold2011-01-251-12/+12
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* poky-image-sdk* renamed to poky-image-sato-sdk*Saul Wold2011-01-255-20/+20
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* meta-toolchain-sdk: Rename meta-toolchain-sdk to meta-toolchain-gmaeJessica Zhang2011-01-252-4/+4
| | | | | | | | Change the name from toolchain-sdk to toolchain-gmae, which is more accurate to what meta-toolchain-sdk generates Signed-off-by: Jessica Zhang <jessica.zhang@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* util-linux: tidy up metadataJoshua Lock2011-01-251-19/+19
| | | | | | | | | | Apply a couple of best practices to the recipe: 1) use the gettext class to ensure the right versions of gettext are used for the recipe variants (target, native, etc). 2) use layout variables rather than absolute paths in the package FILES_ definitions. Signed-off-by: Joshua Lock <josh@linux.intel.com>
* sanity/sstate: Due to the sysroot layout changes, the toolchain bootstrap ↵Richard Purdie2011-01-253-3/+3
| | | | | | process changes and the recent pseudo bug, bump the tmpdir layout version number and the sstate version numbers Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/fetch2: Instrument fetchers when making network accessYu Ke2011-01-259-1/+22
| | | | Signed-off-by: Yu Ke <ke.yu@intel.com>
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-03 20:58:58 +0000