On 9 March 2016 at 08:28, Gary Thomas wrote:
> BTW, if I run 'bitbake -c cleanall' where is the
> name of my recipe that is creating a user (in this case amanda), shouldn't
> that user/group be removed from the sysroot? It's not and it took me a
> long time to realize this - my first attempts
On 15 March 2016 at 22:56, Chris Tapp wrote:
> Should I use master or master-next to track 2.1 release progress?
>
master-next is a guideline of what's due to be merged shortly but patches
will be re-ordered, rebased, partially merged or dropped from it, so only
do that if you're sure. And doub
On 16 March 2016 at 08:56, Mark T wrote:
> I'd like to be able to do the following
>
> IMAGE_INSTALL_append += "package_a"
> if ( not qemu )
> IMAGE_INSTALL_append += "package_b"
> endif
>
The neater way would be if you can easily identify what "not qemu" is, for
example:
IMAGE_INSTALL_append_i
On 18 March 2016 at 17:32, Mark T wrote:
> Thanks, that " IMAGE_INSTALL_append_intel-corei7-64 = "package_b" " worked
> a treat.
>
> If I want to exclude a recipe from a layer for qemu builds - is there a
> similar method for that ?
>
You can use _remove_qemuall for that.
Ross
--
__
On 16 March 2016 at 14:54, Ashish Shrivastava
wrote:
> Now gstreamer is throwing error for introspection.
>
>
> I am trying to disable it but with no success.
>
Can you include the full log of what errors you see?
Ross
--
___
yocto mailing list
yocto
On 16 March 2016 at 16:13, Martin Jansa wrote:
> I think it's because COMBINED_FEATURES conditional is used only to add
> --enable-introspection in EXTRA_OECONF, but other changes like
> introspection.m4 changes are done in all builds.
>
Then the class should be passing --disable-introspection.
On 17 March 2016 at 09:37, Andre McCurdy wrote:
> As an aside, I'm not sure that using DISTRO/MACHINE_FEATURES_BACKFILL
> for gobject-introspection-data is entirely correct since gobject
> introspection is not a feature which was previously enabled by
> default:
>
That is true. Maybe we should
On 18 March 2016 at 15:11, Jussi Kukkonen wrote:
> XChangeProperty documentation: "If the specified format is 32, the
> property data must be a long array."
>
> Using int can lead to bogus data being used on platforms where long
> actually is different from int.
>
> Signed-off-by: Jussi Kukkonen
On 17 March 2016 at 03:03, 윤영석 wrote:
> So, i had try to found crosswalk recipes,
>
> finally i got it. but it is not lately version. (version : 12.40.295.0)
>
> refer under the link,
>
> https://github.com/crosswalk-project/meta-crosswalk
>
I suggest you try asking the crosswalk developers (eit
On 20 March 2016 at 11:24, Jussi Kukkonen wrote:
> There are cases (in qemu at least) where set_active()
> is never called on startup. Make sure we initialize the active
> state so the icon gets loaded and the applet is not confused
> about the current state.
>
Pushed to master, thanks.
Ross
--
On 22 March 2016 at 10:41, Jussi Kukkonen wrote:
> This prevents an opportunistic alt-F4 from closing the desktop.
>
Pushed, thanks
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 5 April 2016 at 19:55, Ronald Oakes wrote:
> Illegal instruction
>
It probably built a binary to run on your host using compiler flags for
your target, which means that the binary contains instructions your
processor can't execute.
What release of OE/Poky/Yocto/whatever is this?
Ross
--
__
On 5 April 2016 at 23:17, Ronald Oakes wrote:
> I'm basing off of poky-jethro-14.0.1.tar.bz as downloaded from
> yoctoproject.org. I've also got meta-intel from the git of that name
> to support the corei7, my eventual target.
>
The full compile and install logs would be helpful.
Cheers,
Ross
On 6 April 2016 at 11:53, Chris Trobridge
wrote:
> ImportError: No module named importlib
>
Looks like python-gobject needs to depend on python-importlib. Not sure
why that isn't in -core to be honest.
Can you add python-importlib to your image and see if it then works, or if
other modules are
On 6 April 2016 at 12:19, Chris Trobridge
wrote:
> This did the trick for python 2.7, and "from gi.repository import GObject"
> works too.
>
Can you send a patch to add this dependency to the pygobject package?
Ross
--
___
yocto mailing list
yocto@yo
On 6 April 2016 at 15:27, Ronald Oakes wrote:
> Unfortunately, my build system is airgapped from the Internet, making
> copying files into emails (or attaching them) extremely difficult.
>
Can you not put them on a USB stick?
Ross
--
___
yocto mailin
On 6 April 2016 at 16:45, Chris Trobridge
wrote:
> I will try to sort that out tomorrow (p...@yoctoproject.org, right?).
>
No, openembedded-c...@lists.openembedded.org
Regarding python3, whenever I change the "--with-python" option to
> something other than "python2.7" then I get an error.
>
Y
On 6 April 2016 at 18:18, Santosh Y wrote:
> Can sstate cache be shared among builds for different architectures like
> x86 & PowerPC?
>
> Yes (and different host distros).
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproje
On 6 April 2016 at 20:55, Ronald Oakes wrote:
> For what it's worth, I may be able to work around this by using the
> Poky-Tiny distribution, which is closer to what I'll need for the
> minimalist system we need in the end.
>
If you need a minimal system then you might want to look at oe-core fr
On 7 April 2016 at 08:05, Khem Raj wrote:
> busybox based init system is available and used in many
> other distributions e.g. buildroot, therefore use that
> combination with mdev gives a scalable image and chance
> to execute sysvinit scripts as well, adding nothing to
> image size.
>
> +VIRT
On 7 April 2016 at 14:28, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> You need to change the inherits to pull in python3native. Sadly
>> flipping between py2 and py3 isn't trivial.
>>
>
> I think 'git revert 7f7c9ab29eba0e58916629ca13dc4a494535ce19' should do
> the trick, how
On 7 April 2016 at 14:29, Hans-Georg Bader wrote:
> Here is the output:
> bader@ubuntu64:~/oe-core/build$ bitbake -b php_5.4.36
> WARNING: Buildfile specified, dependencies will not be handled. If this is
> not what you want, do not use -b / --buildfile.
>
The clue is in the output. Don't use -
On 8 April 2016 at 15:30, Andy Gikling wrote:
> Dear Yocto,
>
>
>
> First of all, I love this project. Thanks for all your hard work.
>
>
>
> Question: What is the prescribed way to allow image recipes to make
> global configuration variables that other recipes can use?
>
>
You can't. The basi
On 8 April 2016 at 16:05, Andy Gikling wrote:
> So what do I do in that case? Just make two of my own versions of the
> u-boot_2014.04.bb file, and give them different names? For example “
> u-boot-faux_2014.04.bb” and “u-boot-faux-debug_2014.04.bb” ? That should
> work but does that make sense
On 12 April 2016 at 12:43, Jussi Kukkonen wrote:
> Handle even the last combo, the one with all modifiers applied at the
> same time.
>
This and 1/2 both pushed to master, thanks Jussi!
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://li
This series is now merged, thanks Richard.
Ross
On 13 April 2016 at 14:57, Richard Leitner
wrote:
> The "Contributing" guideline section should help people sending their
> patches correctly.
>
> A similar section is available in nearly all
> layers/repositories hosted on yoctoproject.org. There
All pushed, thanks Richard.
Ross
On 14 April 2016 at 11:59, Richard Leitner
wrote:
> Define UNUSED macro for GCC's ((__unused__)) attribute and use it for
> the remaining unused-parameter warnings. These unused parameters are
> required due to the definition of the sighandler_t.
>
> This fixes
On 14 April 2016 at 12:18, Vajzovic, Tom wrote:
> What command can I use to do the equivalent of running "bitbake -c clean"
> (or cleanstate etc) for all recipes that have previously been run?
>
The easy answer here is rm -rf tmp/. What do you actually want to do?
Ross
--
On 14 April 2016 at 21:05, Michael Hu wrote:
> Yocto pulls in systemd and enable certain features by default.I am trying
> to remove some features in systemd *225* yocto builds such as logind
> (just for testing purpose), I was trying to use a '*.bbappend' file with
> 'PACKAGECONFIG_append' to ac
Hi,
At the moment we don't really have a policy for oe-core bugs in
bugzilla.yoctoproject.org that apply to multiple releases, for example
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9400. This is a CVE bug
that should be fixed in all supported branches, and indeed Sona has sent
patches for
On 18 April 2016 at 18:35, Khem Raj wrote:
> Can we have a possibility to select field like "affected version" and
> have it such that multiple versions can be specified
>
You'd then need to have the ability to set multiple target versions, and
track each of those independently. Without this y
On 19 April 2016 at 03:17, Christopher Larson wrote:
> There may be something better out there, and if we can find it, great, but
> I think separate issues is better than not addressing the issue at all, but
> only if the tooling is good enough to help reduce overhead on the part of
> the devs de
On 22 April 2016 at 18:04, Trevor Woerner wrote:
>
> Have the eSDK and CROPS projects been announced publicly? Are they
available
> for us to "play with"?
eSDK is the "extensible SDK', or what appears when you do bitbake image -c
populate_sdk_ext. This should be in the manual already, the tl;dr
On 25 April 2016 at 00:17, Trevor Woerner wrote:
> > CROPS is docker magic to do builds on Windows/Mac. Todor did a
> > presentation at ELC: http:
> > //
> events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> > <
> http://events.linuxfoundation.org/sites/events
On 25 April 2016 at 07:46, Amarnath Valluri
wrote:
> I would like to provide a pakcagegroup-config, that should automatically
> select the configuration packages that are part of image configuration. Say
> if ‘connman’ is part of image then it should add ‘connman-conf’ to its
> RDEPENDS_${PN}.
>
On 25 April 2016 at 14:30, Jaggi, Manish
wrote:
> It seems the revid / tag is not on any branch
> git branch --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
> returns nothing.
>
> How to fix this issue ?
>
You probably want to use git branch -r --contains 213... as otherwise git
branch will
On 26 April 2016 at 09:04, wrote:
> I am new to yocto. I like to create an recipe for the g3log library. I
> managed to get the git sources and start the cmake compile. But it stops
> when it tries to compile "#include ". Do you have an idea how to
> fix that?
>
Actually including the output of
On 26 April 2016 at 09:37, Jaggi, Manish
wrote:
> IMAGE_INSTALL_append = "gcc"
> IMAGE_INSTALL_append += " glibc"
> IMAGE_INSTALL_append += " libgcc"
> IMAGE_INSTALL_append += " binutils"
> IMAGE_INSTALL_append += " gccmakedep"
>
You left out the development headers and libraries required to act
On 27 April 2016 at 07:27, Chris Trobridge
wrote:
> Aside from the issues I mentioned previously, pjproject is detecting
> cross-compilation and this causes it to append '-x86_64-poky-linux-gnu' to
> all its library names.
>
> This is then breaking autotools configuration in other recipes that ar
On 27 April 2016 at 03:30, Paul Eggleton
wrote:
> Looking at meta/recipes-devtools/qemu/qemu.inc it is explicitly looking at
> DISTRO_FEATURES for the native class. That seems wrong to me as well, but I
> would be surprised if it were the only place we were referring to
> DISTRO_FEATURES in the n
On 21 April 2016 at 04:06, Khem Raj wrote:
> I have updated
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-6
>
> With few more patches added now. Most of packages in OE-Core are
> building fine except linux-yocto on mips and ppc
>
I threw this at the autobuilder. Lots
Finally made errors.yp do the right thing:
http://errors.yoctoproject.org/Errors/Latest/?filter=91ef7bf5ad13304827e2ef06738f7fc28ed650f6&type=commit
is a list of all the failures.
Ross
On 27 April 2016 at 09:02, Burton, Ross wrote:
>
> On 21 April 2016 at 04:06, Khem Raj wrote:
&
On 27 April 2016 at 09:48, Gary Thomas wrote:
> Is there any way to not have both the hwdb.bin (which I assume
> is a binary version of the hardware databases) and /etc/udev/hwdb.d?
> Perhaps there is some way to only use one?
>
> Or maybe there is a better choice, such as mdev? I'm not sure abo
On 27 April 2016 at 10:22, Gary Thomas wrote:
> Can you explain a bit more? - BAD_RECOMMENDS doesn't seem to be documented.
>
My mistake - BAD_RECOMMENDATIONS.
http://www.yoctoproject.org/docs/2.0.1/ref-manual/ref-manual.html#var-BAD_RECOMMENDATIONS
Ross
--
___
On 27 April 2016 at 10:07, Chris Trobridge
wrote:
> pjproject hasn't been touched for 6 years and has some custom steps I
> don't understand (
> https://github.com/openembedded/openembedded/tree/master/recipes/pjproject
> ).
>
> asterisk (
> https://github.com/openembedded/openembedded/tree/maste
On 27 April 2016 at 14:03, Lars Larsen wrote:
>
> BRANCH ?="develop"
> SRC_URI =
"git:///eserver/GIT/autodiscover/;branch=${BRANCH};;name=discover "
> SRCREV_discover= "${AUTOREV}"
> SRCREV_FORMAT= "discover"
This is likely the problem.
$(AUTOREV) means "go and get the latest revision every bui
On 28 April 2016 at 10:50, wrote:
> I like to include the hiredis library. I created a recipe and modified the
> EXTRA_OEMAKE. The compilation works (in the git directory object, "so" and
> "a" files are generated). But the generated files are not placed into
> packages.
>
> Any ideas?
>
You nee
On 28 April 2016 at 13:09, wrote:
> ERROR: QA Issue: libhiredis: Files/directories were installed but not
> shipped in any package:
> /usr/local
>
It either hard-codes /usr/local as the prefix, or if it respects a prefix
variable you should also pass in ${prefix} ${libdir} ${includedir} and so
On 28 April 2016 at 16:25, Fred Ollinger wrote:
> FILES_${PN} += "/usr/local"
>
Please don't do this unless that's actually what you want - nothing else in
the image will be using those paths so eg libraries in there might not be
found.
Ross
--
___
y
On 28 April 2016 at 17:09, wrote:
> EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS}
> -I${S}/include' 'BUILDDIR=${S}' 'DESTDIR=${D}'"
>
Neater to pass DESTDIR via do_install, so remove DESTDIR from here.
However you want to tell it where PREFIX is, and that goes into
On 28 April 2016 at 17:18, YUKATHARSANI JEYACHANDRA <
yukatharsa...@tataelxsi.co.in> wrote:
> Use INSANE_SKIP_${PN} = "installed-vs-shipped" in your recipe to avoid
> this error. Orelse, add FILES_${PN} += "/usr/local/" in your recipe.
>
> No.
*Only* use installed-vs-shipped if you're incapable
Took it for another ride on our AB last night:
http://errors.yoctoproject.org/Errors/Latest/?filter=ab893d4e1c3efc1ee73c6cfbbb9a64036c63d93c&type=commit
The systemd-sysusers stuff I failed to remove, and is broken.
There's a pango-native failure that appears to be caused by GIR.
And two SDK ima
Hi Stefan,
So close :) Some more points:
On 29 April 2016 at 08:54, wrote:
> LICENSE = "COPYING"
This should be the name of the license itself, not the filename. Looks a
bit like MIT to me.
> LIC_FILES_CHKSUM =
"file://${WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"
This URI is
On 29 April 2016 at 10:59, wrote:
> Finally we made it - Thanks to you all for helping me! I attached my bb
> file for that case someone is searching for a bitbake recipe for building
> the libhiredis
>
If you submit the recipe to meta-oe then you can share development of the
recipe with others.
On 29 April 2016 at 15:01, SIVA SUBRAMANIAN.P wrote:
> > If you submit the recipe to meta-oe then you can share development of the
> > recipe with others.
>
> How can we do that? Kindly guide.
>
In general the README at the top of the layer that your recipe would be
suited for should tell you ho
On 29 April 2016 at 08:47, Jussi Kukkonen wrote:
> -PKG_CHECK_MODULES(APP, [gconf-2.0 gdk-x11-2.0 x11])
> +PKG_CHECK_MODULES(APP, [gconf-2.0 gdk-x11-3.0 x11])
>
Looking at this, so little of GTK+ is used (just gdkx). Maybe we should
port this to pure XLib?
Ross
--
Merged and pushed, thanks Jussi. I've started tagging the last GTK+ 2
commit with 'GTK+2'.
Ross
On 29 April 2016 at 11:41, Jussi Kukkonen wrote:
> Signed-off-by: Jussi Kukkonen
> ---
> Makefile.am | 4 ++--
> configure.ac | 2 +-
> main.c | 49 +++
Hi,
mb-appearance.c: In function 'new_frame':
mb-appearance.c:352:3: warning: 'gtk_alignment_get_type' is deprecated
[-Wdeprecated-declarations]
*align = g_object_new (GTK_TYPE_ALIGNMENT,
^
In file included from /usr/include/gtk-3.0/gtk/gtk.h:248:0,
from mb-appearance.c:28:
On 29 April 2016 at 08:06, Jussi Kukkonen wrote:
> This still has all the problems that the new API would allow us to
> fix: mainly that multiple displays will almost certainly not work
> at all.
>
screenshot-utils.c: In function 'screenshot_grab_lock':
screenshot-utils.c:251:3: warning: 'gdk_po
On 10 May 2016 at 16:04, Christian Ege wrote:
> -DAEMON=/usr/lib/bluez5/bluetooth/bluetoothd
> +DAEMON=/usr/libexec/bluetooth/bluetoothd
>
This is only true if libexecdir is set to /usr/libexec (the original patch
was equally broken). Can you change the recipe so that the init script
uses some
On 13 May 2016 at 08:25, Chandrakanth Sherkhane (IC Nexus) <
c...@icnexus.com.tw> wrote:
> Could anyone help to provide more details for,
>
> 1. Yocto Virtual Keyboard in French language - is it available now?
>
> 2. If not available, when will it be available?
>
> 3. Is the Yocto Virtual Keyboard
On 13 May 2016 at 15:21, wrote:
> I try to build the libdbus-c++ libary. The build process is based on
> autotools. When compiling it do_configure throws an error. The macro
> "AC_DEFINE" is not found. Any idea how to make autoreconf run?
>
Try also inheriting pkgconfig. I've noticed that if t
Hi Herve,
Can you submit the two patches (caps behaviour, and french layout) against
the matchbox-keyboard-0.1 branch directly to this list please? Then we can
just bump the srcrev in the recipe instead of carrying patches against our
own software.
Ross
On 17 May 2016 at 10:43, Herve Jourdain
On 17 May 2016 at 02:15, Andrew Jeffery wrote:
> Is there a better way to work that might avoid these issues?
> Alternatively, should we start looking at reworking the
> runqemu/runqemu-internal scripts such that we don't have to patch them
> to support our use-case? If so, what sort of approach
On 18 May 2016 at 08:58, Christian Fuchs wrote:
> I just checked and EXTRA_OECONF is not correctly expanded. It is missing
> the "ac_cv_sizeof_off_t=8" part that is present on the Ubuntu machine.
>
Have you verified that DISTRO_FEATURES is identical on both?
Ross
--
___
On 18 May 2016 at 09:13, Andrew Jeffery wrote:
> Thanks for the pointer. Is this the patchset you're referring to?
>
>
> http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118982.html
>
> A brief look suggests it might get us some of the way there, but I'll
> take a more detaile
On 2 May 2016 at 08:48, Jussi Kukkonen wrote:
> The grab code was trickier with current API (which is why I left it as
> is), but I took another look and it turns out that code has never
> actually been used...
>
> So I removed _grab_lock() and _release_lock(), and replaced STOCK
> items with tex
On 19 May 2016 at 17:36, Colin Helliwell
wrote:
> I have a recipe (for kura) which uses a do_compile to run kura's build
> process, and this in itself generates a .deb (i.e. I'm not doing anything
> within the *recipe* to create the .deb - it's done for me by kura's build
> steps). I can copy the
On 20 May 2016 at 21:17, Sywula, Krzysztof M
wrote:
> I recommend we add ‘bluez5’ to 11.2 Distro Features section as that’s
> where people go to find available values for DISTRO_FEATURES variable.
>
>
Agreed. I've forwarded this to Scott to ensure it gets done.
Ross
--
On 22 May 2016 at 00:52, Bjorn Sorensen wrote:
> I need to have two separate recipes for "libftdi" and "ftdi-eeprom" in my
> meta layer, which both of them are build dependencies for one package. The
> issue is that the said packages are actually in one tarball and when I
> build "libftdi" it bui
On 22 May 2016 at 22:19, Bjorn Sorensen wrote:
> Its the other way around, actually libftdi builds eeprom. I am still a
> newbie with Yocto and dont have the knowledge to manipulate the builds from
> the recipe like you suggested.
> Although I managed the workaround by adding the SSTATE_DUPWHITEL
On 22 May 2016 at 17:35, Gerard Bucas wrote:
> I am trying to bitbake core-image-sato with Chromium (as per
> https://github.com/ds-hwang/wiki/wiki/build-chromium-on-yocto )
>
> BUT I keep getting a build error on libsoup (using master). Can't seem to
> resolve it.
>
Hi Gerard,
Theres no error
On 23 May 2016 at 12:36, Alvaro Martinez Tovar wrote:
> until now I have followed a "manual" methodology to add script to startup
> on system boot:
> - create sh file
> - made it executable and copy it to /etc/init.d
> - add it with update-rc.d my-startup-file.sh defaults 99 to be executed
> just
On 26 May 2016 at 17:01, Jonathan Haws wrote:
> However, when building core-image-full-cmdline, I get the following errors.
>
The error is in the batctl recipe, does that also have a DEPENDS=libnl?
Ross
--
___
yocto mailing list
yocto@yoctoproject.or
On 26 May 2016 at 17:36, Jonathan Haws wrote:
> I did find that if I do:
>
> DEPENDS += " batman-adv libnl"
>
> instead of
>
> DEPENDS_${PN} += " batman-adv libnl"
>
DEPENDS is built-time for the recipe, so the concept of per-package build
dependencies doesn't really make sense.
DEPENDS = "foo
On 26 May 2016 at 18:03, Jonathan Haws wrote:
> > DEPENDS is built-time for the recipe, so the concept of per-package
> > build dependencies doesn't really make sense.
> >
> > DEPENDS = "foo bar" are build dependencies
> > RDEPENDS_${PN} = "foo bar" are package-specific runtime dependencies.
>
>
On 26 April 2016 at 08:57, Jussi Kukkonen wrote:
> MBWM already supports setting MB theme with "MATCHBOX/THEME",
> there is no advantage to also set it with "Net/ThemeName" -- the
> expectation that MBWM has a matching theme for all toolkit themes
> is not realistic.
>
> Net/ThemeName is used by
On 2 June 2016 at 10:03, Jussi Kukkonen wrote:
> Typical result of separate Applications and Utilities is that
> Applications only contains a single icon. Applications is also
> the default folder: it's a waste of space to have that empty.
>
> Merge all Utilities into Applications.
>
Reviewed-by
On 31 May 2016 at 12:09, Alfonso Lima Astor
wrote:
> Do you know where this rdependency could get pulled into? how could I
> remove it?
>
This can happen if the package generates unversioned libraries that look
like development symlinks (such as /usr/lib/libfoo.so), which by default
get packaged
2016-05-30 12:59 GMT+01:00 :
> I want to build a recipe for a cmake based application. To make it run I
> need to set a cached cmake variable.
>
EXTRA_OECMAKE += "-DVARIABLE_NAME=value"
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lis
On 31 May 2016 at 23:11, Julien Gueytat wrote:
> A new fbdev file is needed and should be overrided if needed.
> The number contained in fbdev will be used as X in /dev/fbX.
>
> By overriding fbdev you can have a splash screen on another
> framebuffer than /dev/fbO.
>
> The getenv(FBDEV) line has
On 6 June 2016 at 10:39, wrote:
> I have a git source which need some submodules. For that I need to execute
> "git submodule init" and "git submodule update". Any idea how to do it in a
> comon way?
>
Use the gitsm: fetcher, which will do that for you.
Ross
--
On 7 June 2016 at 13:10, piotr.lewicki wrote:
> Is it possible to manipulate DISTRO_FEATURES from my image recipe file?
>
No. You should control distro features in your distro configuration or if
they're for local tweaking in your local.conf. Would it be helpful if you
explained why you want t
On 5 June 2016 at 17:44, Gary Thomas wrote:
> I just updated my Poky repo and did a rebuild and saw this "error"
> (although it carried on with the build):
> ERROR: base-files-3.0.14-r89 do_install: Taskhash mismatch
> ceb25febc6f11a5cc2b3c4a4b0b2c136 verses 44f498452dfce5875451bca66b230e31
> for
On 7 June 2016 at 17:02, Burton, Ross wrote:
> It means the hash calculated my the bitbake master was different to the
> hash calculated when the worker started up. This usually means that you're
> using something like ${TIME} in the recipe but not marking it appropriatly
> so
On 8 June 2016 at 10:20, piotr.lewicki wrote:
> I actually want to enable systemd in all packages, but my current DISTRO
> is "poky".
> Can you point me some documentation where I can get information on how to
> create a distro file based on poky and add systemd there?
>
http://www.yoctoproject.
On 9 June 2016 at 16:13, Rajasekaran, Monica <
monica.rajaseka...@us.fujitsu.com> wrote:
> I am new to the Yocto project. Could someone please give me information on
> how to install openvswitch ? I have already done the same in other Linux
> OSs but no idea on how to do the same for Yocto.
>
>
Th
On 9 June 2016 at 16:58, Edward Wingate wrote:
> Does anyone have an example of a recipe that installs a python module
> from a git repo? There is a python module that is not regularly
> updated on PyPI, but its git repo is up to date. All the examples of
> python module recipes I can find uses
On 9 June 2016 at 15:52, wrote:
> I switched from RPM to DEB because the board configuration should be
> handled by a package manager. By doing so I ran into a QA problem. All the
> software provided by my colleagues I maked with
Note that deb is the least-tested package manager, we generally r
On 9 June 2016 at 19:56, Rajasekaran, Monica <
monica.rajaseka...@us.fujitsu.com> wrote:
> Doesn’t that include the openvswitch folder as well? If it is, what else
> do I need to add/change?
>
>
You need to actually add the packages that you want to your image.
Ross
--
__
On 9 June 2016 at 22:40, Rajasekaran, Monica <
monica.rajaseka...@us.fujitsu.com> wrote:
> I have openvswitch package installed in my image. But, I do not see a
> folder called “openvswitch-2.xx” with all the source code at all! I need
> the code to make changes. I see these:
>
>
You installed bin
On 10 June 2016 at 09:33, Gary Thomas wrote:
> bitbake -g by itself works fine. Is this a [new] issue with my
> build host, or just the change over to python3?
>
That's missing packages on your build host.
Ross
--
___
yocto mailing list
yocto@yoctop
On 10 June 2016 at 09:39, Gary Thomas wrote:
> Any hints on which (and why it's not being recommended by the sanity
> checker)?
>
It's not recommended by the sanity checker because its only needed by
depexp and on a X11-less build server will pull in vast numbers of packages.
It's the python2 G
On 10 June 2016 at 11:06, Gary Thomas wrote:
> bitbake -u depexp used to work on this same system before the change over
> to
> python3 in bitbake.
>
Sorry I meant python3 :)
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctopr
On 10 June 2016 at 06:54, Maxin B. John wrote:
>
> Had the same experience. We need to modify depexp.py to support python3:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=maxin/depexp
> ( Please note that this is a work in progress )
>
Ah my plan to leave it until someone else
Hi Bartosz,
Please can you re-send these to the bitbake list?
Thanks,
Ross
On 7 June 2016 at 16:15, Woronicz, Bartosz ( NSN - PL/Wroclaw) <
bartosz.woron...@nokia.com> wrote:
>
> --
> Kind regards,
> Bartosz Woronicz
> Engineer, Software Configuration (SCM)
> Nokia Networks - PL/Wroclaw
>
>
> -
On 10 June 2016 at 19:12, Michael Hu wrote:
> What could be the difference?
>
bitbake uses quilt to apply patches, not git am, so if the patch isn't
exactly right then they'll behave differently. Stripping the trailing CRs
would be a start.
Ross
--
On 13 June 2016 at 22:47, Rajasekaran, Monica <
monica.rajaseka...@us.fujitsu.com> wrote:
> I thought it would be the usual method as in other linux versions such as
> Ubuntu. But there is no /etc/resolv.conf file.
>
>
Did you try just creating a /etc/resolv.conf with the nameserver entries
you wa
On 14 June 2016 at 14:48, Jeffrey D Boyer wrote:
> FYI, I'm running 3.14 kernel. Is this a job for aufs? If so, how would I
> go about configuring it?
>
If you want to support arbitrary mounts then it's probably simplest to
either change /media to be a symlink to /run/media, or put a tmpfs on
On 9 June 2016 at 02:11, Dey, Megha wrote:
> However, I do have a script recipe which is currently placed as a bbappend
> to initscripts (meta/recipes-core/initscripts/initscript_..bb) in my custom
> meta layer.
>
>
>
> This script even after shifting to systemd, is being placed in the
> /etc/ini
701 - 800 of 1567 matches
Mail list logo
