| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
xorg-cf-files includes configuration files used by imake-based
recipes. Also add native support to the recipe.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
|
|
|
|
| |
The native recipe is needed by the transfig-native dependency chain.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
|
|
|
|
| |
The native recipe is needed by the transfig-native dependency chain.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
|
|
|
|
|
| |
This package includes configuration files needed for old x11
imake-based packages - transfig in particular.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The LIC_CHKSUM_FILES are specific to the source determined by SRC_URI. As such,
keep all the license information together with the SRC_URI. This also avoids
confusion from having these defined in both the .inc and the .bb files. The
CHKSUM got out of date in u-boot_git.bb, so update it while we're at it.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Ilya Yanok <yanok@emcraft.com>
CC: Gary Thomas <gary@mlbassoc.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The -Os option was disabled due to a bug in gcc building bad binaries for ARM
in an earlier commit:
f2dc7fadd8c6b180c3f985873261216d53f47f0d
This caused problems for powerpc which was resolved by replacing -Os with
-O2 for that architecture:
d0eb6794d964aa5ac938533a222c39bef09fd945
Using -O2 also works for ARM, so there is no need to condition using -O2 on
powerpc. Remove the condition and use -O2 on all architectures.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Ilya Yanok <yanok@emcraft.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
It is common enough to want to apply a defconfig if the inheriting
recipe provides it. If the file exists in the $WORKDIR, copy it
over to ${S}/.config provided the target does not already exist.
This allows for recipes derived from kernel.bbclass to manage the
.config on their own, such as linux.inc.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
| |
If a valid uImage exists, don't overwrite it with Image.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
|
| |
gcc on PowerPC is currently compiled with -Os optimization disabled so
we have to use -O2 on PowerPC instead.
Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
| |
Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
| |
Linux is licensed under GPL so add appropriate LIC_FILES_CHKSUM to
linux.inc file.
Signed-off-by: Ilya Yanok <yanok@emcraft.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes [BUGID #610]
dtb files were not being built for the mpc8315e-rdb, since they
weren't being configured into the machine. With this and the
related dtc fixes, we now get a dtb in the deployment directories.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new license processing rules error if dtc-native itself
doesn't have license information. Previously only the .inc
files contained this information, so we make a copy and leave
the existing license info to be removed pending further review.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes [BUGID #610]
The powerpc linux-yocto kernels were not creating dtb images
in the deploy directories. This was due to two problems:
- the dtb generation rules were not being configured
- the boards were not specifying a device tree in their config
This change addresses the first point by factoring out the
dtb generation routines into a new include that can be used by
multiple recipes.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In order to build BSPs that were not already integrated into
the upstream linux yocto kernel AND keep the git fetcher happy,
some fairly complex anonymous python sections were required.
These sections cause problems with variable expansion and SRCREV
processing.
With the updated git fetcher code, we can streamline the BSP
boostrapping process and drop 99% of the anonymous python code.
This commit has the following changes to support BSP boot strapping
and simplication for existing BSPs.
- KMETA is set per-recipe rather than in python code
- undefined machines are no longer used, but instead common
branch names are set per-recipe
- fallback machine SRCREVs are present in the default revisions
file
- A new variable YOCTO_KERNEL_EXTERNAL_BRANCH should be set in
the local.conf for new BSPs instead of being programatically
determined in the anonymous python.
- No more explicity KMACHINE variable expansion and manipulation,
since the tools and build phases no longer require it due
to the per-recipe fallbacks.
Integrated/merged BSPs are unaffected by the changes and have been
regression tested.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
foo
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In order to build BSPs that were not already integrated into
the upstream linux yocto kernel AND keep the git fetcher happy,
some fairly complex anonymous python sections were required.
These sections cause problems with variable expansion and SRCREV
processing.
With the updated git fetcher code, we can streamline the BSP
boostrapping process and drop 99% of the anonymous python code.
This commit has the following changes to support BSP boot strapping
and simplication for existing BSPs.
- KMETA is set per-recipe rather than in python code
- undefined machines are no longer used, but instead common
branch names are set per-recipe
- fallback machine SRCREVs are present in the default revisions
file
- A new variable YOCTO_KERNEL_EXTERNAL_BRANCH should be set in
the local.conf for new BSPs instead of being programatically
determined in the anonymous python.
- No more explicity KMACHINE variable expansion and manipulation,
since the tools and build phases no longer require it due
to the per-recipe fallbacks.
Integrated/merged BSPs are unaffected by the changes and have been
regression tested.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
foo
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The error this works around is:
cc1: warnings being treated as errors
gas/config/tc-arm.c: In function 'parse_operands':
gas/config/tc-arm.c:1876:27: error: 'firsttype$defined' may be used uninitialized in this function
gas/config/tc-arm.c:1876:27: error: 'firsttype$index' may be used uninitialized in this function
Ideally it should get fixed properly, but let's mimic binutils-cross for now
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It was using a '/' in a name variable, subtly breaking things like this:
populate_sdk.bbclass:
mkdir -p ${SDK_DEPLOY}
cd ${SDK_OUTPUT}
tar --owner=root --group=root -cj --file=${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.bz2 .
Tar will error out since SDK_DEPLOY/DISTRO/ doesn't exist. Change the default to be more like the one from poky.conf, without the poky specific POKYLIBC.
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Enable the fetcher to be able to unpack and SRPM. By default the system will
unpack the contents of the SRPM into the WORKDIR.
A new syntax "unpack=file" was developed for the SRC_URI, to allow for a
recipe to extract a specific file within an SRPM. An unpack operation will
then be executed on the extracted file.
In order to apply extracted patches (or unpack files not specified with
unpack), you must specify the path using WORKDIR, i.e.:
file://${WORKDIR}/mypatch.patch
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[BUG #702]
The previous error message was confusing. It was looking for both library and
include host contamination, but the message only indicated include files.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| | |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The python code in this class file needs to run before SRCPV is expanded
and calls into the fetcher are made. To so this we create a python function
and prepend a call to it before SRCPV's get_srcrev() call.
Ugly, ugly, ugly but the ordering is guaranteed.
If this doesn't happen, the fetcher can end up in two different states and
there may be caching implications of this.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
kernels
If we don't do this and try to bring up a new machine we can trigger network
access to resolve the branch name to a revision which is undesireable.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes [BUGID #693]
The init-live.sh script starts udevd in init-live.sh:early_setup(),
but doesn't account for the possibility that the root device may have
already been registered by the kernel before udevd starts up.
If the device is detected after udevd starts up, everything's fine -
udevd gets the 'add' uevent for the device, the root image shows up at
e.g. /media/sda/rootfs.img, and the boot continues.
If however the device is detected before udevd starts up, udevd misses
the 'add' uevent and the root image never shows up, causing it to stay
in the 'waiting for removable media' loop forever.
The 'udevadm trigger' command is meant to be used to avoid this
situation, but init-live.sh doesn't use it. Furthermore, since the
default was changed in udev 152 from 'add' to 'change', the command
needs to explicity name 'add' as the action.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the rpm recipe after the recent changes to the fetcher API. Koen wrote
the original patch, Richard cleaned it up and fixed it.
This code needs to be merged into the fetcher instead at some point soon.
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
| |
| |
| |
| | |
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
commits: 7697c24..2e05e11
upstream: git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git
Update to lttng-0.242 for 2.6.37. Built and boot tested on all
architectures.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All the libraries needs to be specified explicitely with the new gcc dso
linking change patch. This was causing build errors for this
recipe. Specifying the libpthread library explicitely for linking to work
without errors.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add the mount lock patch that moves the lock file from the potentially R/O
/etc, to the R/W /var/lock directory.
This resolves a problem when mounting when / (and /etc) is mounted R/O.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| |
| |
| |
| | |
Merge a small bug fix located in the Fedora Core 9 version of this
package.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a number of bug fixes, mostly imported from Fedora and Wind River
Linux.
cp-i-u: fix unnecessary prompting
fix-install: Fix installing to a dangling symlink
i18n: li18nux/lsb compliance
ls-x: Fix incorrect output
overflow: Fix potential overflow in who command
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the kernel is started using ip=dhcp, we want a way to be able to run
the udhcp client within busybox and not reset the interface.
When using the '-D' option to udhcpc, the defconfig script will be skipped
allowing the refresh without changing the network settings.
Also provide an initscript that can be used to detect ip=dhcp on the
kernel command line, if detected it will refresh the lease and set the
proper resolve.conf and related files, but not reset the interface.
Original code in Wind River Linux by Greg Moffatt <greg.moffat@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Uprev pseudo to the latest version. This corrects a linking problem on
some newer host systems.
In addition, we add more detail to the local.conf.sample file to explain
the NO32LIBS and why someone would set it to 0.
Also fix a minor bug in pseudo that prevented it from building for the
target.
Signed-off-by: Mark Hatle <mark.hatle@windriver.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>
|
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This issue is really do to the timestamps of files being different
enough and that the make of the doc directory is being triggered by
this.
This is partly due to the new git fetcher laying the files down
differently. Once this issue is resolve, this can be reverted.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 62337be30b904542ca46333aa9b58fe0f09d3561.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 8b5e600141b2b4275551bea925a2e63cfe1297bd.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 3eef8470547beed186c38a7da44cb8e22e1497e8.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|