Re: [yocto] how does one use a prebuilt toolchain from the toolchain/ directory?

[Robert P. J. Day]

On Mon, 2 Jul 2012, Zhang, Jessica wrote:

> On Tue, Jun 26, 2012 at 4:51 AM, Robert P. J. Day  
> wrote:

... snip ...

> > 4) once i install a toolchain, how do i use it?  say i install the arm
> > toolchain, and want to build a beagleboard image.  at what point do i
> > source the arm toolchain environment setup file?  is that all it
> > takes?  will the bitbake build process automatically recognize what
> > i've done and use that toolchain?
>
> [JZ] Please note this toolchain is meant to be used by application
> developers not image builders.  This toolchain is meant for cross
> development that allows you to develop target application on your
> host machines.  Once you source the environment-setup script, it'll
> setup your path correctly that makes it able to find all the cross
> development tools, e.g.
> /opt/poky/1.2/sysroots/i686-pokysdk-linux/usr/bin/i586-poky-linux/i586-poky-linux-gcc
> will be used for compiling your programs.

  ah, i wasn't aware that the prebuilt toolchains were meant primarily
for *app* development, not *image* development.  i already knew how to
use them for app development, that's fairly straightforward.

  which brings me back to my original curiosity -- how can i use the
same toolchain across a number of different *image* builds?  under
what circumstances does that make sense, and how would i do that?

  say i want to configure and build images for a number of
beagleboards, and a beaglebone, and a pandaboard, etc., all of which
require an ARM toolchain.  if these builds can share the same
toolchain, how can i build it once, then not have to build it over and
over for the remaining builds?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how does one use a prebuilt toolchain from the toolchain/ directory?

[Gary Thomas]

On 2012-07-03 03:51, Robert P. J. Day wrote:

On Mon, 2 Jul 2012, Zhang, Jessica wrote:


On Tue, Jun 26, 2012 at 4:51 AM, Robert P. J. Day  wrote:


... snip ...


4) once i install a toolchain, how do i use it?  say i install the arm
toolchain, and want to build a beagleboard image.  at what point do i
source the arm toolchain environment setup file?  is that all it
takes?  will the bitbake build process automatically recognize what
i've done and use that toolchain?


[JZ] Please note this toolchain is meant to be used by application
developers not image builders.  This toolchain is meant for cross
development that allows you to develop target application on your
host machines.  Once you source the environment-setup script, it'll
setup your path correctly that makes it able to find all the cross
development tools, e.g.
/opt/poky/1.2/sysroots/i686-pokysdk-linux/usr/bin/i586-poky-linux/i586-poky-linux-gcc
will be used for compiling your programs.


   ah, i wasn't aware that the prebuilt toolchains were meant primarily
for *app* development, not *image* development.  i already knew how to
use them for app development, that's fairly straightforward.

   which brings me back to my original curiosity -- how can i use the
same toolchain across a number of different *image* builds?  under
what circumstances does that make sense, and how would i do that?

   say i want to configure and build images for a number of
beagleboards, and a beaglebone, and a pandaboard, etc., all of which
require an ARM toolchain.  if these builds can share the same
toolchain, how can i build it once, then not have to build it over and
over for the remaining builds?


Use SSTATE_MIRRORS to point at the sstate-cache of the first build.
This will let bitbake reuse as much as possible, including the toolchain.

I do exactly as you are proposing above and my builds for the "secondary"
targets can be as little as a couple of minutes (from scratch).

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how does one use a prebuilt toolchain from the toolchain/ directory?

[Robert P. J. Day]

On Tue, 3 Jul 2012, Gary Thomas wrote:

> Use SSTATE_MIRRORS to point at the sstate-cache of the first build.
> This will let bitbake reuse as much as possible, including the toolchain.
>
> I do exactly as you are proposing above and my builds for the "secondary"
> targets can be as little as a couple of minutes (from scratch).

  ah, and once i knew what to look for, a quick google brought me
here:

https://wiki.yoctoproject.org/wiki/Enable_sstate_cache

but that page is not linked to either from the main wiki page or the
FAQ page, which makes it a bit hard to find.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how does one use a prebuilt toolchain from the toolchain/ directory?

[Robert P. J. Day]

On Tue, 3 Jul 2012, Gary Thomas wrote:

> Use SSTATE_MIRRORS to point at the sstate-cache of the first build.
> This will let bitbake reuse as much as possible, including the toolchain.
>
> I do exactly as you are proposing above and my builds for the "secondary"
> targets can be as little as a couple of minutes (from scratch).

  what's strange is that there's a whole yocto wiki page devoted to
build performance issues:

https://wiki.yoctoproject.org/wiki/Build_Performance

which says nothing about this.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Hob question: meta-yocto layer and 'defaultsetup' distro option

[Barros Pena, Belen]

Thanks, Khem.

Just to make sure I understand this correctly: if I don't use the
meta-yocto layer, OE-Core should provide reference distro policies that
allow me to build an image. So I guess the 'defaultsetup' option in Hob is
referring to those OE-Core policies. Shane, Dongxiao: could you confirm if
this is the case?

Thanks!

Belen

On 02/07/2012 17:53, "Khem Raj"  wrote:

>On Mon, Jul 2, 2012 at 9:05 AM, Barros Pena, Belen
> wrote:
>>
>> If I delete the meta-yocto layer, am I supposed to provide the distro to
>> be used via a layer or some other means?
>
>OE-Core has reference distro policies which are enough to generate
>images by just using OE-Core and that is what happens when you drop
>meta-yocto its testing the reference distro setup from OE-Core
>
>

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Hob question: meta-yocto layer and 'defaultsetup' distro option

[Xu, Dongxiao]

> -Original Message-
> From: Barros Pena, Belen
> Sent: Tuesday, July 03, 2012 7:04 PM
> To: Khem Raj; Wang, Shane; Xu, Dongxiao
> Cc: yocto
> Subject: Re: [yocto] Hob question: meta-yocto layer and 'defaultsetup' distro
> option
> 
> Thanks, Khem.
> 
> Just to make sure I understand this correctly: if I don't use the meta-yocto 
> layer,
> OE-Core should provide reference distro policies that allow me to build an
> image. So I guess the 'defaultsetup' option in Hob is referring to those 
> OE-Core
> policies. Shane, Dongxiao: could you confirm if this is the case?

Yes, actually "defaultsetup" will be applied in default for any kind of layer 
settings, including the default OE-Core. The difference is, OE-Core only 
applies "defaultsetup", while for meta-yocto layer, we can add additional 
distro policies (poky, poky-bleeding, etc) to override some of the 
"defaultsetup" settings.

Thanks,
Dongxiao

> 
> Thanks!
> 
> Belen
> 
> On 02/07/2012 17:53, "Khem Raj"  wrote:
> 
> >On Mon, Jul 2, 2012 at 9:05 AM, Barros Pena, Belen
> > wrote:
> >>
> >> If I delete the meta-yocto layer, am I supposed to provide the distro
> >> to be used via a layer or some other means?
> >
> >OE-Core has reference distro policies which are enough to generate
> >images by just using OE-Core and that is what happens when you drop
> >meta-yocto its testing the reference distro setup from OE-Core
> >
> >

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Some questions about the webhob design

[Xu, Dongxiao]

Hi Paul and Jim,

Today Jessica and PRC team had a discussion of the webhob tasks listed in the 
wiki page, and about the "Group" and "Project" concept, we still have some 
questions.

Say user A and user B are privileged users, who have the right to customize 
images, while user C is normal user (Say a TME) and only "building image" is 
allowed.

1) If user A customized an image with certain configurations, and he told user 
C that the environment is ready, and user C can build his demo image there. 
However, before user C starts to build, user B changed some configurations, 
making the final output not the expected version.

2) Another issue may be how to avoid global project changes happened together? 
For example user A and user B change the setting in the same time?

3) If user A changes the global project setting, what's the impact to the user 
B who already kicked off a build based on the original setting?

We are really appreciate if you can help to clarify these questions for us.

Thanks,
Dongxiao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Some questions about the webhob design

[Jim Kosem]

Hi,


   1. Paul and I had talked about the last one doing something wins. So if
   I am selecting Package Groups or Recipes and someone selects another
   recipe, this would be updated in my interface as well with an indication
   that it has been updated. However, the final build would reflect both
   selections.
   2. Again, for now, and this could be changed in the future when we have
   users and real use cases, the last person to change something has their
   change.
   3. User A would have his settings impact User B's build.

Again, our thinking is that this is the first version of WebHob and there
is still work to be done on permissions and groups. However, we need to at
this stage keep things simple and then once in testing, we can see how
people may or may not work over one another.

--
Jim Kosem

Skype: jkosem
Gtalk: j...@halfman.com
Mobile: +44 7757 559081

Note: I read and reply to email only a couple of times a day. If you need
something quicker, please use Skype, GTalk or if its urgent call my mobile.



On 3 July 2012 13:10, Xu, Dongxiao  wrote:

> Hi Paul and Jim,
>
> Today Jessica and PRC team had a discussion of the webhob tasks listed in
> the wiki page, and about the "Group" and "Project" concept, we still have
> some questions.
>
> Say user A and user B are privileged users, who have the right to
> customize images, while user C is normal user (Say a TME) and only
> "building image" is allowed.
>
> 1) If user A customized an image with certain configurations, and he told
> user C that the environment is ready, and user C can build his demo image
> there. However, before user C starts to build, user B changed some
> configurations, making the final output not the expected version.
>
> 2) Another issue may be how to avoid global project changes happened
> together? For example user A and user B change the setting in the same time?
>
> 3) If user A changes the global project setting, what's the impact to the
> user B who already kicked off a build based on the original setting?
>
> We are really appreciate if you can help to clarify these questions for us.
>
> Thanks,
> Dongxiao
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Documentation question: How are the

[Timo Müller]

Hi,

I have a question regarding the licenses of the buildfiles  of the 
yocto-docs project (e.g. Makefile, poky.ent, tools, ...). I'm not able 
to figure out how these files are actually licensed.
The documentation itself is licensed by the Creative Commons 
Attribution-Share Alike 2.0 (CCA-SA) license. Terms of Service states 
that all code submissions are governed by the BSD license 
(http://www.yoctoproject.org/about/terms-service).
Can I contribute to the buildfiles under the BSD license or are they 
also licensed under the CCA-SA?


Best regards
Timo Müller

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to use PRINC

[Rifenbark, Scott M]

> For this example the focus is on the FILESEXTRAPATHS_prepend line in 
> the .bbappend file.  The PRINC = "1" line is included in the example 
> because that is how the file actually appears.  Is the proper thing to 
> change that line to PRINC := "${@int(PRINC) + 2}" ??
> 
> And would the reason be because I am overriding the file in SRC_URI.
> I guess I am unsure as to whether we increment PR here in this 
> example.  If so, I will change it and add some explanatory text around 
> it as part of the example.
> 
> See
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#us
> ing-bbappend-files
> for the entire example.
> 
> Thanks, Scott

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Chris Larson
Sent: Monday, July 02, 2012 9:05 AM
To: Markus Hubig
Cc: Yocto Project Mailing List
Subject: Re: [yocto] How to use PRINC

On Mon, Jul 2, 2012 at 9:00 AM, Markus Hubig  wrote:
> PRINC := "${@int(PRINC) + 2}"

This is the correct method to use in a bbappend. Start with 1,
obviously, and bump it each time the bbappend changes.
-- 
Christopher Larson
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Hob question: meta-yocto layer and 'defaultsetup' distro option

[Barros Pena, Belen]

Great. Thanks, Dongxiao.

I think it is a question of changing the label to make it a bit more
self-explanatory, then. I'll try to come up with something.

Cheers

Belen

On 03/07/2012 13:00, "Xu, Dongxiao"  wrote:

>> -Original Message-
>> From: Barros Pena, Belen
>> Sent: Tuesday, July 03, 2012 7:04 PM
>> To: Khem Raj; Wang, Shane; Xu, Dongxiao
>> Cc: yocto
>> Subject: Re: [yocto] Hob question: meta-yocto layer and 'defaultsetup'
>>distro
>> option
>> 
>> Thanks, Khem.
>> 
>> Just to make sure I understand this correctly: if I don't use the
>>meta-yocto layer,
>> OE-Core should provide reference distro policies that allow me to build
>>an
>> image. So I guess the 'defaultsetup' option in Hob is referring to
>>those OE-Core
>> policies. Shane, Dongxiao: could you confirm if this is the case?
>
>Yes, actually "defaultsetup" will be applied in default for any kind of
>layer settings, including the default OE-Core. The difference is, OE-Core
>only applies "defaultsetup", while for meta-yocto layer, we can add
>additional distro policies (poky, poky-bleeding, etc) to override some of
>the "defaultsetup" settings.
>
>Thanks,
>Dongxiao
>
>> 
>> Thanks!
>> 
>> Belen
>> 
>> On 02/07/2012 17:53, "Khem Raj"  wrote:
>> 
>> >On Mon, Jul 2, 2012 at 9:05 AM, Barros Pena, Belen
>> > wrote:
>> >>
>> >> If I delete the meta-yocto layer, am I supposed to provide the distro
>> >> to be used via a layer or some other means?
>> >
>> >OE-Core has reference distro policies which are enough to generate
>> >images by just using OE-Core and that is what happens when you drop
>> >meta-yocto its testing the reference distro setup from OE-Core
>> >
>> >
>

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Bug 2162 - work in progress

[Barros Pena, Belen]

I know some of you have been asking about designs for bug 2162. I am not
done yet (those settings are quite complicated), but I've uploaded to
Bugzilla what I've done so far:

https://bugzilla.yoctoproject.org/attachment.cgi?id=619


Let me know what you think.

Belen

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/4] linux-yocto-3.4/standard/base: perf scripting updates

[tom . zanussi]

From: Tom Zanussi 

This patchset comprises the kernel side of the modifications needed to
enable the Perl and Python bindings for perf scripting.

Please pull into linux-yocto-3.4 standard/base.

Thanks,

Tom

The following changes since commit a8291fa6f723b0182d2b7033b5d59f412ba7cf72:
  Bruce Ashfield (1):
yaffs2: update to 2012-05-29 development head

are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.4-perf-scripting-standard-base
  
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.4-perf-scripting-standard-base

Tom Zanussi (4):
  Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
  perf: use pkg-config instead of python-config
  perf: add 'libperl not found' warning
  perf: change --root to --prefix for python install

 tools/perf/Makefile |   90 +--
 1 files changed, 87 insertions(+), 3 deletions(-)

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/4] Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"

[tom . zanussi]

From: Tom Zanussi 

This reverts commit 7c35c402e5bc2df6907b8f5d8a495dd6937a1b50.

LIBPERL and LIBPYTHON can now be enabled using the 'perf-scripting'
feature.
---
 tools/perf/Makefile |   87 +-
 1 files changed, 85 insertions(+), 2 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index bb1b364..92271d3 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -539,14 +539,97 @@ else
endif
 endif
 
-BASIC_CFLAGS += -DNO_LIBPERL
-BASIC_CFLAGS += -DNO_LIBPYTHON
+ifdef NO_LIBPERL
+   BASIC_CFLAGS += -DNO_LIBPERL
+else
+   PERL_EMBED_LDOPTS = $(shell perl -MExtUtils::Embed -e ldopts 
2>/dev/null)
+   PERL_EMBED_LDFLAGS = $(call strip-libs,$(PERL_EMBED_LDOPTS))
+   PERL_EMBED_LIBADD = $(call grep-libs,$(PERL_EMBED_LDOPTS))
+   PERL_EMBED_CCOPTS = `perl -MExtUtils::Embed -e ccopts 2>/dev/null`
+   FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
+
+   ifneq ($(call try-cc,$(SOURCE_PERL_EMBED),$(FLAGS_PERL_EMBED)),y)
+   BASIC_CFLAGS += -DNO_LIBPERL
+   else
+   ALL_LDFLAGS += $(PERL_EMBED_LDFLAGS)
+   EXTLIBS += $(PERL_EMBED_LIBADD)
+   LIB_OBJS += $(OUTPUT)util/scripting-engines/trace-event-perl.o
+   LIB_OBJS += $(OUTPUT)scripts/perl/Perf-Trace-Util/Context.o
+   endif
+endif
+
+disable-python = $(eval $(disable-python_code))
+define disable-python_code
+  BASIC_CFLAGS += -DNO_LIBPYTHON
+  $(if $(1),$(warning No $(1) was found))
+  $(warning Python support won't be built)
+endef
 
 override PYTHON := \
   $(call get-executable-or-default,PYTHON,python)
 
 ifndef PYTHON
   $(call disable-python,python interpreter)
+  python-clean :=
+else
+
+  PYTHON_WORD := $(call shell-wordify,$(PYTHON))
+
+  # python extension build directories
+  PYTHON_EXTBUILD := $(OUTPUT)python_ext_build/
+  PYTHON_EXTBUILD_LIB := $(PYTHON_EXTBUILD)lib/
+  PYTHON_EXTBUILD_TMP := $(PYTHON_EXTBUILD)tmp/
+  export PYTHON_EXTBUILD_LIB PYTHON_EXTBUILD_TMP
+
+  python-clean := rm -rf $(PYTHON_EXTBUILD) $(OUTPUT)python/perf.so
+
+  ifdef NO_LIBPYTHON
+$(call disable-python)
+  else
+
+override PYTHON_CONFIG := \
+  $(call get-executable-or-default,PYTHON_CONFIG,$(PYTHON)-config)
+
+ifndef PYTHON_CONFIG
+  $(call disable-python,python-config tool)
+else
+
+  PYTHON_CONFIG_SQ := $(call shell-sq,$(PYTHON_CONFIG))
+
+  PYTHON_EMBED_LDOPTS := $(shell $(PYTHON_CONFIG_SQ) --ldflags 2>/dev/null)
+  PYTHON_EMBED_LDFLAGS := $(call strip-libs,$(PYTHON_EMBED_LDOPTS))
+  PYTHON_EMBED_LIBADD := $(call grep-libs,$(PYTHON_EMBED_LDOPTS))
+  PYTHON_EMBED_CCOPTS := $(shell $(PYTHON_CONFIG_SQ) --cflags 2>/dev/null)
+  FLAGS_PYTHON_EMBED := $(PYTHON_EMBED_CCOPTS) $(PYTHON_EMBED_LDOPTS)
+
+  ifneq ($(call try-cc,$(SOURCE_PYTHON_EMBED),$(FLAGS_PYTHON_EMBED)),y)
+$(call disable-python,Python.h (for Python 2.x))
+  else
+
+ifneq ($(call try-cc,$(SOURCE_PYTHON_VERSION),$(FLAGS_PYTHON_EMBED)),y)
+  $(warning Python 3 is not yet supported; please set)
+  $(warning PYTHON and/or PYTHON_CONFIG appropriately.)
+  $(warning If you also have Python 2 installed, then)
+  $(warning try something like:)
+  $(warning $(and ,))
+  $(warning $(and ,)  make PYTHON=python2)
+  $(warning $(and ,))
+  $(warning Otherwise, disable Python support entirely:)
+  $(warning $(and ,))
+  $(warning $(and ,)  make NO_LIBPYTHON=1)
+  $(warning $(and ,))
+  $(error   $(and ,))
+else
+  ALL_LDFLAGS += $(PYTHON_EMBED_LDFLAGS)
+  EXTLIBS += $(PYTHON_EMBED_LIBADD)
+  LIB_OBJS += $(OUTPUT)util/scripting-engines/trace-event-python.o
+  LIB_OBJS += $(OUTPUT)scripts/python/Perf-Trace-Util/Context.o
+  LANG_BINDINGS += $(OUTPUT)python/perf.so
+endif
+
+  endif
+endif
+  endif
 endif
 
 ifdef NO_DEMANGLE
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 3/4] perf: add 'libperl not found' warning

[tom . zanussi]

From: Tom Zanussi 

If libperl isn't found, display a message to that effect along with
some hints on how to fix it.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 35425ab..f966313 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -549,6 +549,7 @@ else
FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
 
ifneq ($(call try-cc,$(SOURCE_PERL_EMBED),$(FLAGS_PERL_EMBED)),y)
+   msg := $(warning libperl not found, disables Perl scripting 
support. Please install libperl-dev or perl-devel);
BASIC_CFLAGS += -DNO_LIBPERL
else
ALL_LDFLAGS += $(PERL_EMBED_LDFLAGS)
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 4/4] perf: change --root to --prefix for python install

[tom . zanussi]

From: Tom Zanussi 

Otherwise we get the sysroot path appended to the build path, not what
we want.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index f966313..15ec207 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -954,7 +954,7 @@ install: all
$(INSTALL) scripts/python/bin/* -t 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin'
 
 install-python_ext:
-   $(PYTHON_WORD) util/setup.py --quiet install --root='/$(DESTDIR_SQ)'
+   $(PYTHON_WORD) util/setup.py --quiet install 
--prefix='$(DESTDIR_SQ)/usr'
 
 install-doc:
$(MAKE) -C Documentation install
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/4] perf: use pkg-config instead of python-config

[tom . zanussi]

From: Tom Zanussi 

Python has build flags available via pkg-config, use those at
build-time instead.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 92271d3..35425ab 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -596,10 +596,10 @@ else
 
   PYTHON_CONFIG_SQ := $(call shell-sq,$(PYTHON_CONFIG))
 
-  PYTHON_EMBED_LDOPTS := $(shell $(PYTHON_CONFIG_SQ) --ldflags 2>/dev/null)
+  PYTHON_EMBED_LDOPTS := $(shell pkg-config --libs python 2>/dev/null)
   PYTHON_EMBED_LDFLAGS := $(call strip-libs,$(PYTHON_EMBED_LDOPTS))
   PYTHON_EMBED_LIBADD := $(call grep-libs,$(PYTHON_EMBED_LDOPTS))
-  PYTHON_EMBED_CCOPTS := $(shell $(PYTHON_CONFIG_SQ) --cflags 2>/dev/null)
+  PYTHON_EMBED_CCOPTS := $(shell pkg-config --cflags python 2>/dev/null)
   FLAGS_PYTHON_EMBED := $(PYTHON_EMBED_CCOPTS) $(PYTHON_EMBED_LDOPTS)
 
   ifneq ($(call try-cc,$(SOURCE_PYTHON_EMBED),$(FLAGS_PYTHON_EMBED)),y)
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/1] linux-yocto-3.4/meta: perf scripting updates

[tom . zanussi]

From: Tom Zanussi 

This patchset enables FTRACE_SYSCALLS, used by some existing perf scripts.

Please pull into linux-yocto-3.4.

Thanks,

Tom

The following changes are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.4-perf-scripting-meta
  
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.4-perf-scripting-meta

Tom Zanussi (1):
  features/ftrace: enable FTRACE_SYSCALLS

 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/1] features/ftrace: enable FTRACE_SYSCALLS

[tom . zanussi]

From: Tom Zanussi 

Add support for generic syscall entry/exit tracing.

Signed-off-by: Tom Zanussi 
---
 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg 
b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
index bab800c..692dffe 100644
--- a/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
+++ b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
@@ -1,2 +1,3 @@
 CONFIG_FUNCTION_TRACER=y
 CONFIG_FUNCTION_GRAPH_TRACER=y
+CONFIG_FTRACE_SYSCALLS=y
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/4] linux-yocto-3.2/standard/base: perf scripting updates

[tom . zanussi]

From: Tom Zanussi 

This patchset comprises the kernel side of the modifications needed to
enable the Perl and Python bindings for perf scripting.

Please pull into linux-yocto-3.2 standard/base.

Thanks,

Tom

The following changes are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.2-perf-scripting-standard-base
  
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.2-perf-scripting-standard-base

Tom Zanussi (4):
  Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
  perf: use pkg-config instead of python-config
  perf: add 'libperl not found' warning
  perf: change --root to --prefix for python install

 tools/perf/Makefile |   90 +--
 1 files changed, 87 insertions(+), 3 deletions(-)

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/4] Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"

[tom . zanussi]

From: Tom Zanussi 

This reverts commit 417fc778a86e81303bab5883b919ee422ec51c04.

LIBPERL and LIBPYTHON can now be enabled using the 'perf-scripting'
feature.
---
 tools/perf/Makefile |   87 +-
 1 files changed, 85 insertions(+), 2 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 287c7b3..b98e307 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -480,14 +480,97 @@ else
endif
 endif
 
-BASIC_CFLAGS += -DNO_LIBPERL
-BASIC_CFLAGS += -DNO_LIBPYTHON
+ifdef NO_LIBPERL
+   BASIC_CFLAGS += -DNO_LIBPERL
+else
+   PERL_EMBED_LDOPTS = $(shell perl -MExtUtils::Embed -e ldopts 
2>/dev/null)
+   PERL_EMBED_LDFLAGS = $(call strip-libs,$(PERL_EMBED_LDOPTS))
+   PERL_EMBED_LIBADD = $(call grep-libs,$(PERL_EMBED_LDOPTS))
+   PERL_EMBED_CCOPTS = `perl -MExtUtils::Embed -e ccopts 2>/dev/null`
+   FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
+
+   ifneq ($(call try-cc,$(SOURCE_PERL_EMBED),$(FLAGS_PERL_EMBED)),y)
+   BASIC_CFLAGS += -DNO_LIBPERL
+   else
+   ALL_LDFLAGS += $(PERL_EMBED_LDFLAGS)
+   EXTLIBS += $(PERL_EMBED_LIBADD)
+   LIB_OBJS += $(OUTPUT)util/scripting-engines/trace-event-perl.o
+   LIB_OBJS += $(OUTPUT)scripts/perl/Perf-Trace-Util/Context.o
+   endif
+endif
+
+disable-python = $(eval $(disable-python_code))
+define disable-python_code
+  BASIC_CFLAGS += -DNO_LIBPYTHON
+  $(if $(1),$(warning No $(1) was found))
+  $(warning Python support won't be built)
+endef
 
 override PYTHON := \
   $(call get-executable-or-default,PYTHON,python)
 
 ifndef PYTHON
   $(call disable-python,python interpreter)
+  python-clean :=
+else
+
+  PYTHON_WORD := $(call shell-wordify,$(PYTHON))
+
+  # python extension build directories
+  PYTHON_EXTBUILD := $(OUTPUT)python_ext_build/
+  PYTHON_EXTBUILD_LIB := $(PYTHON_EXTBUILD)lib/
+  PYTHON_EXTBUILD_TMP := $(PYTHON_EXTBUILD)tmp/
+  export PYTHON_EXTBUILD_LIB PYTHON_EXTBUILD_TMP
+
+  python-clean := rm -rf $(PYTHON_EXTBUILD) $(OUTPUT)python/perf.so
+
+  ifdef NO_LIBPYTHON
+$(call disable-python)
+  else
+
+override PYTHON_CONFIG := \
+  $(call get-executable-or-default,PYTHON_CONFIG,$(PYTHON)-config)
+
+ifndef PYTHON_CONFIG
+  $(call disable-python,python-config tool)
+else
+
+  PYTHON_CONFIG_SQ := $(call shell-sq,$(PYTHON_CONFIG))
+
+  PYTHON_EMBED_LDOPTS := $(shell $(PYTHON_CONFIG_SQ) --ldflags 2>/dev/null)
+  PYTHON_EMBED_LDFLAGS := $(call strip-libs,$(PYTHON_EMBED_LDOPTS))
+  PYTHON_EMBED_LIBADD := $(call grep-libs,$(PYTHON_EMBED_LDOPTS))
+  PYTHON_EMBED_CCOPTS := $(shell $(PYTHON_CONFIG_SQ) --cflags 2>/dev/null)
+  FLAGS_PYTHON_EMBED := $(PYTHON_EMBED_CCOPTS) $(PYTHON_EMBED_LDOPTS)
+
+  ifneq ($(call try-cc,$(SOURCE_PYTHON_EMBED),$(FLAGS_PYTHON_EMBED)),y)
+$(call disable-python,Python.h (for Python 2.x))
+  else
+
+ifneq ($(call try-cc,$(SOURCE_PYTHON_VERSION),$(FLAGS_PYTHON_EMBED)),y)
+  $(warning Python 3 is not yet supported; please set)
+  $(warning PYTHON and/or PYTHON_CONFIG appropriately.)
+  $(warning If you also have Python 2 installed, then)
+  $(warning try something like:)
+  $(warning $(and ,))
+  $(warning $(and ,)  make PYTHON=python2)
+  $(warning $(and ,))
+  $(warning Otherwise, disable Python support entirely:)
+  $(warning $(and ,))
+  $(warning $(and ,)  make NO_LIBPYTHON=1)
+  $(warning $(and ,))
+  $(error   $(and ,))
+else
+  ALL_LDFLAGS += $(PYTHON_EMBED_LDFLAGS)
+  EXTLIBS += $(PYTHON_EMBED_LIBADD)
+  LIB_OBJS += $(OUTPUT)util/scripting-engines/trace-event-python.o
+  LIB_OBJS += $(OUTPUT)scripts/python/Perf-Trace-Util/Context.o
+  LANG_BINDINGS += $(OUTPUT)python/perf.so
+endif
+
+  endif
+endif
+  endif
 endif
 
 ifdef NO_DEMANGLE
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/4] perf: use pkg-config instead of python-config

[tom . zanussi]

From: Tom Zanussi 

Python has build flags available via pkg-config, use those at
build-time instead.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index b98e307..b8cb4d4 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -537,10 +537,10 @@ else
 
   PYTHON_CONFIG_SQ := $(call shell-sq,$(PYTHON_CONFIG))
 
-  PYTHON_EMBED_LDOPTS := $(shell $(PYTHON_CONFIG_SQ) --ldflags 2>/dev/null)
+  PYTHON_EMBED_LDOPTS := $(shell pkg-config --libs python 2>/dev/null)
   PYTHON_EMBED_LDFLAGS := $(call strip-libs,$(PYTHON_EMBED_LDOPTS))
   PYTHON_EMBED_LIBADD := $(call grep-libs,$(PYTHON_EMBED_LDOPTS))
-  PYTHON_EMBED_CCOPTS := $(shell $(PYTHON_CONFIG_SQ) --cflags 2>/dev/null)
+  PYTHON_EMBED_CCOPTS := $(shell pkg-config --cflags python 2>/dev/null)
   FLAGS_PYTHON_EMBED := $(PYTHON_EMBED_CCOPTS) $(PYTHON_EMBED_LDOPTS)
 
   ifneq ($(call try-cc,$(SOURCE_PYTHON_EMBED),$(FLAGS_PYTHON_EMBED)),y)
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 3/4] perf: add 'libperl not found' warning

[tom . zanussi]

From: Tom Zanussi 

If libperl isn't found, display a message to that effect along with
some hints on how to fix it.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index b8cb4d4..97bca9c 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -490,6 +490,7 @@ else
FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
 
ifneq ($(call try-cc,$(SOURCE_PERL_EMBED),$(FLAGS_PERL_EMBED)),y)
+   msg := $(warning libperl not found, disables Perl scripting 
support. Please install libperl-dev or perl-devel);
BASIC_CFLAGS += -DNO_LIBPERL
else
ALL_LDFLAGS += $(PERL_EMBED_LDFLAGS)
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 4/4] perf: change --root to --prefix for python install

[tom . zanussi]

From: Tom Zanussi 

Otherwise we get the sysroot path appended to the build path, not what
we want.

Signed-off-by: Tom Zanussi 
---
 tools/perf/Makefile |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 97bca9c..e5456d3 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -878,7 +878,7 @@ install: all
$(INSTALL) scripts/python/bin/* -t 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin'
 
 install-python_ext:
-   $(PYTHON_WORD) util/setup.py --quiet install --root='/$(DESTDIR_SQ)'
+   $(PYTHON_WORD) util/setup.py --quiet install 
--prefix='$(DESTDIR_SQ)/usr'
 
 install-doc:
$(MAKE) -C Documentation install
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 0/1] linux-yocto-3.2/meta: perf scripting updates

[tom . zanussi]

From: Tom Zanussi 

This patchset enables FTRACE_SYSCALLS, used by some existing perf scripts.

Please pull into linux-yocto-3.2.

Thanks,

Tom

Tom Zanussi (1):
  features/ftrace: enable FTRACE_SYSCALLS

 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 1/1] features/ftrace: enable FTRACE_SYSCALLS

[tom . zanussi]

From: Tom Zanussi 

Add support for generic syscall entry/exit tracing.

Signed-off-by: Tom Zanussi 
---
 meta/cfg/kernel-cache/features/ftrace/ftrace.cfg |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg 
b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
index bab800c..692dffe 100644
--- a/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
+++ b/meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
@@ -1,2 +1,3 @@
 CONFIG_FUNCTION_TRACER=y
 CONFIG_FUNCTION_GRAPH_TRACER=y
+CONFIG_FTRACE_SYSCALLS=y
-- 
1.7.0.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[Rifenbark, Scott M]

Jim, 

Do you have a list of what you had to install?  I can add this to the QS 
"Packages" section.

Scott

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of jfabernathy
Sent: Sunday, June 24, 2012 9:06 AM
To: yocto@yoctoproject.org
Subject: [yocto] prerequisite tools for making documentation

I had a need to look at the bitbake manual in the 
poky/bitbake/doc/manual directory and tried to make pdf.  I had all the 
prerequisites listed in the QS guide.  However, I found the make failed 
due to a number of xml related tools being missing.  I installed those 
and got the pdf manual generated.

Should we add those xml tools to the prerequisites?  BTW, I'm using 
denzil branch and referring to the QS guide 1.2.

Jim A

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[Chris Hallinan]

On Tue, Jul 3, 2012 at 2:25 PM, Rifenbark, Scott M <
scott.m.rifenb...@intel.com> wrote:

> Jim,
>
> Do you have a list of what you had to install?  I can add this to the QS
> "Packages" section.
>
> Scott
>
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:
> yocto-boun...@yoctoproject.org] On Behalf Of jfabernathy
> Sent: Sunday, June 24, 2012 9:06 AM
> To: yocto@yoctoproject.org
> Subject: [yocto] prerequisite tools for making documentation
>
> I had a need to look at the bitbake manual in the
> poky/bitbake/doc/manual directory and tried to make pdf.  I had all the
> prerequisites listed in the QS guide.  However, I found the make failed
> due to a number of xml related tools being missing.  I installed those
> and got the pdf manual generated.
>
> Should we add those xml tools to the prerequisites?  BTW, I'm using
> denzil branch and referring to the QS guide 1.2.
>

I'd also be interested in knowing what host you built it on, as several of
us (including myself) have had difficulty building docs.

Thanks,

Chris

-- 
Life is like Linux - it never stands still.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[jfabernathy]

On 07/03/2012 02:25 PM, Rifenbark, Scott M wrote:

Jim,

Do you have a list of what you had to install?  I can add this to the QS 
"Packages" section.

Scott

*Scott,

I had to go thru the apt log for the day I posted this issues. Below are 
the packages.  I imagine that texlive brought in the last 8 or so.


Jim A

Selecting previously unselected package libxml2-utils.

Selecting previously unselected package docbook-xsl.

Selecting previously unselected package xmlto.

Selecting previously unselected package xmltex.

Selecting previously unselected package texlive.
Selecting previously unselected package texlive-bibtex-extra.
Selecting previously unselected package preview-latex-style.
Selecting previously unselected package texlive-pictures.
Selecting previously unselected package texlive-latex-extra.
Selecting previously unselected package texlive-math-extra.
Selecting previously unselected package dblatex.
Selecting previously unselected package texlive-latex-extra-doc.
Selecting previously unselected package texlive-pictures-doc. *



-Original Message- From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of jfabernathy Sent: 
Sunday, June 24, 2012 9:06 AM To: yocto@yoctoproject.org Subject: 
[yocto] prerequisite tools for making documentation I had a need to look 
at the bitbake manual in the poky/bitbake/doc/manual directory and tried 
to make pdf. I had all the prerequisites listed in the QS guide. 
However, I found the make failed due to a number of xml related tools 
being missing. I installed those and got the pdf manual generated. 
Should we add those xml tools to the prerequisites? BTW, I'm using 
denzil branch and referring to the QS guide 1.2. Jim A 
___ yocto mailing list 
yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[jfabernathy]

On 07/03/2012 02:57 PM, Chris Hallinan wrote:
On Tue, Jul 3, 2012 at 2:25 PM, Rifenbark, Scott M 
mailto:scott.m.rifenb...@intel.com>> wrote:


Jim,

Do you have a list of what you had to install?  I can add this to
the QS "Packages" section.

Scott

-Original Message-
From: yocto-boun...@yoctoproject.org

[mailto:yocto-boun...@yoctoproject.org
] On Behalf Of jfabernathy
Sent: Sunday, June 24, 2012 9:06 AM
To: yocto@yoctoproject.org 
Subject: [yocto] prerequisite tools for making documentation

I had a need to look at the bitbake manual in the
poky/bitbake/doc/manual directory and tried to make pdf.  I had
all the
prerequisites listed in the QS guide.  However, I found the make
failed
due to a number of xml related tools being missing.  I installed those
and got the pdf manual generated.

Should we add those xml tools to the prerequisites?  BTW, I'm using
denzil branch and referring to the QS guide 1.2.


I'd also be interested in knowing what host you built it on, as 
several of us (including myself) have had difficulty building docs.




I'm running Ubuntu 12.04 LTS.

Jim A

Thanks,

Chris
--
Life is like Linux - it never stands still.





___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/4] linux-yocto-3.4/standard/base: perf scripting updates

[Bruce Ashfield]

On 12-07-03 02:07 PM, tom.zanu...@intel.com wrote:

From: Tom Zanussi

This patchset comprises the kernel side of the modifications needed to
enable the Perl and Python bindings for perf scripting.


Looks good to me, I'm happy to finally revert the no_perl patch :)
I assume that you verified everything happily builds with and
without the perf-scripting being available ?

Cheers,

Bruce





Please pull into linux-yocto-3.4 standard/base.

Thanks,

Tom

The following changes since commit a8291fa6f723b0182d2b7033b5d59f412ba7cf72:
   Bruce Ashfield (1):
 yaffs2: update to 2012-05-29 development head

are available in the git repository at:

   git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.4-perf-scripting-standard-base
   
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.4-perf-scripting-standard-base

Tom Zanussi (4):
   Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
   perf: use pkg-config instead of python-config
   perf: add 'libperl not found' warning
   perf: change --root to --prefix for python install

  tools/perf/Makefile |   90 +--
  1 files changed, 87 insertions(+), 3 deletions(-)



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[Robert P. J. Day]

On Tue, 3 Jul 2012, Chris Hallinan wrote:

> I'd also be interested in knowing what host you built it on, as
> several of us (including myself) have had difficulty building docs.

  just recently, i whined incessantly about the issue i was having
building PDF docs on my ubuntu 12.04 system,

http://ubuntu.5.n6.nabble.com/quot-Cannot-open-file-sRGB-pf-quot-when-using-quot-fop-quot-to-generate-PDF-td4981668.html

anyone have a suggestion?  should i switch javas?  if anyone is
getting PDFs to build on their ubuntu system, i'd be interested in
knowing their setup and package list.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/1] linux-yocto-3.4/meta: perf scripting updates

[Bruce Ashfield]

On 12-07-03 02:08 PM, tom.zanu...@intel.com wrote:

From: Tom Zanussi

This patchset enables FTRACE_SYSCALLS, used by some existing perf scripts.

Please pull into linux-yocto-3.4.


A reasonable addition, I can think of when we'd not want this enabled
by default. I'll add this to my queue after it sits on the list for bit.

Cheers,

Bruce



Thanks,

Tom

The following changes are available in the git repository at:

   git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.4-perf-scripting-meta
   
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.4-perf-scripting-meta

Tom Zanussi (1):
   features/ftrace: enable FTRACE_SYSCALLS

  meta/cfg/kernel-cache/features/ftrace/ftrace.cfg |1 +
  1 files changed, 1 insertions(+), 0 deletions(-)



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/4] linux-yocto-3.2/standard/base: perf scripting updates

[Bruce Ashfield]

On 12-07-03 02:09 PM, tom.zanu...@intel.com wrote:

From: Tom Zanussi

This patchset comprises the kernel side of the modifications needed to
enable the Perl and Python bindings for perf scripting.

Please pull into linux-yocto-3.2 standard/base.


Ack'd. Same as the 3.4 variant. Queued pending any review comments.

Cheers,

Bruce



Thanks,

Tom

The following changes are available in the git repository at:

   git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
tzanussi/3.2-perf-scripting-standard-base
   
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.2-perf-scripting-standard-base

Tom Zanussi (4):
   Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
   perf: use pkg-config instead of python-config
   perf: add 'libperl not found' warning
   perf: change --root to --prefix for python install

  tools/perf/Makefile |   90 +--
  1 files changed, 87 insertions(+), 3 deletions(-)



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/4] linux-yocto-3.4/standard/base: perf scripting updates

[Tom Zanussi]

On Tue, 2012-07-03 at 15:05 -0400, Bruce Ashfield wrote:
> On 12-07-03 02:07 PM, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > This patchset comprises the kernel side of the modifications needed to
> > enable the Perl and Python bindings for perf scripting.
> 
> Looks good to me, I'm happy to finally revert the no_perl patch :)
> I assume that you verified everything happily builds with and
> without the perf-scripting being available ?
> 

Yeah, I built and run-tested several different machines with and without
perf-scripting and perf-tui and didn't see any problems...

Tom

> Cheers,
> 
> Bruce
> 
> 
> 
> >
> > Please pull into linux-yocto-3.4 standard/base.
> >
> > Thanks,
> >
> > Tom
> >
> > The following changes since commit a8291fa6f723b0182d2b7033b5d59f412ba7cf72:
> >Bruce Ashfield (1):
> >  yaffs2: update to 2012-05-29 development head
> >
> > are available in the git repository at:
> >
> >git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git 
> > tzanussi/3.4-perf-scripting-standard-base
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/3.4-perf-scripting-standard-base
> >
> > Tom Zanussi (4):
> >Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
> >perf: use pkg-config instead of python-config
> >perf: add 'libperl not found' warning
> >perf: change --root to --prefix for python install
> >
> >   tools/perf/Makefile |   90 
> > +--
> >   1 files changed, 87 insertions(+), 3 deletions(-)
> >
> 


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[McClintock Matthew-B29882]

I went through this trying to fix the docs build on a machine and my
build script has some clues about what I needed to do:

export PATH=/opt/fop-1.0:$PATH
export PATH=/usr/local/bin:$PATH

which xsltproc

cd documentation

for i in adt-manual dev-manual yocto-project-qs bsp-guide
kernel-manual poky-ref-manual; do
make pdf html DOC=$i BRANCH=edison
done

I think I needed a new 'fop' and a new 'xsltproc' - this was on an old
build machine (CentOS 5.X) though so things could be different.

-M

On Tue, Jul 3, 2012 at 2:07 PM, Robert P. J. Day  wrote:
> On Tue, 3 Jul 2012, Chris Hallinan wrote:
>
>> I'd also be interested in knowing what host you built it on, as
>> several of us (including myself) have had difficulty building docs.
>
>   just recently, i whined incessantly about the issue i was having
> building PDF docs on my ubuntu 12.04 system,
>
> http://ubuntu.5.n6.nabble.com/quot-Cannot-open-file-sRGB-pf-quot-when-using-quot-fop-quot-to-generate-PDF-td4981668.html
>
> anyone have a suggestion?  should i switch javas?  if anyone is
> getting PDFs to build on their ubuntu system, i'd be interested in
> knowing their setup and package list.
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[Rifenbark, Scott M]

Jim - thanks for the list for Ubuntu.  If anyone has knowledge of building the 
BitBake documentation on Fedora, CentOS, and openSUSE and the packages needed 
that are not in the QS, please post.

Thanks,
Scott

From: jfabernathy [mailto:jfaberna...@gmail.com]
Sent: Tuesday, July 03, 2012 11:59 AM
To: Chris Hallinan
Cc: Rifenbark, Scott M; yocto@yoctoproject.org
Subject: Re: [yocto] prerequisite tools for making documentation

On 07/03/2012 02:57 PM, Chris Hallinan wrote:
On Tue, Jul 3, 2012 at 2:25 PM, Rifenbark, Scott M 
mailto:scott.m.rifenb...@intel.com>> wrote:
Jim,

Do you have a list of what you had to install?  I can add this to the QS 
"Packages" section.

Scott

-Original Message-
From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] 
On Behalf Of jfabernathy
Sent: Sunday, June 24, 2012 9:06 AM
To: yocto@yoctoproject.org
Subject: [yocto] prerequisite tools for making documentation

I had a need to look at the bitbake manual in the
poky/bitbake/doc/manual directory and tried to make pdf.  I had all the
prerequisites listed in the QS guide.  However, I found the make failed
due to a number of xml related tools being missing.  I installed those
and got the pdf manual generated.

Should we add those xml tools to the prerequisites?  BTW, I'm using
denzil branch and referring to the QS guide 1.2.

I'd also be interested in knowing what host you built it on, as several of us 
(including myself) have had difficulty building docs.


I'm running Ubuntu 12.04 LTS.

Jim A

Thanks,

Chris

--
Life is like Linux - it never stands still.


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] prerequisite tools for making documentation

[Rifenbark, Scott M]

For Ubuntu 10.04 I installed dblatex and that installed everything in Jim's 
list from texlive down (inclusive).  I was able to make the BitBake documents 
after installing dblatex.

Scott

From: jfabernathy [mailto:jfaberna...@gmail.com]
Sent: Tuesday, July 03, 2012 11:58 AM
To: Rifenbark, Scott M
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] prerequisite tools for making documentation

On 07/03/2012 02:25 PM, Rifenbark, Scott M wrote:

Jim,



Do you have a list of what you had to install?  I can add this to the QS 
"Packages" section.



Scott
Scott,

I had to go thru the apt log for the day I posted this issues.  Below are the 
packages.  I imagine that texlive brought in the last 8 or so.

Jim A

Selecting previously unselected package libxml2-utils.

Selecting previously unselected package docbook-xsl.

Selecting previously unselected package xmlto.

Selecting previously unselected package xmltex.

Selecting previously unselected package texlive.
Selecting previously unselected package texlive-bibtex-extra.
Selecting previously unselected package preview-latex-style.
Selecting previously unselected package texlive-pictures.
Selecting previously unselected package texlive-latex-extra.
Selecting previously unselected package texlive-math-extra.
Selecting previously unselected package dblatex.
Selecting previously unselected package texlive-latex-extra-doc.
Selecting previously unselected package texlive-pictures-doc.



-Original Message- From: 
yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of jfabernathy Sent: Sunday, 
June 24, 2012 9:06 AM To: yocto@yoctoproject.org 
Subject: [yocto] prerequisite tools for making documentation I had a need to 
look at the bitbake manual in the poky/bitbake/doc/manual directory and tried 
to make pdf. I had all the prerequisites listed in the QS guide. However, I 
found the make failed due to a number of xml related tools being missing. I 
installed those and got the pdf manual generated. Should we add those xml tools 
to the prerequisites? BTW, I'm using denzil branch and referring to the QS 
guide 1.2. Jim A ___ yocto mailing 
list yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Web Hob's design - missing developer workflow?

[Stewart, David C]

Gang - I was talking with Jessica today about the WebHob design and how we want 
to prioritize some of the feature development. (And I want to say here, I 
really appreciate the clarity and thought process Jessica is bringing to the 
discussion!)

It dawned on me as we were talking that we may have something really 
fundamental missing in the design in the area of workflow. I don't know that we 
have yet thought through the story of how someone uses this thing to get their 
job done.  Let me give you a couple of examples:

I'm developing an embedded device which is headless, based on a particular 
board. It's similar enough to Baryon that I can start there.  So in Web Hob, I 
pick my machine type and build profile, I add in the BSP layer and Baryon layer 
and do a build. It succeeds, so I can now boot up my board and it works.

Now I want to do something like change the default root password. OK, I don't 
know where that file is located so how do I edit it? (Remember, there are no 
local files to do a find | grep to locate "passwd" anyplace.) So how do I 
change this?

In fact, if I want to edit any of the static files we provide in YP, I don't 
know how to do this.

Next I want to add my own application, which consists of .c files, .h files and 
a makefile. (Because I am really old school). So I create a .bb file for this 
and then... what? How do I get this collection of files into my project in 
WebHob to build it?

For that last one, I guess I could treat it as a layer, since I see a way to 
provide an external layer to WebHob. OK, it means I need to create a 
conf/layer.conf file, right? Do I have any clues on how to do this or am I on 
my own?

Oh, and when I tried to make my new layer build, I had a compile error, which I 
just fixed in a .c file. How do I get that file onto the WebHob server? Do I 
need to reload the whole layer?

If you have followed me so far on this journey, you can see that we have 
created a system which can build a custom linux and add/remove packages. But 
when it comes to the steps of actually doing real development, I think there is 
still something missing.

I would challenge the team to think through the bigger developer's story line 
and make sure we have the support we need in WebHob.  Thanks...

Dave
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] how do I deal with two meta-fsl-ppc repos?

[Bob Cochran]

Hello,

I can find a meta-fsl-ppc tree at http://git.freescale.com/git/cgit.cgi/ 
and also one at http://git.yoctoproject.org/.


The former was last updated 12 days ago and the latter was last updated 
5 weeks ago.


Which repo am I supposed to use going forward?  Please explain how these 
two trees will differ.  I'm hoping that the yocto meta-fsl-ppc repo will 
stay active as both a repo for edison patches and for a master branch 
that will benefit from community feedback, discussion, and patches.


Thanks,

Bob

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto