On Tue, 17 Jan 2017 08:51:10 +0100
Andreas Müller wrote:
> On Tue, Jan 17, 2017 at 1:12 AM, Trevor Woerner wrote:
> > Hi Paul,
> >
> > On Thu 2017-01-05 @ 09:59:16 PM, Paul Barker wrote:
> >> Also, are you thinking of moving the -rt recipe to the 4.9 series when
> >> upstream linux-raspberrypi d
Hi
when I want to change gcc version to 4.9.3.
I just change gcc & libgcc,but gcc-truntime still 5.3.
Is there a rapid method to change everything I need?
Regards
Richard
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproje
On 2017-01-17 11:41, Richard Zhang wrote:
Hi
when I want to change gcc version to 4.9.3.
I just change gcc & libgcc,but gcc-truntime still 5.3.
Is there a rapid method to change everything I need?
Of course you'll need the correct recipes, but just add these
lines to local.conf:
GCCVER
On 11 January 2017 at 20:55, Rick Altherr wrote:
> KERNEL_IMAGETYPE only provides the first image type specified in
> KERNEL_IMAGETYPES which can provide surprising results. Since this
> class is solely for FIT images, just hardcode the names to fitImage-*.
>
Nathan sent the identical patch ear
Hi,
A client would like to dish out an SDK to their customers, but only with
a subset of header files compared to those they use internally.
internal SDK:
As it is right now when you build an sdk with e.g. bitbake whatever -c
populate_sdk
external SDK:
everything the same as above, but for
From: André Draszik
The shell script uses time, which is either a bash built-in, or
a GNU utility. Not all build machines will have either bash or
GNU time available out of the box. Make sure it is available.
Note that this needs the patch to OE-core to enable the
time-native BBCLASSEXTEND to be
Current Dev Position: YP 2.3 M2
Next Deadline: YP 2.3 M2 by Jan 23, 2017
SWAT team rotation: Armin -> Saul on Jan. 13, 2017.
SWAT team rotation: Saul -> Paul on Jan. 20, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
·The 2.2.1 release has
On Tue, 2017-01-17 at 15:59 +, André Draszik wrote:
> The shell script uses time, which is either a bash built-in, or
> a GNU utility. Not all build machines will have either bash or
> GNU time available out of the box. Make sure it is available.
Good catch. I'm just wondering whether it would
On Tue, 2017-01-17 at 17:42 +0100, Patrick Ohly wrote:
> On Tue, 2017-01-17 at 15:59 +, André Draszik wrote:
> > The shell script uses time, which is either a bash built-in, or
> > a GNU utility. Not all build machines will have either bash or
> > GNU time available out of the box. Make sure it
Hi all,
As some of you are aware some of my colleagues and I have been working on
improving how incoming patches are handled - initially for OE-Core but we hope
to arrive at something that will be useful for other layers as well. The aim
was to do so without adversely affecting existing workflo
Paul,
That is some impressive work by the team! Thank you all for the hard work and
bringing the plan to fruition - I'm sure this framework will benefit our
entire Community and will improve and streamline the workflow!
--
Denys
On Wed, Jan 18, 2017 at 07:05:58AM +1300, Paul Eggleton wrote:
Layers that aren't published shouldn't be visible via the API. (We don't
need to apply that filter to recipes, machines or distros though since a
layer's content won't automatically be indexed unless it has been
published).
Signed-off-by: Paul Eggleton
---
layerindex/restviews.py | 8
1
On Fri, 13 Jan 2017 11:02:20 Andreas Müller wrote:
> On Fri, Jan 13, 2017 at 9:55 AM, Paul Eggleton
> wrote:
> > On Fri, 13 Jan 2017 08:56:47 Andreas Müller wrote:
> >> again me... sorry but I use index regularly to check if somebody else
> >> already created a recipe I am interested in.
> >>
> >
On Tue, Jan 17, 2017 at 11:21 PM, Paul Eggleton
wrote:
> On Fri, 13 Jan 2017 11:02:20 Andreas Müller wrote:
>> On Fri, Jan 13, 2017 at 9:55 AM, Paul Eggleton
>> wrote:
>> > On Fri, 13 Jan 2017 08:56:47 Andreas Müller wrote:
>> >> again me... sorry but I use index regularly to check if somebody el
external SDK:
everything the same as above, but for some packages there should be
only libraries - no header files.
Is there a reason why you want the libraries without the headers? It
doesn't seem particularly useful to be able to link a program against a
library, but not have the header to
Hi Gary,
I believe that we will see for 4.9 the same issues we had with 4.8, heavy
rebasing from the downstream.
I'm currently working with the upstream - plus patches - and I plan to have
a yocto build that would take the upstream source and add some patches,
instead of taking the downstream as a
Hi Gary,
You get this because the patch to the latest 4.7 version have not been
merged...
4.7 has been stable for some time now, unlike 4.8 - and 4.9 will probably
have some similar issues, basically the downstream is heavily rebasing, so
revisions numbers are not reliable anymore.
I'm OK to remo
Hi,
On 2017-01-18 04:54, Joshua Watt wrote:
external SDK:
everything the same as above, but for some packages there should be
only libraries - no header files.
Is there a reason why you want the libraries without the headers? It
doesn't seem particularly useful to be able to link a program ag
I'm trying to track down some recent changes in the X server
(using the latest Poky/Yocto master). I've had failures on
a number of the embedded targets I work with, so I thought
I'd give it a go on platforms with a larger base - x86 machines.
It used to be that I could run qemu and it would pop
19 matches
Mail list logo
