> > > I know I can fix this by simply doing a menuconfig, but that
> > > isn't
> > > the
> > > proper way to do it - I have multiple BSP layers that do the same
> > > thing
> > > and they all behave in the same way.
> > >
> > > What am I doing wrong? I've attached my layer that contains the
> > >
On Mon, 2017-10-02 at 10:54 -0400, Bruce Ashfield wrote:
> On 09/30/2017 11:22 PM, Jonathan Haws wrote:
> >
> > All,
> >
> > I've created a bbappend that appends to the linux-yocto-rt recipe
> > to
> > simply apply configuration fragments. I
> I'm trying to build an image for an Rpi3 and am having some difficulty.
>
> I've created and posted a meta-batman layer to bring the latest BATMAN
> Advanced module and userspace tools to Yocto. I haven't had any
> troubles getting this layer to work with other architectures, but am
> having tro
I'm trying to build an image for an Rpi3 and am having some difficulty.
I've created and posted a meta-batman layer to bring the latest BATMAN
Advanced module and userspace tools to Yocto. I haven't had any
troubles getting this layer to work with other architectures, but am
having troubles wi
>> I guess we don't cover that explicitly, other than in the reference manual
>> entries for each variable. We probably need a small section on dependencies
>> in the "Writing a new Recipe" section:
>>
>>
>> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-rec
>> ipe-writing
> 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.
Ross, thanks for clearing that up. Is there anything in the
> 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?
>
Oh geez...I feel sheepish!
Attached is my updated batctl recipe - still giving the same errors.
ERROR: oe_runmake failed
ERROR:
I'm working on a recipe for batman-adv, which depends on libnl at build
time.
I've attached my recipe for batman-adv. It's pretty straightforward,
but the DEPENDS variable doesn't seem to work when I build
core-image-full-cmdline. If I clean both libnl and batman-adv, then
bitbake batman-adv
Got it figured out. Turns out I needed some more changes to the
Makefile. New patch attached in case anyone is interested.
Bottom line is that the CC command was getting forcibly set at some
point to check compilers, thus overriding the shell setting. Plus it
needed a modules_install as well
- Original message
From: Chris Trobridge
Date: 2016/01/30 5:13 AM (GMT-07:00)
To: Jonathan Haws , yocto@yoctoproject.org
Subject: RE: [yocto] Compiling different version of IGB as a kernel module
Hi Jon,
As an alternative, have you considered patching the igb source that already
exists wi
Hello all!
I am trying to get the Intel IGB driver compiling as a kernel module
using source downloaded from SF. I'm doing this because I was given a
patch to enable an external PPS to provide a time source to the PTP
mechanisms in the device.
I've got the recipe setup and it makes it to the
I am trying to get iSCSI support into my Yocto build, however I am finding that
it is not going very well...
I have my kernel configured with all the necessary options (I think...):
iSCSI Boot Firmware Table Attributes module (SCSI_ISCSI_ATTRS)
Linux-iSCSI.org iSCSI Target Mode Stack (ISCSI_TARG
>It's still valid for me, I'm still using this
>https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626
H. I did a fresh download of the Yocto repos last week and that is not
what I have. My file still has the HOSTLDFLAGS variable set.
___
Thanks for the help. I used the solution from the following thread to take
care of it:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html
Are there others having this issue? If so, is it something that should be
pushed upstream?
Thanks!
___
>Try:
>
>OE_TERMINAL = "xterm"
>
>in your local.conf
I get the exact same thing, just in xterm instead of konsole.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
When I run 'bitbake linux-yocto -c menuconfig' I was not getting a menuconfig -
I had to tell my local.conf to use screen because auto was selecting a gnome
terminal which would resize itself to something too small and menuconfig would
exit with an error.
Now I can get menuconfig and make chang
ct.org [yocto-boun...@yoctoproject.org] on
> behalf of Jonathan Haws [jonathan.h...@sdl.usu.edu]
> Sent: Tuesday, October 16, 2012 9:32 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] .bashrc not being used by root account
>
> I have modified the .bashrc file for the system, ho
(as a mountpoint for a secondary disk). How is that
typically done?
Thanks!
Jonathan
____
From: Marc Ferland [marc.ferl...@gmail.com] on behalf of Marc Ferland
[ferla...@sonatest.com]
Sent: Tuesday, October 16, 2012 12:27
To: Jonathan Haws
Cc: yocto@yoctoproject.org
__
From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] on behalf
of Marc Ferland [ferla...@sonatest.com]
Sent: Tuesday, October 16, 2012 11:37
To: yocto@yoctoproject.org
Subject: Re: [yocto] lm-sensors not available as a package?
Paul Eggleton writes
I have modified the .bashrc file for the system, however the root account does
not seem to use it by default. What am I missing? I would rather not have to
source the .bashrc file every time I login as root.
Thanks,
Jonathan
___
yocto mailing list
y
I would be surprised if a recipe for lm-sensors has not already been created,
however I cannot find one. Can someone point me in the right direction?
All I can find is a sysstat package that I can include via
IMAGE_INSTALL_append, however I cannot see how I can get the same information
out of
On Fri, 2012-10-12 at 21:42 +, Jonathan Haws wrote:
> What I am trying to do is have Poky build me an image that I can just
> 'dd' to a SSD and hook up to the system to boot. Since that image
> will also only be only ~250MB or so, I would like to have Poky
> genera
g else and just (somewhat) follows a manual.
Thanks,
Jonathan
From: rstr...@linuxfoundation.org [rstr...@linuxfoundation.org] on behalf of
Rudolf Streif [rudolf.str...@linux.com]
Sent: Friday, October 12, 2012 16:13
To: Jonathan Haws
Cc: yocto@yoctoproject.org
S
What I am trying to do is have Poky build me an image that I can just 'dd' to a
SSD and hook up to the system to boot. Since that image will also only be only
~250MB or so, I would like to have Poky generate an image containing multiple
partitions - a small one containing the boot files, then t
I am probably going about this the wrong way, but I am trying to create a new
BSP for an Intel Core2 Duo PC104 board (from ADL-USA, the ADLGS45 to be exact).
I have the BSP and everything working (or so it appears) and I have checked
the kernel configuration. So far I have not had any issues -
25 matches
Mail list logo
