Hello
I have the following kernel recipe, which is based on some help from
Bruce Ashfield last year:
-
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
SUMMARY = "Linaro Kernel 3.14 with additional machine specific patches"
Hi
I'm currently moving from Dora to Fido. I moved all my recipes to a new
yocto installation and are modifying the recipes where necessary.
I have a very strange error when configuring a kernel recipe
(linux-cubox-i). Actually, there is no error when using the defaut
recipe included in fido. Onl
Hi
short question: In my own distro (inheriting from core-image), I
automatically get udev and udev-extraconf included. While I like udev, I
don't think I need udev-extraconf. Especially I don't want the automount
script.
What is the best way to exclude udev-extraconf?
Thanks
Michael
--
_
Hi
It seems to me that gstreamer in yocto daisy does a verbose output per
default. (like gst-launch -v).
Any idea how I can best disable this?
Thanks
Michael
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yo
Am 21.10.2014 um 18:56 schrieb Martin Jansa:
> qt5 isn't special from this perspective (well maybe except that it takes
> damn long to build it all, so it's always useful to narrow the
> problematic module asap and then rebuild only that one as long as
> dependencies on other modules allow), I woul
Hi
I was using qt5 5.3.0-beta1 for a long time. Now I upgraded to 5.3.2,
which is the current master.
Now I am experiencing some video problems. I reverted back to my old
5.3.0-beta 1 and the problems are gone. So, it seems one (or more)
commits between 5.3.0-beta1 and 5.3.2 are the cause of the
Am 18.10.2014 um 23:33 schrieb Tyler Hall:
>>
>> # need to export these variables for python-config to work
>> export BUILD_SYS
>> export HOST_SYS
>> export STAGING_INCDIR
>> export STAGING_LIBDIR
>
Tested and this works, when added to my pyotherside recipe.
It is indeed not very intuitive, but
Am 18.10.2014 um 11:10 schrieb Martin Jansa:
> On Sat, Oct 18, 2014 at 10:51:30AM +0200, Neuer User wrote:
>>> http://git.openembedded.org/openembedded-core/commit/?h=daisy&id=de5797b27a358954eb15318d0d77ad1981981861
THANKS A LOT!!!
This is it. This patch broke the recipe. I re
Am 18.10.2014 um 11:10 schrieb Martin Jansa:
> On Sat, Oct 18, 2014 at 10:51:30AM +0200, Neuer User wrote:
>> Btw. do you know that the qt5 repo is currently incompatible with daisy?
>> There is a patch in fsl-arm that cannot be applied:
>>
>> ./meta-fsl-arm/qt5-layer/r
Am 18.10.2014 um 10:44 schrieb Martin Jansa:
> On Sat, Oct 18, 2014 at 09:11:51AM +0200, Neuer User wrote:
>> I don't see any chance to get this running. The whole environment seems
>> to be missing, such as BUILD_SYS, HOST_SYS, STAGING_LIB_DIR and other.
>>
>> I w
I don't see any chance to get this running. The whole environment seems
to be missing, such as BUILD_SYS, HOST_SYS, STAGING_LIB_DIR and other.
I will now completely resetup yocto from scratch, hoping that this fixes
the problem. Will report tomorrow or as soon as I have a result.
--
Hmm, going deeper into the configure error I found the following:
File
/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py
contains in line 19:
PREFIX = os.path.normpath(sys.prefix).replace( os.getenv("BUILD_SYS"),
os.getenv("HOST_SYS") )
This gives error
T
herside: md5 checksum matched for
file:///home/ubuntu/yocto/sources/poky/meta/files/common-licenses/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302
DEBUG: Python function do_qa_configure finished
DEBUG: Executing shell function qmake5_base_postconfigure
DEBUG: Shell function qmake5_base_postconfig
Am 17.10.2014 um 16:51 schrieb Paul Eggleton:
> Hi there,
>
> I agree this sort of thing shouldn't happen on a stable branch. I'm not sure
> what would have caused such a problem though. However, above you are looking
> under tmp/work, but the file being present under there doesn't really say
>
Hi
Because of shellshock I decided to update my daisy repo to latest
revision (old version was from about June).
Everybody know: "NEVER EVER CHANGE A RUNNING SYSTEM" :-)
Well, I needed to because of shellshock. And now I need to try to repair
everything that broke (currently at 7 packages).
One
Am 11.10.2014 um 18:52 schrieb Albert K:
> Dear all,
>
> May I know if anyone has a BSP for PCEngines APU1c ? Thanks.
>
> Regards.
>
Probably ask Pascal Dornier from PC engines directly. Although, he
mostly only focuses on the hardware, but he might at least know...
--
_
cubox-i_3.10.30.inc
└── linux-cubox-i_3.10.30-linux4kix.bb
Am 06.06.2014 17:12, schrieb Gary Thomas:
> On 2014-06-06 08:56, Neuer User wrote:
>> Hi Bruce
>>
>> Thanks for the hint. I changed it, but the result is the same.
>>
>> Strange is really that it shows the dire
Ashfield:
> On 14-06-06 07:16 AM, Neuer User wrote:
>> I get the following error:
>>
>> WARNING: Failed to fetch URL file://defconfig, attempting MIRRORS if
>> available
>> ERROR: Fetcher failure: Unable to find file file://defconfig anywhere.
>> The paths tha
Am 06.06.2014 14:31, schrieb Burton, Ross:
> On 6 June 2014 12:08, Neuer User wrote:
>>> The postinst is executed by the package manager when the package is
>>> installed. If that installation takes place during do_rootfs, ${D}
>>> will refer to the rootfs directory
Am 06.06.2014 13:19, schrieb Jacob Kroon:
> I'm not sure if this helps, but you can specify rootfs-post-process
> commands in your image recipe:
>
> setup_my_image() {
> # do stuff
> }
>
> ROOTFS_POSTPROCESS_COMMAND += 'setup_my_image ;'
>
> This will run after the rootfs is created from the
I get the following error:
WARNING: Failed to fetch URL file://defconfig, attempting MIRRORS if
available
ERROR: Fetcher failure: Unable to find file file://defconfig anywhere.
The paths that were searched were:
/home/ubuntu/yocto/sources/meta-omnisonix/recipes-kernel/linux/linux-cubox-i-3.10.30/
Am 06.06.2014 12:54, schrieb Paul Barker:
> I usually leave things more than a day before sending a ping email,
> people can be busy but usually you'll get replies within a couple of
> days on this list.
>
Sorry, I guess these 18h were driving me crazy as I don't understand why
it is not working.
Nobody using any postinstalls?
I am still wondering why the postinstall does not work. I don't get any
error messages. The files are just not installed.
Am 05.06.2014 12:44, schrieb Neuer User:
> Hi
>
> I am desperately trying to get some postinstall scripts working. They
> sh
Hi
I am desperately trying to get some postinstall scripts working. They
should replace some defualt files with custom files I have. They are all
in one package. The package looks like this:
do_install() {
install -d ${D}${sbindir}
install -m 0700 ${S}/sbin/* ${D}${sbindir}
install -
Am 04.06.2014 11:59, schrieb Paul Eggleton:
> On Wednesday 04 June 2014 11:24:36 Neuer User wrote:
>> I searched through other recipes for "EXTRA_OECONF_" and found somehting
>> that worked:
>>
>> EXTRA_OECONF_append_mx6 = "--enable-imx6"
>
>
I searched through other recipes for "EXTRA_OECONF_" and found somehting
that worked:
EXTRA_OECONF_append_mx6 = "--enable-imx6"
Main difference is the mx6 versus imx6.
Thanks a lot
Michael
Am 04.06.2014 11:21, schrieb Neuer User:
> The problem is that the MACHINE varia
The problem is that the MACHINE variable is "cubox-i", which is based on
imx6.
Guess that should still work somehow, though...
Am 04.06.2014 11:13, schrieb Neuer User:
> Hmm, like this?
>
> -
> SUMMARY = "USB CEC Adaptor communication Li
onfigured features:
Pulse-Eight CEC Adapter : yes
Pulse-Eight CEC Adapter detection : yes
Raspberry Pi support :no
TDA995x support : no
i.MX6 support : no
...
What am I missing?
Michael
Am 04.06.2014 10:59, schrieb Burton, R
Hi
I have a simple recipe (libcec) that I would like to add an additional
configure option to, depending if the machine is an imx6 based one.
How would I do that best?
Here is the recipe:
-
SUMMARY = "USB CEC Adaptor communication Library with patches
Btw, this works beautifully. Thanks a lot!
Michael
Am 21.05.2014 17:02, schrieb Burton, Ross:
> On 21 May 2014 11:49, Auslands-KV wrote:
>> That's it. It does't seem to know where they are. If I add the option
>> with the path, it works.
>>
>> Do I miss something in my local.conf?
>
> No, OpenS
Sorry, please ignore my mail. I seem to have missed a "install -d"
command. Not it builds the image, but I still seem to have some errors I
need to fix.
Thanks nonetheless!
Michael
Am 23.05.2014 16:23, schrieb Neuer User:
> Hello
>
> I build a read-only-image and nee
Hello
I build a read-only-image and need to exchange a few configuration files
before the final image is build. Unfortunately, I ran into this error:
ERROR: The following packages could not be configuredoffline and rootfs
is read-only: xxx
My recipe looks basically as follows:
...
do_install()
chael
Am 21.05.2014 12:27, schrieb Burton, Ross:
> On 21 May 2014 10:37, Neuer User wrote:
>> I really need certificate support in wget. What am I missing? I guess,
>> it is a very stupid error on my side, but I just don't know which.
>
> Try passing --ca-certificate=/
Thanks Paul.
That's it. It does't seem to know where they are. If I add the option
with the path, it works.
Do I miss something in my local.conf?
Cheers
Michael
Am 21.05.2014 12:27, schrieb Burton, Ross:
> On 21 May 2014 10:37, Neuer User wrote:
>> I really need certific
Nobody any idea?
I really need certificate support in wget. What am I missing? I guess,
it is a very stupid error on my side, but I just don't know which.
Michael
Am 19.05.2014 14:02, schrieb Neuer User:
> Am 19.05.2014 12:56, schrieb Paul Barker:
>> On 19 May 2014 10:35, Neu
Am 19.05.2014 12:56, schrieb Paul Barker:
> On 19 May 2014 10:35, Neuer User wrote:
>> Am 19.05.2014 11:32, schrieb Burton, Ross:
>>> On 19 May 2014 10:25, Neuer User wrote:
>>>> I need to use wget with https support in my image. So I added "wget" to
&g
Am 19.05.2014 11:32, schrieb Burton, Ross:
> On 19 May 2014 10:25, Neuer User wrote:
>> I need to use wget with https support in my image. So I added "wget" to
>> my packages.
>>
>> The problem is that it doesn't seem to find the installed certificates:
Hello
I need to use wget with https support in my image. So I added "wget" to
my packages.
The problem is that it doesn't seem to find the installed certificates:
# wget https://www.google.com
--2014-05-19 11:20:42-- https://www.google.com/
Resolving www.google.com... 173.194.113.242, 173.194.1
Hi
I need qt-gstreamer in my Qt5 app (because I am having problems with the
camera element).
I found a yocto recipe from Andrey Telepin and tried to modify it for
Qt5. It looks like this:
---
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
Am 16.05.2014 14:16, schrieb Neuer User:
> Am 16.05.2014 14:04, schrieb Anders Darander:
>
> Great, that helped with no 1.). Still a lot to learn for me.
>
> No 2. is still open, though. Is that a problem of my recipe or rather a
> generic problem of the python3 recipe? I could
Am 16.05.2014 14:04, schrieb Anders Darander:
> * Neuer User [140516 13:24]:
>
>> require recipes-qt/qt5/qt5.inc
>>
>
>
>> It is WIP, so e.g. the license is stil wrong.
>
>>
Hello
I am trying to build a simple recipe for a package called "pyotherside".
It currently looks like this:
SUMMARY = "Python3 bindings for Qt5"
DESCRIPTION = "New framework for including pyhton interpreter into Qt5 apps"
H
Am 15.05.2014 22:43, schrieb Richard Purdie:
> On Wed, 2014-05-14 at 16:42 +0200, Neuer User wrote:
>> Probably solved. It should be
>>
>> include conf/distro/poky.conf
>>
>> instead of
>>
>> include poky.conf.
>>
>> (Stupid newbie error).
&
5, schrieb Neuer User:
> Am 14.05.2014 16:27, schrieb Burton, Ross:
>> On 14 May 2014 15:22, Neuer User wrote:
>>> Then started a bitbake. Got a strange error "LCONF_VERSION is 6, should
>>> be 5 in bblayers.conf". So I changed it to 5.
>>
>> So t
Am 14.05.2014 16:27, schrieb Burton, Ross:
> On 14 May 2014 15:22, Neuer User wrote:
>> Then started a bitbake. Got a strange error "LCONF_VERSION is 6, should
>> be 5 in bblayers.conf". So I changed it to 5.
>
> So that's because the Poky layers are a vers
or "LCONF_VERSION is 6, should
be 5 in bblayers.conf". So I changed it to 5.
Then bitbake works, but it seems to recompile ALL packages?! Is this
correct. (I stopped it as it will take half a day to finish).
Thanks again for your help!
Michael
Am 14.05.2014 16:13, schrieb Burton, Ross:
&
Am 14.05.2014 15:58, schrieb Burton, Ross:
> On 14 May 2014 14:54, Neuer User wrote:
>> to my image.bb file. Guess, this is then the recommended way to go?
>
> Not in your image recipe, no, as then e.g. connman will still think
> that you need 3g and nfc.
>
> Ross
&
Well, no, not a one-time job. So I rather added
DISTRO_FEATURES_remove = " 3g bluetooth irda nfc zeroconf x11 wayland"
to my image.bb file. Guess, this is then the recommended way to go?
Thanks,
Michael
Am 14.05.2014 15:36, schrieb Vaduva alexandru:
>
> Depending on your situation.
> If it is
Hi
I have a small custom image based on the core-image-minimal.
Due to some DISTRO features (3g, nfc, a.o.) I get useless packages
included (ofono, neard). What is the best way to remove them?
Can the distro content be changed? Or would I need to build my own
distro? (Which would be not so easy
Sounds like a good idea.
Am 09.05.2014 21:22, schrieb Burton, Ross:
> On 9 May 2014 16:19, Neuer User wrote:
>> Yes, it does, as long as you need QtMultimedia. Same applies to Qt5.
>> There was a discussion on the Qt mailing list about moving to
>> gstreamer1.0, but this se
s-core/busybox/files/udhcpc-opts.cfg
b/recipes-core/busybox/files/udhcpc-opts.cfg
new file mode 100644
index 000..d02ba19
--- /dev/null
+++ b/recipes-core/busybox/files/udhcpc-opts.cfg
@@ -0,0 +1 @@
+CONFIG_IFUPDOWN_UDHCPC_CMD_OPTIONS="-R -b"
Am 07.05.2014 10:57, schrieb Neuer User:
&
and the system is
again without ip.
Found this on the internet:
https://www.mail-archive.com/connman@connman.net/msg15637.html
Am 09.05.2014 20:37, schrieb Burton, Ross:
> On 9 May 2014 17:57, Neuer User wrote:
>> Seems, I am not the only one wondering why connman phones home:
>
&g
xplanation why this package adds this
route, I wouldn't use this package on my systems.
Am 09.05.2014 18:51, schrieb Neuer User:
> Hi Andrea
>
> I'd like the idea of a somewhat smarter network daemon, but connman
> slowly becomes a bit suspicious to me.
>
> First, it i
s providing the correct
> d-bus permissions for interacting with connman to processes which run
> under a GUI session (non-root). IMHO this RDEPEND should be somewhat
> conditional to X being enabled on your distro/image. I couldn't find
> any explicit reference to xuser in connman source c
Great, then I will remove it.
My app does not run as root, but all system configuration tasks are only
available for root on my system.
Am 09.05.2014 17:22, schrieb Burton, Ross:
> On 9 May 2014 16:15, Neuer User wrote:
>> Do you by chance know, why it depends on the xuser-account p
Am 08.05.2014 17:54, schrieb Burton, Ross:
> On 8 May 2014 15:48, Burton, Ross wrote:
>> For the 1.7 release I want to move GStreamer 0.10 from oe-core into
>> meta-multimedia, and ensure everything in oe-core has ported to
>> GStreamer 1.x. GStreamer 0.10 is considered dead upstream and is
>> un
t any additional user accounts on my system. If it is not
essential I would remove it.
Thanks
Michael
Am 09.05.2014 15:06, schrieb Andrea Galbusera:
> Hi,
>
> On Fri, May 9, 2014 at 12:28 PM, Neuer User wrote:
>> Connman is really a problem without documentation. :-(
>>
>
#x27;t find a config file for connman. Is there one?
Thanks
Michael
Am 08.05.2014 12:27, schrieb Burton, Ross:
> On 8 May 2014 04:58, Neuer User wrote:
>> I had a brief look at connman half a year ago, but that time I was
>> unable to find a good documentation about it. Do you h
I had a brief look at connman half a year ago, but that time I was
unable to find a good documentation about it. Do you have by chance a
link to some tutorial or at least man entry for the configuration?
Am 07.05.2014 12:24, schrieb Burton, Ross:
> On 7 May 2014 09:57, Neuer User wrote:
>
Am 07.05.2014 11:27, schrieb Søren Holm:
> Use ifplugd recipe I just submitted.
>
Very nice idea. Where do I find the recipe?
> Onsdag den 7. maj 2014 10:57:22 skrev Neuer User:
>> Hi
>>
>> I encounter a problem with the DHCP network setup during boot:
>>
>&
Hi
I encounter a problem with the DHCP network setup during boot:
System starts. During start ifup is called. ifup calls udhcpc. Network
is, however, not yet up! udhcpc exits with failure. Then network is up.
But, of course, no connection, because no IP address.
In earlier times I used debian ba
That's great! And just one line to add. Perfect solution!
Thanks a lot!
Michael
Am 02.05.2014 19:24, schrieb Bruce Ashfield:
> On 14-05-01 01:12 PM, Bruce Ashfield wrote:
>> On 14-05-01 02:32 AM, Neuer User wrote:
>>> Hi Bruce
>>>
>>> Here is the er
Am 02.05.2014 08:43, schrieb Khem Raj:
> On Thu, May 1, 2014 at 11:06 PM, Neuer User wrote:
>> Before I copied the whole conf dir back from a backup. This time I tried
>> with a completely new conf dir. I did that and strangely got another
>> error message by "sani
n a future yocto revision.
Cheers
Michael
Am 01.05.2014 12:19, schrieb Neuer User:
> Hi
>
> I needed to re-setup my yocto directory due to a fs error (was using
> btrfs). Before I used master-next. Now I checked out daisy.
>
> When I start bitbaking, I already get an error [&qu
Hi
I needed to re-setup my yocto directory due to a fs error (was using
btrfs). Before I used master-next. Now I checked out daisy.
When I start bitbaking, I already get an error ["File not found"] when
building quilt-native. The error is in the step do_populate_sysroot. The
problem is pretty cle
Hi Bruce
Here is the error messega, I get after a "bitbake linux-cubox-i -c
cleansstate; bitbake linux-cubox-i" using the recipe you posted:
ERROR: Function failed: do_patch (log file is located at
/home/ubuntu/yocto/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/temp/log.do_pa
Am 30.04.2014 21:21, schrieb Bruce Ashfield:
>
> Hrm. I have all the key layers right, which leaves me with the expansion
> issue. The README indicates the danny branch for the meta-fsl-* layers,
> is that what you are using ?
>
> Bruce
>
No, I'm using master-next. Only in master-next you can fi
Am 30.04.2014 20:44, schrieb Bruce Ashfield:
> Can you send me your bblayers out of band ? I'm using meta-fsl-arm
> and meta-fsl-arm-extra to get a build going, and running into
> expansion errors in the kernel recipes. Rather than hunt around
> more than necessary, I'll check against your layers.
Hi Bruce
Have you got any further?
I currently use a "defconfig" replacement, but honestly, it feels very
dumb. Fragments seem to be much smarter to combine and test different
configurations.
Cheers
Michael
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
> On 14-04-28 09:35 AM, Neu
Thanks for the hint. I will try this today.
Cheers
Michael
Am 30.04.2014 11:26, schrieb Paul Eggleton:
> Hi Michael,
>
> On Monday 28 April 2014 17:11:36 Neuer User wrote:
>> I want to include the package sox_14.4.0.bb in my distro. Should be
>> straight forward, I tho
Hi
I want to include the package sox_14.4.0.bb in my distro. Should be
straight forward, I thought. But I am having problems as the package
always wants GL as a requirement, which my distro does not have (without X).
the sox recipe looks like this:
DESCRIPTION="SoX is the Swiss Army knife of sou
Am 28.04.2014 15:37, schrieb Bruce Ashfield:
>
> If you send me pointers to your bblayers and local.conf settings, I'll
> run a build to see what happens here as well.
>
> I'm always interested in tracking these down regardless.
>
> Bruce
>
Testing this should be pretty straightforward, if see
Am 28.04.2014 15:16, schrieb Bruce Ashfield:
> It all depends on how adventurous you are today :) Using a defconfig
> will work, and you can generate one without much trouble. Using
> fragments will allow you to keep your changes separate from the
> baseline configuration, but you'll need to tweak
Am 28.04.2014 15:03, schrieb Bruce Ashfield:
>
> The answer to your question depends on the base linux-cubox-i
> recipe.
>
> Config fragment support works for kernels that inherit from linux-yocto,
> versus ones that inherit directly from kernel.bbclass. So if you
> pop open that base recipe, and
Hello
I am trying to add a custom kernel config to my layer. I followed the
following guide:
http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#creating-config-fragments
I have the following files in my layer:
recipes-kernel/linux/linux-cubox-i_3.0.35.bbappend:
FILESEXTRAPATHS_prep
Got it working!
The hint with the "devshell" helped very much. I could try out
"pkg-config --list-all|grep rtsp" and found the name pkg-config was
expecting.
So, the line must be:
pkg-config --cflags --libs gstreamer-0.10 gst-rtsp-server-0.10
(Thought I had tried this, but maybe had a typo in t
ery simple to do, but for a Newbie like
me... :-)
Am 22.04.2014 16:32, schrieb Robert Calhoun:
>
>
> On 4/22/14 3:57 AM, "Neuer User"
> wrote:
>> Sorry for this simple question. I've just started building my
>> first image with yocto and would now like to add a (ve
Am 22.04.2014 10:42, schrieb Richard Purdie:
>
> Basically, you need to pass in the correct compiler and linker flags.
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/chapter-developing.html
>
> Adding:
>
> `pkg-config --cflags --libs gstreamer`
>
> to your compiler line
Hi
Sorry for this simple question. I've just started building my first
image with yocto and would now like to add a (very simple) own recipe.
I followed the Yocto Development guide, added my own layer and included
the "helloworld" example.
Now I would like to exchange the helloworld.c code with
79 matches
Mail list logo
