Attendees:
AlexG, Björn, MichaelH, MatthewW, Saul, BruceA, Denys, Nitin, DaveST, PaulE,
JeffP, Belen, Richard, Beth, Darren, Jessica, Song
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.4.2 release - 10 min (Paul/AlexG)
- QA report is just out. Things looking pretty good. Only issue we fo
All,
We've delayed generating M4.rc1 until tomorrow AM so that we can get
things a bit more stabilized. We're running a master build right now
to see where we are. I'll let folks know when we get the rc running.
Thanks
--
Elizabeth Flanagan
Yocto Project
Build and Release
__
Hi,
I wants to build the recipes name linphone(SIP-based IP phone) with
poky-9.0.0 build environment.
I found he linphone recipes under the "angstrom-openembedded". In my poky build
environment I have created the new layer, name linphone, and copy the .bb files.
But when i am building it thr
> From: Gary Thomas
>
> As far as I understand, the 'do_rootfs' step in building an
> image is basically
> equivalent to running "${PKG_MGR} install
> ", where PKG_MGR
> is your package management method of choice - ipk or rpm.
> This seems to me to
> be a very single-threaded process.
If the
On 2013-08-27 16:27, Paul D. DeRocco wrote:
I got really tired of waiting for builds on my lowly dual-core Atom
machine, so I went out and bought a nice fast machine with an i7-4770K and
a Samsung SSD. Full builds are now screechingly fast, over 10x compared to
the Atom.
But when making a tiny c
Hi,
I need mgetty and don't see it anywhere in any of the OE core based
layers. Did something replace it? I'm trying to migrate some OE classic
work to OE core based distros.
Regards,
Brian
___
yocto mailing list
yocto@yoctoproject.org
https://lists.
I got really tired of waiting for builds on my lowly dual-core Atom
machine, so I went out and bought a nice fast machine with an i7-4770K and
a Samsung SSD. Full builds are now screechingly fast, over 10x compared to
the Atom.
But when making a tiny change, I still have to wait for do_rootfs. Sin
[YOCTO #3867]
Five additional patches which cause the --os flag to be accepted and observed
are added. An additional distro, Yocto, is added. The individual patches
are described below.
upgrade_options_processing.patch: Changes setOptions procedure so that it
accepts named parameters for greater
[YOCTO #3867]
bastille -l now reports existing configuration file paths even if it has
not previously been run. Previously, it exited with an error if it detected
an absence of log files indicating a previous run.
Signed-off-by: mulhern
---
recipes-security/bastille/bastille_3.2.1.bb|
[YOCTO #3867]
Adds four additional small patches which address miscellaneous small problems
in Bastille.
The four patches are:
fix_missing_use_directives.patch: A number of use directives were missing from
several files. These were added as discovered.
fix_number_of_modules.patch: The curses in
The README file is updated to indicate the functionality of Bastille that is
actually available.
The recipe file is updated with a pointer to the README file.
An additional patch is added so that when Bastille is run in interactive mode
it will not attempt to make any changes to the system. This
[YOCTO #3867]
Renames existing patches and removes some changes.
Curses-and-IOLoader-changes.patch is renamed to call_output_config.patch. The
new patch omits the removal of the pruning step in Load_Questions but
retains the replacement of a call to a non-existant function with a call
to an appro
The python script, set_required_questions.py reads the list of questions and
answers from the config file and edits the REQUIRE_DISTRO field for those
questions in the questions file so that it includes "Yocto" if it is not
already present. This has the effect of causing Bastille, when loading
ques
The patches in this set consist of a number of actual bug fixes and a few
enhancements. The two enhancements are:
1) A change in the semantics of the -l flag so that it lists configuration
files even if Bastille has not been run previously.
2) A change in the distributions are inferred, specified,
On 8/27/2013 5:42 AM, Bruce Ashfield wrote:
On Tue, Aug 27, 2013 at 4:33 AM, Paul Eggleton
wrote:
On Tuesday 27 August 2013 09:32:24 David Nyström wrote:
On Mon 26 Aug 2013 11:27:30 PM CEST, Yang Shi wrote:
Add recipe for 1.0.6 version. And, add status and reload commands into
init script.
S
On Aug 26, 2013, at 5:23 AM, Javi Roman wrote:
> $ cat recipes-devtools/libtool/libtool-cross_2.4.2.bbappend
> export FC = "${CCACHE}${HOST_PREFIX}gfortran ${HOST_CC_ARCH}
> --sysroot=${STAGING_DIR_HOST}"
can you submit this as a patch to OE-Core libtool recipe please ?
On Tue, 2013-08-27 at 08:28 -0700, Darren Hart wrote:
> Update the manuals to reflect the recent replacement of atom-pc with
> genericx86.
>
> Signed-off-by: Darren Hart
> Cc: Ross Burton
> Cc: Paul Eggleton
> Cc: Scott Rifenbark
> Signed-off-by: Darren Hart
Arg, sorry for the dupe S O B, Sc
Update the manuals to reflect the recent replacement of atom-pc with
genericx86.
Signed-off-by: Darren Hart
Cc: Ross Burton
Cc: Paul Eggleton
Cc: Scott Rifenbark
Signed-off-by: Darren Hart
---
documentation/dev-manual/dev-manual-model.xml | 2 +-
documentation/ref-manual/ref-var
I'm trying to figure out the syntax for specifying more than one URI in a
single PREMIRROR statement, e.g.
PREMIRRORS_append = "git://.*/.* file://toplevel/premirror
ftp://ftp.acme.com/pre_mirror/foo \n"
So for all "git" fetches I want it to *first* look in a local premirror
directory and if the
On Tue, 2013-08-27 at 12:11 +0100, Paul Eggleton wrote:
> Hi Darren,
>
> On Friday 23 August 2013 20:52:41 Darren Hart wrote:
> > On Tue, 2013-08-13 at 12:00 +0100, Paul Eggleton wrote:
> > > Automated testing on real hardware is something that a lot of us do
> > > already, but the likelihood is t
On Tue, Aug 27, 2013 at 4:33 AM, Paul Eggleton
wrote:
> On Tuesday 27 August 2013 09:32:24 David Nyström wrote:
>> On Mon 26 Aug 2013 11:27:30 PM CEST, Yang Shi wrote:
>> > Add recipe for 1.0.6 version. And, add status and reload commands into
>> > init script.
>> >
>> > Signed-off-by: Yang Shi
>
Hi Darren,
On Friday 23 August 2013 20:52:41 Darren Hart wrote:
> On Tue, 2013-08-13 at 12:00 +0100, Paul Eggleton wrote:
> > Automated testing on real hardware is something that a lot of us do
> > already, but the likelihood is that we've all been coming up with our own
> > solutions for this, so
ELSBSTRING = "SUSE-LINUX-11"
>> TARGET_SYS= "arm-poky-linux-gnueabi"
>> MACHINE = "zynq-zc706"
>> DISTRO= "poky-chris"
>> DISTRO_VERSION= "1.4+snapshot-20130827"
>> TUNE_FEATURES = &qu
= "x86_64-linux"
NATIVELSBSTRING = "SUSE-LINUX-11"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE = "zynq-zc706"
DISTRO = "poky-chris"
DISTRO_VERSION= "1.4+snapshot-20130827"
TUNE_F
quot;SUSE-LINUX-11"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE = "zynq-zc706"
DISTRO = "poky-chris"
DISTRO_VERSION= "1.4+snapshot-20130827"
TUNE_FEATURES = "armv7a vfp cortexa9"
TARGET_FPU= "v
On Tuesday 27 August 2013 09:32:24 David Nyström wrote:
> On Mon 26 Aug 2013 11:27:30 PM CEST, Yang Shi wrote:
> > Add recipe for 1.0.6 version. And, add status and reload commands into
> > init script.
> >
> > Signed-off-by: Yang Shi
> > ---
> >
> > ...irqbalance-Add-status-and-reload-command
On Mon 26 Aug 2013 11:27:30 PM CEST, Yang Shi wrote:
Add recipe for 1.0.6 version. And, add status and reload commands into
init script.
Signed-off-by: Yang Shi
---
...irqbalance-Add-status-and-reload-commands.patch | 55
recipes-extended/irqbalance/irqbalance_1.0.6.b
27 matches
Mail list logo
