From: Paul Barker
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 0f78225..b235772 100644
From: Paul Barker
U-boot configured with 'rpi_2_config' does not boot on a RaspberryPi 3.
Instead we need to configure with 'rpi_3_32b_config'.
Signed-off-by: Paul Barker
---
conf/machine/raspberrypi3.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/conf/machine
From: Paul Barker
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_4.9.bb | 5 +
recipes-kernel/linux/linux-raspberrypi_dev.bb | 5 +
2 files changed, 10 insertions(+)
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
b/recipes-kernel/linux/linux
From: Paul Barker
This is currently an RFC as I'd like some input from Khem and anyone else
interested in this before these patches get merged.
The hope is that by using AUTOREV we won't have to update the _dev recipe so
frequently in the future.
The third patch depends on a chan
From: Paul Barker
This makes the linux-raspberrypi_dev recipe more flexible by allowing
the kernel branch to be overridden in local.conf.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_dev.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes
From: Paul Barker
The development branches of linux-raspberrypi are rebased frequently. To
avoid fetch failures caused by out-of-date git hashes we need to use
AUTOREV.
LINUX_VERSION may need to be overridden in local.conf to match the
upstream version.
Signed-off-by: Paul Barker
---
recipes
From: Paul Barker
After this change, LINUX_VERSION should not need to be changed every time
upstream bumps the kernel version.
Signed-off-by: Paul Barker
---
recipes-kernel/linux/linux-raspberrypi_dev.bb | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/recipes-kernel
alsa-utils-amixer \
> +alsa-utils-aplay \
> +ltp \
> +"
This would work, but in this instance I think it would be better if we fixed
the packagegroup-core-tools-* recipes in OE-Core so that the items that
require X11 are only included when x11 is in DISTRO_FEATURES, rather
ge is insructing
> the developer to install a lot of software that OE will handle
> automatically, no?
Er, no. Well, if by "handle automatically" you mean "error out when they are
not present" then that's not very helpful - it's much easier if people just
get a l
On Wednesday 21 November 2012 23:01:22 Rifenbark, Scott M wrote:
> >-Original Message-
> >From: yocto-boun...@yoctoproject.org [mailto:yocto-
> >boun...@yoctoproject.org] On Behalf Of Paul Eggleton
> >Sent: Wednesday, November 21, 2012 2:51 PM
> >To:
On Wednesday 21 November 2012 20:19:05 Robert P. J. Day wrote:
> On Wed, 21 Nov 2012, Paul Eggleton wrote:
> > On Wednesday 21 November 2012 17:23:56 Robert P. J. Day wrote:
> > > as i read it, the sanity.bbclass and ASSUME_PROVIDED will
> > > dictate what needs to be
On Thursday 22 November 2012 06:54:33 Robert P. J. Day wrote:
> On Thu, 22 Nov 2012, Paul Eggleton wrote:
> > On Wednesday 21 November 2012 20:19:05 Robert P. J. Day wrote:
> > > On Wed, 21 Nov 2012, Paul Eggleton wrote:
> > > > On Wednesday 21 November 2012 1
nks, I've added the layer to the layerindex [1].
Cheers,
Paul
[1] http://www.openembedded.org/wiki/LayerIndex
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Friday 23 November 2012 09:31:39 Robert P. J. Day wrote:
> On Thu, 22 Nov 2012, Paul Eggleton wrote:
> > On Thursday 22 November 2012 06:54:33 Robert P. J. Day wrote:
> > > first, is ASSUME_PROVIDED technically completely superfluous?
> > >
> > > it
pen. Is there some simple mechanism I
> can use to force all native packages to build as 32-bit on a 64-bit system?
Sorry for the delay in replying. I've not had to do this myself but I suspect
something like this might do it:
BUILD_ARCH = "i686"
;
>
> but in meta-yocto, we do:
>
> BBPATH := "${LAYERDIR}:${BBPATH}"
>
> Unless someone explains to me that it's necessary to use this different
> ordering in meta-yocto's layer.conf, I will submit a patch to make this
> more consistent.
I think it
On Sunday 02 December 2012 15:35:54 you wrote:
> On 12/02/2012 03:24 PM, Paul Eggleton wrote:
> > On Sunday 02 December 2012 14:51:28 Scott Garman wrote:
> >> Robert Day has brought up an inconsistency in the way we append to
> >> BBPATH within a couple of our layer.con
On Monday 03 December 2012 03:16:10 Robert P. J. Day wrote:
> On Sun, 2 Dec 2012, Paul Eggleton wrote:
> > On Sunday 02 December 2012 15:35:54 you wrote:
> > > On 12/02/2012 03:24 PM, Paul Eggleton wrote:
> > > > On Sunday 02 December 2012 14:51:28 Scott Garman
.minix
> to ../bin/busybox
>
> *
>
> What am I missing here?
Sorry for the late reply - the "mkfs" command is provided by util-linux and is
in its own separate package, so I think you want
> Yocto project with Mindspeed hardware. This is going to speedup the release
> cicles and tools of our products.
Great to hear! Please let us know if you have any other feedback or issues.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
}${sysconfdir}/proftpd.conf
> sed -i '/ *Group[ \t]*/s/ftp/${FTPGROUP}/'
> ${D}${sysconfdir}/proftpd.conf
> install -d ${D}${sysconfdir}/init.d
Applied, thanks. I've also sent this over to be applied to meta-networking.
Cheers,
Paul
--
Paul Eggleton
Intel Ope
no clue
> that that was being expanded into multiple directories, one of which
> just *happened* to match the directory name they supplied. so things
> worked out, but not for the reason they thought.
By saying "just happened" you're implying that it is somehow accidental or
incidental that the directory that the user has specified is added - it is
nothing of the sort. It is completely deliberate and if it did not do so in
fact almost no recipe that used this construct would work.
We know this isn't a particularly self-evident structure; if it makes it
easier, consider it as just a single line of boilerplate when you want to add
or override any file in SRC_URI within a bbappend.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
re appropriately named link. A fix that has a
> lot more ripples would be to rename the directory to something like
> "ref-manual."
My suggestion would be to do both - rename it and then symlink from the old
name to the new one.
Cheers,
Paul
--
n to enable building from local
> repository.
>
> scripts/build.sh | 30 ++
> 1 files changed, 26 insertions(+), 4 deletions(-)
Can you please include Signed-off-by in your commit messages?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
didn't want to break existing machines that do have an RTC and don't
yet have "rtc" in MACHINE_FEATURES, we added it to MACHINE_FEATURES_BACKFILL.
In order to prevent it from being backfilled, you can add the following to your
machine config:
MACHINE_FEATURES_BACKFILL_CONSID
in meta/ -
I'm guessing you are using the 1.3 release version, in which case you can add
the following to your local.conf:
PREFERRED_VERSION_udev = "164"
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
this is the situation where the code hasn't been released
> yet, so there's no point in checking mirrors.
I guess the easiest thing would be just to set PREMIRRORS and MIRRORS to "" in
the recipe.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
_
ore pseudo gets built and only the ones that may require
configuration (e.g. network connectivity checks) are deferred.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
x27;s not unreasonable to want to avoid touching anything external when
building something internal; but you're right as a general practice this is
something we would not do in published recipes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
ING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$
Which version of the build system are you using?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
incompatible with the denzil release. I would suggest updating to the danny
release, or alternatively you'll need to modify meta-java to be compatible
with denzil (i.e. you'll have to match indenting in python functions such as
populate_packages_prepend).
Cheers,
Paul
--
Paul Egglet
On Thursday 20 December 2012 09:43:32 Raul Rosetto Munoz wrote:
> 2012/12/19 Paul Eggleton
> > On Wednesday 19 December 2012 15:31:42 Raul Rosetto Munoz wrote:
> > > raul@phi04:/home/prjs/poky$ git branch
> > > * local/origin/denzil
> >
> > There doesn
ually any
files in that directory you don't want or is it just the directory name that
concerns you?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
sure the package manager's database (RPM if you've selected RPM
packaging) is preserved, but won't set up any sample feeds. The latter would
need to be done manually or via ROOTFS_POSTPROCESS_COMMAND.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
cipes.
> >
> > That should be a do_install_append(), not install_append(). I'd also
> > double check the qtopia path, as I wrote that from memory, which may
> > not be reliable. ;)
>
> I tried the same but again ended up with error. As of now i am removing all
&g
|2 +-
> 4 files changed, 6 insertions(+), 5 deletions(-)
I've merged these, and created a danny branch which excludes the perl-module-
warnings-register patch.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
nt? If not could something be written up
and kept up-to-date?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ailing list for meta-raspberrypi specific discussions. Please
> don't forget to add "[meta-raspberrypi]" in subject.
>
> For more information check the included README in the layer.
FYI I've updated the OE layer index for the new location.
Cheers,
Paul
--
Paul
p because the core-image-minimal on the ADT download site is missing
> them too.
I can't tell but it could be this bug, for which I have sent a patch:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3792
(Although this doesn't prevent *all* dev packages from being included, just
s a regression would you mind
filing a bug for this in bugzilla if you haven't already?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
/poky-contrib/log/?h=paule/webmin-update
Kevin Strasser (1):
webmin: correct net-lib.pl patch
Paul Eggleton (3):
webmin: update to 1.620
webmin: tidy up recipe
webmin: fix for changes in OE-Core master
.../webmin/files/disable-version-check.patch | 25 +---
recipes-extended
Signed-off-by: Paul Eggleton
---
.../webmin/files/disable-version-check.patch | 25 +---
.../webmin/{webmin_1.590.bb => webmin_1.620.bb}|6 ++---
2 files changed, 18 insertions(+), 13 deletions(-)
rename recipes-extended/webmin/{webmin_1.590.bb => webmin_1.
* Move packaging definitions to the end
* Set SUMMARY instead of DESCRIPTION
* Remove EXCLUDE_FROM_SHLIBS and override of split_and_strip_files since
these are now taken care of by allarch.bbclass
* Reindent SRC_URI
Signed-off-by: Paul Eggleton
---
recipes-extended/webmin/webmin_1.620.bb
* Hide read-only-rootfs-hook.sh in init module
* Hide debugfs filesystems in mount module
* perl-module-file is no longer packaged, so remove references to it
Signed-off-by: Paul Eggleton
---
recipes-extended/webmin/webmin_1.620.bb |6 +++---
1 file changed, 3 insertions(+), 3 deletions
From: Kevin Strasser
remove absolute path from reference to debian-linux-lib.pl
Signed-off-by: Kevin Strasser
---
recipes-extended/webmin/files/net-lib.pl.patch |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/webmin/files/net-lib.pl.patch
b/recipes-exte
0)
> >
> > are available in the git repository at:
> > git://git.yoctoproject.org/poky-contrib paule/webmin-update
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/webmin-up
> > date>
> > Kevin Strasser (1):
> > webmin: correct net-li
gt;
> I think what you are trying to do is to modify the busybox configuration
> and then recompile and package. Bitbake will not automatically recompile
> after menuconfig. Menuconfig does not invslidate the shared state cache.
I think it possibly should though, since it does for
there some way to tell the built-in patch system to
> use a different -pnum value?
Yes there is - use the striplevel parameter e.g (from make_3.82.bb):
file://make-savannah-bug30612-handling_of_archives.patch;striplevel=0
Cheers,
Paul
--
Paul Eggleton
Intel
t;${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
>
> BBFILE_COLLECTIONS += "meta-baryon"
> -BBFILE_PATTERN_meta-baryon := "^${LAYERDIR}/"
> +BBFILE_PATTERN_meta-baryon = "^${LAYERDIR}/"
> BBFILE_PRIORITY_meta-baryon = "7"
Merged
Hi Kevin,
On Monday 18 March 2013 18:05:21 Kevin Strasser wrote:
> Cc: Paul Eggleton
>
> The following changes since commit 566cb211cee8a9870257a4ac2fc706990a70b9d2:
>
> nfs-utils: update bbappend version to 1.2.7 (2013-02-27 15:24:30 +)
>
> are available in
h) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 720 tasks of which 713 didn't need to be rerun and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>
> /home/testuser/myYocto/poky_danny/meta-ti/
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#enabling-your-layer
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
eploy them on the
target separately.
Cheers,
Paul
PS: please reply on-list so that everyone can follow the discussion. Thanks.
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ot;
> +BBPATH .= ":${LAYERDIR}"
>
> # We have a packages directory, add to BBFILES
> -BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb"
> +BBFILES += "${LAYERDIR}/recipes-*/*/*.bb"
>
> BBFILE_COLLECTIONS += "qt3"
> -BBFILE_PATTERN_
On Tuesday 19 March 2013 23:35:57 David Mulder wrote:
> > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> > Sent: Thursday, February 21, 2013 11:53 AM
> > I've now simply cherry-picked the two patches that came before this plus
> > my
> > patch fr
age. For information on how to do that,
see:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproj
On Thursday 21 March 2013 13:24:21 Kevin Strasser wrote:
> Hi Paul,
>
> The old configuration bits are now included with the new samba recipe and
> everything is again working out-of-the-box. Also, I've added a commit to
> the series that removes our workaround for the NFS reg
ikely that sharing DL_DIR directly between multiple users is not a
heavily tested scenario. One way around it which is fairly widely used
though is to set up a local mirror shared by all of the build machines
and keep DL_DIR separate on each machine. There is some information on
how to do that
ople have had a chance to give feedback I'll replace the content of the
existing OE wiki page with a link to the new index.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Friday 29 March 2013 18:58:09 Otavio Salvador wrote:
> On Fri, Mar 29, 2013 at 6:34 PM, Paul Eggleton
>
> wrote:
> > There is a new index for OpenEmbedded layers available here:
> > http://layers.openembedded.org
> >
> > It can be used to browse and searc
On Wednesday 27 March 2013 20:10:40 Paul D. DeRocco wrote:
> So is there a general way to peruse the collection of recipes? Does one have
> to do "ls -R *.bb" to get the list of recipes, then read the comments
> inside the files to see how to use them?
There are a few useful
n is, how would you like this to be used within the index?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Monday 01 April 2013 16:42:46 Paul D. DeRocco wrote:
> What I don't see is any info on the recipes, beyond name and version
> number.
> I don't see a list of packages they produce. For instance, doing "bitbake
> -e samba", and then looking at the PACKAGES vari
using your own separate distro config (perhaps
copying poky.conf instead of "require"ing it) and then the user can just set
it with "=" ?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Tuesday 02 April 2013 23:44:06 Khem Raj wrote:
> On Apr 2, 2013, at 11:41 PM, Paul Eggleton
wrote:
> > I'm not sure this is a path we should be going down; potentially we could
> > end up having to use ??= for just about everything.
>
> whats is downside of us
a new recipe (among other
methods it uses to determine recipe contents), however it could be adapted to
read a specified spec file I would think.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproje
e VERSION not PROVIDER, qt4-embedded not qt4_embedded, and = not ?= )
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ter-box2d doesn't signal that clutter itself is
unsupported, so I think maybe we shouldn't be removing these templates just
yet.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoc
On Wednesday 03 April 2013 08:42:23 Grigoropol, IoanaX wrote:
> Paul Eggleton wrote:
> > On Tuesday 12 March 2013 18:05:33 Ioana Grigoropol wrote:
> > > - support for clutter was removed from core-image-sato along with
> > > clutter-box2d and thus the project templat
nformation on how to customise the contents of images:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
OE-Classic; bringing it back into somewhere
like meta-oe would be much appreciated I think.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
b paule/docs3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/docs3
Paul Eggleton (5):
ref-manual: add buildhistory SDK contents collection
ref-manual: add info on buildhistory SRCREV value collection
ref-manual: add preamble to buildhistory section on top-level
contents
Update la
Buildhistory can now collect information on SDK contents, so add this to
the appropriate section.
Signed-off-by: Paul Eggleton
---
documentation/ref-manual/usingpoky.xml | 62
1 file changed, 62 insertions(+)
diff --git a/documentation/ref-manual
features to the appropriate section.
Signed-off-by: Paul Eggleton
---
documentation/ref-manual/usingpoky.xml | 52
1 file changed, 52 insertions(+)
diff --git a/documentation/ref-manual/usingpoky.xml
b/documentation/ref-manual/usingpoky.xml
index c8bee36..101411c
Add a paragraph to the top of the section on buildhistory mentioning the
metadata-revs file and the top-level directories.
Signed-off-by: Paul Eggleton
---
documentation/ref-manual/usingpoky.xml |8
1 file changed, 8 insertions(+)
diff --git a/documentation/ref-manual
have been for some time).
* Add collection name override to BBFILE_PRIORITY example
* Fix comments referring to old structure ("packages directory" or
"recipes directory")
Signed-off-by: Paul Eggleton
---
documentation/bsp-guide/bsp.xml| 10
Signed-off-by: Paul Eggleton
---
documentation/dev-manual/dev-manual-common-tasks.xml |3 +++
1 file changed, 3 insertions(+)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a697b8c..66df375 100644
--- a
SIZE}) +
> #
> Create rootfs partition to the end of disk
> + parted -s ${SDIMG} -- unit KiB mkpart primary ext2 $(expr
> ${BOOT_SPACE_ALIGNED} \+ ${IMAGE_ROOTFS_ALIGNMENT}) -1s parted ${SDIMG}
> print
>
> # Create a vfat image with boot files
Looks like this is a patch for meta-raspberrypi although it isn't marked as
such. Andrei, have you seen this?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
, but yes it does sound useful. I'll add it to
the todo list.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
add it to the image, details on
how to do that can be found here:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing li
On Friday 05 April 2013 09:05:34 Satya Swaroop Damarla wrote:
> Thank you Paul.. This was very helpful... From your reply. I understood
> that poky build doesnot support unicode characters set because the german
> special characters are not displayed ... Am I right?
There's no
p so far. If anything else comes to your mind, please
> tell me. I guess I will have to live with my Q&D patch for now ;)
One other possibility I can think of would be using a udev rule to run a
script when the actual hardware detection/insertion eve
PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> This .bbappend file works perfectly :-(
The FILESPATH line you referred to is very old and probably no longer
necessary. Try dropping it and see if everything works.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
be installed via
> > the 'eglibc-thread-db' package, but I can't find this package anywhere
> > on my system.
>
> It's not clear to me why, but the files labelled as 'eglibc-thread-db' in
> the eglibc recipe
t;No"
> Close and launch your terminal, now it will works !
We do not need to do this anymore as of the denzil release (1.2) - we
explicitly support /bin/sh not being bash, and in fact I am running with
/bin/sh -> dash on Ubuntu here right now.
Cheers,
Paul
--
Paul Eggleton
Intel O
On Wednesday 10 April 2013 17:36:06 Hans Beckérus wrote:
> Just for follow-up.
> The solution to this problem is to make sure CONFIG_LEGACY_PTYS=y in
> the kernel config.
Thanks, it's good to know you found the solution (as will others hopefully if
they come across your post.)
. (2013-04-11
08:43:26 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/docs6
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/docs6
Paul Eggleton (29):
ref-manual: add documentation for rm_work.bbclass
ref-manual: add more
On Sunday 14 April 2013 15:49:12 Paul D. DeRocco wrote:
> I've built core-image-base-cedartrail-nopvr, which includes ALSA. /dev/snd
> properly contains the devices for my mobo, and /proc/asound/devices lists
> them as well. If I plug in a USB MIDI device (a USB to MIDI converter), I
nal release occurs.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
the meta-oe
layer.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
dump the installed package list (rpm -qa?).
Or, use buildhistory:
https://wiki.yoctoproject.org/wiki/Buildhistory
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
"don't look here!" stuff elsewhere ;)
Also as I believe I mentioned before, FILESEXTRAPATHS adds not just one
directory but an "entire list of directories" is it allows bbappend file path
behaviour to match that of the recipe itself.
Cheers,
P
ke (i.e. provide it
with the BitBake source, which I hope we can look at within the next
development cycle).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
st be able to "git
grep" for the value in each of the layers you have enabled in order to find
where it is being set.
Are you sure you really need your own version of linux-libc-headers? Most of
the time it is not necessary for the version to match that of the k
On 19 April 2013 15:39, Robert P. J. Day wrote:
>
> i think i'll just leave this to the rpi folks. :-)
>
I'm building for raspberrypi so I'll add this to my queue of things to look at.
--
Paul Barker
Email: p...@paulbarker.me.uk
htt
defined and that's why you're
seeing that unexpanded value. Where did you get your net-snmp recipe from?
Which version of the build system are you using?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
__
7; as aliases for localhost,
which I don't see the purpose of myself.
So I'd recommend dropping these from meta-raspberrypi completely. Just
my opinion though, anyone else got any thoughts on this?
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
_
On 20 April 2013 21:35, Andrei Gherzan wrote:
> On Sat, Apr 20, 2013 at 4:05 PM, Paul Barker wrote:
>>
>> So I'd recommend dropping these from meta-raspberrypi completely. Just
>> my opinion though, anyone else got any thoughts on this?
>>
>
> Hello guy
Dropped raspberrypi modifications to hosts and interfaces files as they are
unnecessary.
Signed-off-by: Paul Barker
---
recipes-core/netbase/netbase-5.0/raspberrypi/hosts |2 --
recipes-core/netbase/netbase-5.0/raspberrypi/interfaces | 15 ---
recipes-core/netbase
ng TMPDIR on NFS, particularly
because of cases like this where NFS does not behave in the same way as a
standard filesystem. Aside from our own code, we'd have to take care of any
subtle issues in the build systems of every piece of upstream software being
built, and that's a bit too m
1 - 100 of 2360 matches
Mail list logo