just noticed this:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-SERIAL_CONSOLE
while the "Note" rendering looks pretty (single leading and trailing
blank line, indented), the "Caution" rendering just below that is not
as pretty (double leading blank line, no trailing
before submitting as a patch, open for comments on anything i should
adjust first. a collection of typo fixes, grammar fixes,
clarifications (i hope), updates of examples to match current dora
tarball, and on and on and on.
based on fairly quick first pass and i made a list of things which
i'
wasn't sure what to do about some of these so i'd appreciate some
clarification. and away we go, mostly in alphabetical order ...
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE
that entry *really* implies you need the meta-yocto and
meta-yocto-b
On 02/11/2013 21:49, Ryan Kirkpatrick
wrote:
On Thu, 31 Oct 2013, Alex J Lennon wrote:
I see that Mono no longer seems to be building against Yocto head /
qemux86 (for me at least) and am considering looking at a recipe to
build the current r
Thanks Saul,
I'll dust off my vPro test hardware this week and get these rolled in.
Regards,
- Philip
On 11/01/2013 06:02 PM, Saul Wold wrote:
> This patch set updates to use the latest 3.10 kernel and adds the needed
> support, including switching form unionfs to aufs for the initramfs.
>
>
On Thu, Oct 31, 2013 at 3:48 PM, Markus Svilans wrote:
> With the help of a friend, have confirmed that 'core-image-minimal' cannot
> be built with Ubuntu 13.10 64-bit when MACHINE=genericx86-64. Attempted the
> build on a different machine in a different city, same results (failure to
> build).
>
On Sat, Nov 2, 2013 at 2:14 AM, Robert P. J. Day wrote:
> gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel = "1"
> gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-general = "1"
> gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-video = "1"
> gst-va-intel.bb:ALLOW_EMPTY_gst-va-intel-vaapi = "1"
>
> i'm *assuming* the abo
On Sat, Nov 2, 2013 at 3:27 AM, Robert P. J. Day wrote:
>
> (i can see it's going to be that kind of weekend.) ref manual reads:
>
> BB_DANGLINGAPPENDS_WARNONLY = "1"
>
> but some layers define:
>
> meta-linaro/meta-aarch64/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY = "true"
> meta-linaro/
WARNING: Variable key FILES_${PN}-dev (${includedir} ${FILES_SOLIBSDEV}
${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig
${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la
${base_libdir}/*.la) replaces original key FILES_mono-xsp-dev (
/usr/lib/pkgconfig/xsp.pc /
Remove redundant patches, use PV where possible and
remove hardcoding
Reorganise the patch directories
Fixes parse warnings like
WARNING: Unable to get checksum for mono SRC_URI entry Makefile.am.diff:
file could not be found
WARNING: Unable to get checksum for mono-native SRC_URI entry
Makefile
Hi Khem,
Per your suggestion, I installed gcc-multilib and was able to build
syslinux and core-image-minimal. Wonderful!
Thank you for having a look at this problem and finding the fix.
May I suggest that the Ubuntu/Debian section in Yocto Quick Start
documentation
(https://www.yoctoproject
The Fish River Island 2 documentation on the Yocto Project website has an error
(BSP version 9.0.0 "Dylan").
Specifically, the first section "Building the meta-fri2 BSP layer" describes a
step where you are to add a LICENSE_FLAGS_WHITELIST entry to your local.conf
when trying to enable the EMGD
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
On Sat, Nov 2, 2013 at 3:13 AM, Robert P. J. Day wrote:
> on my quest to spiff up the ref manual variables glossary, a question
> about ALTERNATIVE_LINK_NAME, explained here:
>
>
> http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-ALTERNATIVE_LINK_NAME
>
> at first glance, t
On 13-10-29 11:31 AM, Diego Sueiro wrote:
Bruce,
I've created new build setup with this configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.10"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE = "beagleb
On Sun, 3 Nov 2013, Chris Larson wrote:
>
> On Sat, Nov 2, 2013 at 3:13 AM, Robert P. J. Day
> wrote:
> on my quest to spiff up the ref manual variables glossary, a question
> about ALTERNATIVE_LINK_NAME, explained here:
>
>
> http://www.yoctoproject.org/docs/latest/ref-manua
Fixes include:
* typoes
* grammar fixes
* updated package and version references
* clarifications
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index f3211f8..81624ba 100644
--- a/documentation/ref
18 matches
Mail list logo
