[yocto] Creating an system installer/updater image

[J.T. Conklin]

I've created an image recipe that builds an image that runs under qemu
or from a "live" CD on a generic x86-64 server.

I'd like to create an installer/updater CD/USB stick that partitions,
formats, and installs the kernel and the set of packages from the above
image onto the server's hard disk.

The core-image-minimal-initramfs.bb recipe builds an image which
contains partitioning and formatting tools and install scripts.  The
install script partitions and formats the hard disk, then mounts the
/media filesystem (I assume this would be the same CD containing the
initramfs / install kernel), copies a different kernel and unpacks a
root filesystem image to the system's hard disk.

Aside from using a kernel image and root filesystem instead of a
kernel image and discrete packages, this looks to be pretty much
what I want to do.

However, it's not immediately clear to me how to connect the dots
between the build artifacts built for the production image and creating
CD install media containing the initramfs image and those artifacts.

Is there a example of this (taking artifacts from one build and using
them in another)? Or am I barking up the wrong tree?

   --jtc

-- 
J.T. Conklin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] how to use the new features of the toaster

[leimao...@cn.fujitsu.com]

Hi,
 
 Because I noticed that in poky(master), the toaster has the ability to trigger 
a build command, and have
 the build executed.
 --
 commit 6e71c276b582135228419d95174b7e7784d496b2
 Author: Alexandru DAMIAN 
 Date:   Mon Jun 30 18:33:04 2014 +0100

bitbake: toaster: add project main edit page

This is the first commit on the project main edit page.

At this point we have:
* the default settings for a newly created project
* the ability to add targets
* the ability to trigger a build command, and have
the build executed
..
 ---
 
 So, I tried to use the new features of the toaster. But I don't know how .
 
 Is there anybody tell me where can I find the documentation how to use the new 
features?
 
 Best Regards,
 Lei Maohui
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] pinentry: Fix QA error

[Armin Kuster]

This fixes: WARNING: QA Issue: pinentry rdepends on libcap, but it isn't a 
build dependency? [build-deps]

Also add pkgconfig support.

Signed-off-by: Armin Kuster 
---
 recipes-security/pinentry/pinentry_0.8.3.bb | 13 +
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/recipes-security/pinentry/pinentry_0.8.3.bb 
b/recipes-security/pinentry/pinentry_0.8.3.bb
index 3209e53..0bd3021 100644
--- a/recipes-security/pinentry/pinentry_0.8.3.bb
+++ b/recipes-security/pinentry/pinentry_0.8.3.bb
@@ -2,14 +2,19 @@ DESCRIPTION = "This is a collection of simple PIN or 
passphrase entry dialogs wh
 HOMEPAGE = "ftp://ftp.gnupg.org/gcrypt/";
 LICENSE = "GPL-2.0"
 LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-DEPENDS = "glib-2.0 ncurses"
+DEPENDS = "glib-2.0 "
 
 SRC_URI = "ftp://ftp.gnupg.org/gcrypt/pinentry/${PN}-${PV}.tar.bz2";
 
 SRC_URI[md5sum] = "2ae681cbca0d9fb774b2c90b11ebf56c"
 SRC_URI[sha256sum] = 
"568b0b09b50b2388a4f94d704d5bcb28718ecd4654ed1acc43ab1f97d921a0ad"
 
-inherit autotools
+inherit autotools pkgconfig
 
-EXTRA_OECONF +="--disable-pinentry-gtk2 --disable-pinentry-qt 
--disable-pinentry-qt4 --without-x --enable-ncurses \
---with-ncurses-include-dir=${STAGING_INCDIR} "
+EXTRA_OECONF +="--disable-pinentry-gtk2 --disable-pinentry-qt \
+--disable-pinentry-qt4 --without-x "
+
+PACKAGECONFIG ??= "ncurses"
+
+PACKAGECONFIG[ncurses] = "--enable-ncurses  
--with-ncurses-include-dir=${STAGING_INCDIR}, '--disable-ncurses', ncurses"
+PACKAGECONFIG[libcap] = "--with-libcap, --without-libcap, libcap"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [vmdk] vmdk image not booting

[Bruno Dal Bó Silva]

Hello,

I attempted the following configuration, with no luck:
-daisy branch
-core-image-minimal
-machine=genericx86
-IMAGE_FSTYPES += "vmdk"

Then I tried booting the vmdk in vmware and virtualbox players. But the
boot process stops just before hitting sysvinit, although the "live" image
works just fine. Am I missing something?

Thanks
Bruno
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [vmdk] vmdk image not booting

[Bruno Dal Bó Silva]

Hello,

I attempted the following configuration, with no luck:
-daisy branch
-core-image-minimal
-machine=genericx86
-IMAGE_FSTYPES += "vmdk"

Then I tried booting the vmdk in vmware and virtualbox players. But the
boot process stops just before hitting sysvinit, although the "live" image
works just fine. Am I missing something?

Thanks


Bruno Dal Bó Silva
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [ANNOUNCEMENT] Yocto Project 1.7 Milestone 2 now available

[Flanagan, Elizabeth]

The second milestone for our upcoming 1.7 release is now available at:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.7_M2/


bitbake 4aaf56bfbad4aa626be8a2f7a5f70834c3311dd3
eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
oecore 7986adeac16550b33f65fded39a55f668e0e543f
poky 2d1660112e54653f7bb763939d0416472c49fe01


-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Python3: Unable to get the locale encoding (Yocto/daisy)

[Mikhail Zakharov]

Hi all,

We are using yocto daisy 1.6.1  and added 'python3' to our local.conf
when building 'core-image-minimal' , however we get the following error
when invoking the interpreter in  on target:

Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'

Could someone please share a possible cause/solution to this?

Thanks and regards,
Mikhail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fix for meta-oe/recipes-graphics/fbida/fbida_git.bb

[Jens Rehsack]

Hi Paul,

Am 18.08.2014 um 16:48 schrieb Paul Eggleton :

> Hi Jens,
> 
> On Sunday 17 August 2014 20:06:10 Jens Rehsack wrote:
>> Am 17.08.2014 um 19:39 schrieb Martin Jansa :
>>> On Sun, Aug 17, 2014 at 05:02:39PM +0200, Jens Rehsack wrote:
 we played a bit with some tools before using a modified psplash to show
 some guidance on hdmi-fb and there was an error in fbida which wrongly
 mixes host-paths and target paths. Additionally - for Poky or OE it's
 unnecessary to guess additional path to check - recipes will do
 correctly.
>>> 
>>> Please follow README and send it as inline patch to oe-devel ML.
>>> 
>>> Thanks
>> 
>> Hi Martin,
>> 
>> 1) I do not send inline-patches
>> 2) I do not subscribe to more mailing lists just to send patches.
>> 
>> Either it's helpful and maintainers accept it or it's not and when one uses
>> a search engine one applies it locally.
> 
> You do want to avoid carrying these patches yourself indefinitely, right?
> If so, you'd rather they got merged rather than being missed by the 
> maintainer 
> because they weren't in the expected place or format - right?
> 
> The way we accept and review patches is via our mailing lists; and we have to 
> have more than one list because of the sheer volume of patches and 
> discussion. 
> Unfortunately we also have to force subscription in order to protect 
> ourselves 
> from spam. However, it's worth noting that you don't actually need to receive 
> emails from the list in order to be subscribed - you can disable delivery in 
> your account options.
> 
> The procedures we have in place do require just a little bit more work on the 
> part of the submitter, but that does translate to a huge reduction in work 
> for 
> the maintainers; and preserving our maintainers' sanity is important if we 
> want to keep the system maintained ;)

It's a bit more difficult ;)

I took the patch from customers place to submit it in my spare time, because
mail setup at customers place is terrible. OTOH - dealing with "git send-mail"
is everything else than easy to setup and use. Since I'm a contractor for a
limited time in a project which lacks time for dealing such extra-effort, I
could only clone the repository and submit the stuff (without having any
chance to re-test in case of errors) after end of project.

You might check the list of open issues in the projects maintained or co-
maintained by me (some basic perl modules as Hash::Merge, List::MoreUtils,
MooX::Cmd, ... and libstatgrab and Packager::Utils needs some polishing to
get out before 2014Q3 of pkgsrc is branched) - with 50+ hours per week working
in the project and ~10h+ commuting and spending time with family and friends
and hacking on my projects - I do not see any time to setup a reasonable
environment for "git send-email".

So I accept patches in any way - I only care about unified diff and in case of
code changes, some unit tests.

Best regards
-- 
Jens Rehsack
pkgsrc, Perl5
s...@netbsd.org





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Khem Raj]

On Mon, Aug 18, 2014 at 12:08 PM, Paul Barker  wrote:
>> That would be handy too. But I wanted was to keep this info in project
>> for folks to try it out.
>>
>
> I'll just post one ticket for now.
>

Thats fine too.

> I think I've got a fix for e2fsprogs as well.

Great. when we write patches that arise out of musl systems we should
make sure that

1. If patch fixes a genuine issue surfaced with musl, fight it out ar
respective package upstream and in OE universe add it to the original
layer where recipe primarily resides
but we can keep the patches in meta-musl as a last resort.

2. If its something musl specific then lets keep it in meta-musl and
see how musl can be changed to fix it.

Thanks
-Khem
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Paul Barker]

On Mon, Aug 18, 2014 at 12:04:54PM -0700, Khem Raj wrote:
> On Mon, Aug 18, 2014 at 11:50 AM, Paul Barker  wrote:
> > On Mon, Aug 18, 2014 at 11:26:26AM -0700, Khem Raj wrote:
> >>
> >> Thanks cool. Can you open a ticket on github with this information ?
> >
> > Will do. Do you want just want one ticket or do you want to separate these 
> > into
> > one ticket per failing recipe or similar?
> >
> 
> That would be handy too. But I wanted was to keep this info in project
> for folks to try it out.
> 

I'll just post one ticket for now.

I think I've got a fix for e2fsprogs as well.

Cheers,

-- 
Paul Barker

Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk


pgp2atZngHaGK.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Khem Raj]

On Mon, Aug 18, 2014 at 11:50 AM, Paul Barker  wrote:
> On Mon, Aug 18, 2014 at 11:26:26AM -0700, Khem Raj wrote:
>> On Mon, Aug 18, 2014 at 11:14 AM, Paul Barker  wrote:
>> > On Sat, Aug 16, 2014 at 05:50:38PM -0700, Khem Raj wrote:
>> >> Hello All
>> >>
>> >> musl  is a newer implementation licensed
>> >> under MIT licence
>> >> A layer to support musl to supply your system C library as an
>> >> alternative to uclibc and eglibc/glibc  is now available at
>> >>
>> >> https://github.com/kraj/meta-musl
>> >>
>> >> README describes way to get going with it.
>> >>
>> >> Few things to note
>> >>
>> >> * Supports gcc 4.9 in OE not 4.8
>> >> * Current musl recipe is 1.1.4 based
>> >> * You need latest master of OE-Core
>> >> (106305227003761c3fc562c21bb859a5256f2b36) or  newer and
>> >> bitbake
>> >> * Its only able to build core-image-minimal
>> >> * core-image-minimal boots on qemuarm, qemuppc, qemumips, qemux86, 
>> >> qemux86-64
>> >>
>> >> I will send a request to add it to layerindex soon and then you should
>> >> be able to find it using
>> >> layerindex.opernembedded.org as well
>> >>
>> >> If you try it out on your hardware and/or have feedback I am
>> >> interested. Fork it from github, file bugs
>> >> send patches 
>> >>
>> >> Happy hacking
>> >>
>> >
>> > core-image-minimal works with my configuration on qemuarm. It also 
>> > successfully
>> > builds what will soon be released as opkg-0.2.3 and the recipe for 
>> > toybox-0.4.9
>> > which I've recently created.
>> >
>> > I tried building core-image-full-cmdline as I think that would be good 
>> > next step
>> > from core-image-minimal. I'm seeing failures in:
>> >
>> >   meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb, do_compile
>> >   meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb, do_compile
>> >   meta/recipes-extended/libtirpc/libtirpc_0.2.4.bb, do_compile
>> >   meta/recipes-extended/iptables/iptables_1.4.21.bb, do_compile
>> >   meta/recipes-connectivity/nfs-utils/libnfsidmap_0.25.bb, do_compile
>> >   meta/recipes-devtools/perl/perl_5.20.0.bb, do_compile
>> >   meta/recipes-extended/sysklogd/sysklogd_1.5.bb, do_compile
>> >   meta/recipes-extended/ethtool/ethtool_3.14.bb, do_compile
>> >   meta/recipes-extended/psmisc/psmisc_22.21.bb, do_compile
>> >   meta/recipes-extended/pax/pax_3.4.bb, do_compile
>> >   meta/recipes-extended/procps/procps_3.2.8.bb, do_compile
>> >   meta/recipes-extended/net-tools/net-tools_1.60-25.bb, do_compile
>> >   meta/recipes-extended/findutils/findutils_4.4.2.bb, do_compile
>> >   meta/recipes-extended/logrotate/logrotate_3.8.7.bb, do_compile
>> >   meta/recipes-extended/cronie/cronie_1.4.11.bb, do_compile
>> >   meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile
>> >   meta/recipes-extended/at/at_3.1.14.bb, do_compile
>> >   meta/recipes-extended/iputils/iputils_s20121221.bb, do_compile
>> >   meta/recipes-extended/gzip/gzip_1.6.bb, do_compile
>> >   meta/recipes-extended/sudo/sudo_1.8.10p3.bb, do_compile
>> >   meta/recipes-extended/mc/mc_4.8.12.bb, do_compile
>> >
>> > I can share detailed logs if anyone wants them. I'll have a look and see 
>> > if I
>> > can find some low hanging fruit amongst these which are easy to fix.
>> >
>>
>>
>> Thanks cool. Can you open a ticket on github with this information ?
>
> Will do. Do you want just want one ticket or do you want to separate these 
> into
> one ticket per failing recipe or similar?
>

That would be handy too. But I wanted was to keep this info in project
for folks to try it out.

> I've put the failing "log.do_compile" files into one directory which is 1.3MB
> uncompressed or just 41kB compressed. I've posted them to:
>   http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/
>   
> http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/musl-error-logs_2014-08-18.tar.xz
>
> Cheers,
>
> --
> Paul Barker
>
> Email: p...@paulbarker.me.uk
> http://www.paulbarker.me.uk
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Paul Barker]

On Mon, Aug 18, 2014 at 11:26:26AM -0700, Khem Raj wrote:
> On Mon, Aug 18, 2014 at 11:14 AM, Paul Barker  wrote:
> > On Sat, Aug 16, 2014 at 05:50:38PM -0700, Khem Raj wrote:
> >> Hello All
> >>
> >> musl  is a newer implementation licensed
> >> under MIT licence
> >> A layer to support musl to supply your system C library as an
> >> alternative to uclibc and eglibc/glibc  is now available at
> >>
> >> https://github.com/kraj/meta-musl
> >>
> >> README describes way to get going with it.
> >>
> >> Few things to note
> >>
> >> * Supports gcc 4.9 in OE not 4.8
> >> * Current musl recipe is 1.1.4 based
> >> * You need latest master of OE-Core
> >> (106305227003761c3fc562c21bb859a5256f2b36) or  newer and
> >> bitbake
> >> * Its only able to build core-image-minimal
> >> * core-image-minimal boots on qemuarm, qemuppc, qemumips, qemux86, 
> >> qemux86-64
> >>
> >> I will send a request to add it to layerindex soon and then you should
> >> be able to find it using
> >> layerindex.opernembedded.org as well
> >>
> >> If you try it out on your hardware and/or have feedback I am
> >> interested. Fork it from github, file bugs
> >> send patches 
> >>
> >> Happy hacking
> >>
> >
> > core-image-minimal works with my configuration on qemuarm. It also 
> > successfully
> > builds what will soon be released as opkg-0.2.3 and the recipe for 
> > toybox-0.4.9
> > which I've recently created.
> >
> > I tried building core-image-full-cmdline as I think that would be good next 
> > step
> > from core-image-minimal. I'm seeing failures in:
> >
> >   meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb, do_compile
> >   meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb, do_compile
> >   meta/recipes-extended/libtirpc/libtirpc_0.2.4.bb, do_compile
> >   meta/recipes-extended/iptables/iptables_1.4.21.bb, do_compile
> >   meta/recipes-connectivity/nfs-utils/libnfsidmap_0.25.bb, do_compile
> >   meta/recipes-devtools/perl/perl_5.20.0.bb, do_compile
> >   meta/recipes-extended/sysklogd/sysklogd_1.5.bb, do_compile
> >   meta/recipes-extended/ethtool/ethtool_3.14.bb, do_compile
> >   meta/recipes-extended/psmisc/psmisc_22.21.bb, do_compile
> >   meta/recipes-extended/pax/pax_3.4.bb, do_compile
> >   meta/recipes-extended/procps/procps_3.2.8.bb, do_compile
> >   meta/recipes-extended/net-tools/net-tools_1.60-25.bb, do_compile
> >   meta/recipes-extended/findutils/findutils_4.4.2.bb, do_compile
> >   meta/recipes-extended/logrotate/logrotate_3.8.7.bb, do_compile
> >   meta/recipes-extended/cronie/cronie_1.4.11.bb, do_compile
> >   meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile
> >   meta/recipes-extended/at/at_3.1.14.bb, do_compile
> >   meta/recipes-extended/iputils/iputils_s20121221.bb, do_compile
> >   meta/recipes-extended/gzip/gzip_1.6.bb, do_compile
> >   meta/recipes-extended/sudo/sudo_1.8.10p3.bb, do_compile
> >   meta/recipes-extended/mc/mc_4.8.12.bb, do_compile
> >
> > I can share detailed logs if anyone wants them. I'll have a look and see if 
> > I
> > can find some low hanging fruit amongst these which are easy to fix.
> >
> 
> 
> Thanks cool. Can you open a ticket on github with this information ?

Will do. Do you want just want one ticket or do you want to separate these into
one ticket per failing recipe or similar?

I've put the failing "log.do_compile" files into one directory which is 1.3MB
uncompressed or just 41kB compressed. I've posted them to:
  http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/
  
http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/musl-error-logs_2014-08-18.tar.xz

Cheers,

-- 
Paul Barker

Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk


pgpeEjkX7Kglw.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Khem Raj]

On Mon, Aug 18, 2014 at 11:14 AM, Paul Barker  wrote:
> On Sat, Aug 16, 2014 at 05:50:38PM -0700, Khem Raj wrote:
>> Hello All
>>
>> musl  is a newer implementation licensed
>> under MIT licence
>> A layer to support musl to supply your system C library as an
>> alternative to uclibc and eglibc/glibc  is now available at
>>
>> https://github.com/kraj/meta-musl
>>
>> README describes way to get going with it.
>>
>> Few things to note
>>
>> * Supports gcc 4.9 in OE not 4.8
>> * Current musl recipe is 1.1.4 based
>> * You need latest master of OE-Core
>> (106305227003761c3fc562c21bb859a5256f2b36) or  newer and
>> bitbake
>> * Its only able to build core-image-minimal
>> * core-image-minimal boots on qemuarm, qemuppc, qemumips, qemux86, qemux86-64
>>
>> I will send a request to add it to layerindex soon and then you should
>> be able to find it using
>> layerindex.opernembedded.org as well
>>
>> If you try it out on your hardware and/or have feedback I am
>> interested. Fork it from github, file bugs
>> send patches 
>>
>> Happy hacking
>>
>
> core-image-minimal works with my configuration on qemuarm. It also 
> successfully
> builds what will soon be released as opkg-0.2.3 and the recipe for 
> toybox-0.4.9
> which I've recently created.
>
> I tried building core-image-full-cmdline as I think that would be good next 
> step
> from core-image-minimal. I'm seeing failures in:
>
>   meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb, do_compile
>   meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb, do_compile
>   meta/recipes-extended/libtirpc/libtirpc_0.2.4.bb, do_compile
>   meta/recipes-extended/iptables/iptables_1.4.21.bb, do_compile
>   meta/recipes-connectivity/nfs-utils/libnfsidmap_0.25.bb, do_compile
>   meta/recipes-devtools/perl/perl_5.20.0.bb, do_compile
>   meta/recipes-extended/sysklogd/sysklogd_1.5.bb, do_compile
>   meta/recipes-extended/ethtool/ethtool_3.14.bb, do_compile
>   meta/recipes-extended/psmisc/psmisc_22.21.bb, do_compile
>   meta/recipes-extended/pax/pax_3.4.bb, do_compile
>   meta/recipes-extended/procps/procps_3.2.8.bb, do_compile
>   meta/recipes-extended/net-tools/net-tools_1.60-25.bb, do_compile
>   meta/recipes-extended/findutils/findutils_4.4.2.bb, do_compile
>   meta/recipes-extended/logrotate/logrotate_3.8.7.bb, do_compile
>   meta/recipes-extended/cronie/cronie_1.4.11.bb, do_compile
>   meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile
>   meta/recipes-extended/at/at_3.1.14.bb, do_compile
>   meta/recipes-extended/iputils/iputils_s20121221.bb, do_compile
>   meta/recipes-extended/gzip/gzip_1.6.bb, do_compile
>   meta/recipes-extended/sudo/sudo_1.8.10p3.bb, do_compile
>   meta/recipes-extended/mc/mc_4.8.12.bb, do_compile
>
> I can share detailed logs if anyone wants them. I'll have a look and see if I
> can find some low hanging fruit amongst these which are easy to fix.
>


Thanks cool. Can you open a ticket on github with this information ?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Paul Barker]

On Sat, Aug 16, 2014 at 05:50:38PM -0700, Khem Raj wrote:
> Hello All
> 
> musl  is a newer implementation licensed
> under MIT licence
> A layer to support musl to supply your system C library as an
> alternative to uclibc and eglibc/glibc  is now available at
> 
> https://github.com/kraj/meta-musl
> 
> README describes way to get going with it.
> 
> Few things to note
> 
> * Supports gcc 4.9 in OE not 4.8
> * Current musl recipe is 1.1.4 based
> * You need latest master of OE-Core
> (106305227003761c3fc562c21bb859a5256f2b36) or  newer and
> bitbake
> * Its only able to build core-image-minimal
> * core-image-minimal boots on qemuarm, qemuppc, qemumips, qemux86, qemux86-64
> 
> I will send a request to add it to layerindex soon and then you should
> be able to find it using
> layerindex.opernembedded.org as well
> 
> If you try it out on your hardware and/or have feedback I am
> interested. Fork it from github, file bugs
> send patches 
> 
> Happy hacking
> 

core-image-minimal works with my configuration on qemuarm. It also successfully
builds what will soon be released as opkg-0.2.3 and the recipe for toybox-0.4.9
which I've recently created.

I tried building core-image-full-cmdline as I think that would be good next step
from core-image-minimal. I'm seeing failures in:

  meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb, do_compile
  meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb, do_compile
  meta/recipes-extended/libtirpc/libtirpc_0.2.4.bb, do_compile
  meta/recipes-extended/iptables/iptables_1.4.21.bb, do_compile
  meta/recipes-connectivity/nfs-utils/libnfsidmap_0.25.bb, do_compile
  meta/recipes-devtools/perl/perl_5.20.0.bb, do_compile
  meta/recipes-extended/sysklogd/sysklogd_1.5.bb, do_compile
  meta/recipes-extended/ethtool/ethtool_3.14.bb, do_compile
  meta/recipes-extended/psmisc/psmisc_22.21.bb, do_compile
  meta/recipes-extended/pax/pax_3.4.bb, do_compile
  meta/recipes-extended/procps/procps_3.2.8.bb, do_compile
  meta/recipes-extended/net-tools/net-tools_1.60-25.bb, do_compile
  meta/recipes-extended/findutils/findutils_4.4.2.bb, do_compile
  meta/recipes-extended/logrotate/logrotate_3.8.7.bb, do_compile
  meta/recipes-extended/cronie/cronie_1.4.11.bb, do_compile
  meta/recipes-devtools/elfutils/elfutils_0.148.bb, do_compile
  meta/recipes-extended/at/at_3.1.14.bb, do_compile
  meta/recipes-extended/iputils/iputils_s20121221.bb, do_compile
  meta/recipes-extended/gzip/gzip_1.6.bb, do_compile
  meta/recipes-extended/sudo/sudo_1.8.10p3.bb, do_compile
  meta/recipes-extended/mc/mc_4.8.12.bb, do_compile

I can share detailed logs if anyone wants them. I'll have a look and see if I
can find some low hanging fruit amongst these which are easy to fix. 

Thanks,

-- 
Paul Barker

Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk


pgpnYRNvUVMTf.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fix for meta-oe/recipes-graphics/fbida/fbida_git.bb

[Paul Eggleton]

Hi Jens,

On Sunday 17 August 2014 20:06:10 Jens Rehsack wrote:
> Am 17.08.2014 um 19:39 schrieb Martin Jansa :
> > On Sun, Aug 17, 2014 at 05:02:39PM +0200, Jens Rehsack wrote:
> >> we played a bit with some tools before using a modified psplash to show
> >> some guidance on hdmi-fb and there was an error in fbida which wrongly
> >> mixes host-paths and target paths. Additionally - for Poky or OE it's
> >> unnecessary to guess additional path to check - recipes will do
> >> correctly.
> >
> > Please follow README and send it as inline patch to oe-devel ML.
> > 
> > Thanks
> 
> Hi Martin,
> 
> 1) I do not send inline-patches
> 2) I do not subscribe to more mailing lists just to send patches.
> 
> Either it's helpful and maintainers accept it or it's not and when one uses
> a search engine one applies it locally.

You do want to avoid carrying these patches yourself indefinitely, right?
If so, you'd rather they got merged rather than being missed by the maintainer 
because they weren't in the expected place or format - right?

The way we accept and review patches is via our mailing lists; and we have to 
have more than one list because of the sheer volume of patches and discussion. 
Unfortunately we also have to force subscription in order to protect ourselves 
from spam. However, it's worth noting that you don't actually need to receive 
emails from the list in order to be subscribed - you can disable delivery in 
your account options.

The procedures we have in place do require just a little bit more work on the 
part of the submitter, but that does translate to a huge reduction in work for 
the maintainers; and preserving our maintainers' sanity is important if we 
want to keep the system maintained ;)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] toybox in OpenEmbedded

[Paul Barker]

On Mon, Aug 18, 2014 at 07:29:33AM -0700, Christopher Larson wrote:
> On Mon, Aug 18, 2014 at 6:44 AM, Paul Barker  wrote:
> 
> > I've been wanting to try out toybox within OpenEmbedded for quite a while
> > and
> > have finally found time to put a recipe together. Toybox is a BSD-licensed
> > alternative to Busybox which may be of interest to a few people. It's
> > still a
> > work in progress but it already covers a large number of the basic
> > commands a
> > system needs. It should tie in well with the recent work Khem has done to
> > enable
> > the use of musl in OpenEmbedded as toybox and musl are often used together
> > (e.g.
> > Aboriginal Linux distro).
> >
> > My patches are currently against openembedded-core for convenience but this
> > probably belongs in meta-oe for now. I've done some basic testing on
> > qemuarm but
> > nothing significant. toybox builds and installs correctly though and I've
> > set
> > ALTERNATIVE_PRIORITY = 60 so that it takes precedence over busybox tools.
> >
> > Removing toybox after it has been installed currently bricks the system
> > though
> > as the postrm script runs after '/bin/toybox' has been removed (so things
> > like
> > '/bin/ln' become broken links and the update-alternatives script can't
> > run).
> >
> 
> One option for that might be to try the C implementation of alternatives
> that's provided in chkconfig, rather than cworth's shell version. I haven't
> tested it in that context, but I doubt it runs so many external tools.

I did try that at one point in the last year or so but couldn't get it to work.
I think it was something to do with it lacking offline root support. The only
implementation I've been able to get working is the shell script one which is
now in opkg-utils.

I'm actually looking at making a new update-alternatives implementation in C as
I wanted to explore a few alternative ways of doing things. I was going to post
about that once I have some basic working code.

I think the solution for the removal problem is to call update-alternatives in a
pre-rm script rather than a post-rm script. There's already an entry in the opkg
issue tracker for adding support for pre-rm scripts, that's another thing I'm
planning on fixing soon.

Thanks,

-- 
Paul Barker

Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk


pgpt4mSdnp1pK.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] toybox in OpenEmbedded

[Christopher Larson]

On Mon, Aug 18, 2014 at 6:44 AM, Paul Barker  wrote:

> I've been wanting to try out toybox within OpenEmbedded for quite a while
> and
> have finally found time to put a recipe together. Toybox is a BSD-licensed
> alternative to Busybox which may be of interest to a few people. It's
> still a
> work in progress but it already covers a large number of the basic
> commands a
> system needs. It should tie in well with the recent work Khem has done to
> enable
> the use of musl in OpenEmbedded as toybox and musl are often used together
> (e.g.
> Aboriginal Linux distro).
>
> My patches are currently against openembedded-core for convenience but this
> probably belongs in meta-oe for now. I've done some basic testing on
> qemuarm but
> nothing significant. toybox builds and installs correctly though and I've
> set
> ALTERNATIVE_PRIORITY = 60 so that it takes precedence over busybox tools.
>
> Removing toybox after it has been installed currently bricks the system
> though
> as the postrm script runs after '/bin/toybox' has been removed (so things
> like
> '/bin/ln' become broken links and the update-alternatives script can't
> run).
>

One option for that might be to try the C implementation of alternatives
that's provided in chkconfig, rather than cworth's shell version. I haven't
tested it in that context, but I doubt it runs so many external tools.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] toybox in OpenEmbedded

[Paul Barker]

Hi all,

I've been wanting to try out toybox within OpenEmbedded for quite a while and
have finally found time to put a recipe together. Toybox is a BSD-licensed
alternative to Busybox which may be of interest to a few people. It's still a
work in progress but it already covers a large number of the basic commands a
system needs. It should tie in well with the recent work Khem has done to enable
the use of musl in OpenEmbedded as toybox and musl are often used together (e.g.
Aboriginal Linux distro).

My patches are currently against openembedded-core for convenience but this
probably belongs in meta-oe for now. I've done some basic testing on qemuarm but
nothing significant. toybox builds and installs correctly though and I've set
ALTERNATIVE_PRIORITY = 60 so that it takes precedence over busybox tools.

Removing toybox after it has been installed currently bricks the system though
as the postrm script runs after '/bin/toybox' has been removed (so things like
'/bin/ln' become broken links and the update-alternatives script can't run).

I can send patches but as I say, this is a work in progress and you shouldn't
install toybox using this recipe on a production system yet. Would anyone else
be interested in testing this out? And should I send these patches against
openembedded-core or meta-oe or should I create a separate layer for this until
it stabilises?

Thanks,

-- 
Paul Barker

Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk


pgpVPY0uqSHs7.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] setting ASSUME_PROVIDED just for target package

[Marek Andrus]

Hi,

I'd like to tell bitbake not to build python for target, but I still 
want python-native.


If I add
ASSUME_PROVIDED += "python"
it stops building both python and python-native. If it add
ASSUME_PROVIDED += "python-native"
it stops building just python-native.

What to do to prevent building just python ("-target")?

BR,
Marek
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-security][PATCH 0/3] Samhain package

[Alexandru Vaduva]

Thanks Armin,

This package will be a nice addition to meta-cgl layer.


Alex



On Monday, August 18, 2014 5:43 AM, Armin Kuster  wrote:
 


I have been sitting on this far to long. Wanted to get it
out before I completely space on it. 

Armin Kuster (3):
  samhain: New ISD package
  samhain: client package
  samhain: server package

.../samhain/files/samhain-client.default           |   3 +
recipes-security/samhain/files/samhain-client.init | 122 +
.../samhain/files/samhain-server-volatiles         |   1 +
.../samhain/files/samhain-server.default           |   3 +
recipes-security/samhain/files/samhain-server.init | 116 
recipes-security/samhain/samhain-client_3.1.1.bb   |  21 
recipes-security/samhain/samhain-server_3.1.1.bb   |  50 +
recipes-security/samhain/samhain.inc               |  82 ++
8 files changed, 398 insertions(+)
create mode 100644 recipes-security/samhain/files/samhain-client.default
create mode 100644 recipes-security/samhain/files/samhain-client.init
create mode 100644 recipes-security/samhain/files/samhain-server-volatiles
create mode 100644 recipes-security/samhain/files/samhain-server.default
create mode 100644 recipes-security/samhain/files/samhain-server.init
create mode 100644 recipes-security/samhain/samhain-client_3.1.1.bb
create mode 100644 recipes-security/samhain/samhain-server_3.1.1.bb
create mode 100644 recipes-security/samhain/samhain.inc

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto