| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
any other pieces of the dependency tree
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
setscene time
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
log warning
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
- 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>
|
| |
| |
| |
| |
| |
| | |
Also update some local files from upstream, and add nodolt.patch to fix build error.
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
|
| |
| |
| |
| |
| |
| | |
This avoid build error due to defination missing.
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
in creating them
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
it now (gcc-cross-intermediate)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
invalid comment
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
overhead for a simple task
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| | |
many times
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| | |
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Sometime user want a purely local fetching, i.e. using local mirror without
any remote netowrk access. BB_NO_NETWORK option is introduced for this purpose
check_network_access() is the guard for BB_NO_NETWOKR option. it should be
put in any place that fetcher use network access
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| | |
Fetch.try_mirrors is no longer exists, so the code is obsolate
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
the download is to fetch the source from URL, the build_mirror_data is
to create the mirror tar ball. the original go() method mix them together,
it is more clean to split them.
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| | |
fetch v2
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| | |
no functional change
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Yu Ke <ke.yu@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
there is case that we need to distingush bb.fetch and bb.fetch2,
and use different API for bb.fetch and bb.fetch2. so it is necessary
to add version info for distinguish purpose
Signed-off-by: Yu Ke <ke.yu@intel.com>
|