Re: [yocto] examples / docs on utilizing an external toolchain
Bug submitted: http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 My question still stands even w/o it being in formal docs. - k On Aug 2, 2011, at 11:29 AM, Rifenbark, Scott M wrote: > Is the problem here that we need better documentation on using a prebuilt > toolchain? I will have to learn more about the context of the problem from > someone. The bug could just be against documentation in general and specify > the need for "better documentation using a prebuilt toolchain." > > ScottR > > -Original Message- > From: Kumar Gala [mailto:ga...@kernel.crashing.org] > Sent: Tuesday, August 02, 2011 9:10 AM > To: Stewart, David C > Cc: 'yocto@yoctoproject.org'; Rifenbark, Scott M > Subject: Re: [yocto] examples / docs on utilizing an external toolchain > > I can, but not sure what the bug is. > > - k > > On Jul 28, 2011, at 11:39 PM, Stewart, David C wrote: > >> Scott - I have had a couple of questions about this exact topic. Can you >> please submit a bug on this? Thanks. >> >> Sent from my Blackberry >> >> - Original Message - >> From: Kumar Gala [mailto:ga...@kernel.crashing.org] >> Sent: Wednesday, July 27, 2011 08:37 PM >> To: Yocto discussion list >> Subject: [yocto] examples / docs on utilizing an external toolchain >> >> It seems like there is a way to use a prebuilt toolchain with poky but no >> real details. >> >> Some refs in the docs like: >> >> POKYMODE >> Toolchain selector. It can be external toolchain built from Poky or few >> supported combinations of upstream GCC or CodeSourcery Labs toolchain. >> >> But grepping the code there doesn't seem to be any actual use of POKYMODE. >> There seems to be some references even on the autobuilder about this >> 'nightly-external-toolchain'. So wondering what the details where on how to >> configure things to use an external toolchain. >> >> - k >> ___ >> 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] examples / docs on utilizing an external toolchain
On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: > Bug submitted: > > http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 > > My question still stands even w/o it being in formal docs. FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. I'd be interested to know where we've missed the references to it and get to get those references fixed. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote: > On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: > > Bug submitted: > > > > http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 > > > > My question still stands even w/o it being in formal docs. > > FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. > I'd be interested to know where we've missed the references to it and > get to get those references fixed. git grep tells me we still have it in local.conf.sample in meta-yocto, as well as in the reference manual. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
On Aug 3, 2011, at 9:29 AM, Paul Eggleton wrote: > On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote: >> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: >>> Bug submitted: >>> >>> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 >>> >>> My question still stands even w/o it being in formal docs. >> >> FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. >> I'd be interested to know where we've missed the references to it and >> get to get those references fixed. > > git grep tells me we still have it in local.conf.sample in meta-yocto, as > well > as in the reference manual. Yep, and not sure if the online docs: http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html are generated nightly or not? - k ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
On Aug 3, 2011, at 9:22 AM, Richard Purdie wrote: > On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: >> Bug submitted: >> >> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 >> >> My question still stands even w/o it being in formal docs. > > FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. > I'd be interested to know where we've missed the references to it and > get to get those references fixed. Ok, but how does one use TCMODE? :) is there an example around anywhere? - k ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
No, they're generated ad-hoc when needed. Scott, let's regenerate them and talk about a regular generation of them offline. -b On Wed, Aug 3, 2011 at 7:49 AM, Kumar Gala wrote: > > On Aug 3, 2011, at 9:29 AM, Paul Eggleton wrote: > >> On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote: >>> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: Bug submitted: http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 My question still stands even w/o it being in formal docs. >>> >>> FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. >>> I'd be interested to know where we've missed the references to it and >>> get to get those references fixed. >> >> git grep tells me we still have it in local.conf.sample in meta-yocto, as >> well >> as in the reference manual. > > Yep, and not sure if the online docs: > > http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html > > are generated nightly or not? > > - k > ___ > 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] examples / docs on utilizing an external toolchain
On Wed, 2011-08-03 at 09:50 -0500, Kumar Gala wrote: > On Aug 3, 2011, at 9:22 AM, Richard Purdie wrote: > > > On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: > >> Bug submitted: > >> > >> http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 > >> > >> My question still stands even w/o it being in formal docs. > > > > FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. > > I'd be interested to know where we've missed the references to it and > > get to get those references fixed. > > Ok, but how does one use TCMODE? :) > > is there an example around anywhere? I'll explain on the condition that someone actually documents this ;-). TCMODE determines which of the files in meta/conf/distro/include/tcmode-* is used. It defaults to "default" and our default toolchain definition is in tcmode-default.inc. There is another example there which is "external-csl2008q3". As you can see from the tcmode-external-csl2008q3 file, it sets up the system to use an external toolchain instead. So you can define one of these files in your layer and then the system can select alternative toolchain configurations. Does that help? :) There is a similar TCLIBC variable which controls which libc is used (eglibc or uclibc). Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] examples / docs on utilizing an external toolchain
Ok - ping me when you want to discuss this -Original Message- From: Flanagan, Elizabeth [mailto:elizabeth.flana...@intel.com] Sent: Wednesday, August 03, 2011 8:02 AM To: Kumar Gala Cc: Paul Eggleton; yocto@yoctoproject.org; Rifenbark, Scott M Subject: Re: [yocto] examples / docs on utilizing an external toolchain No, they're generated ad-hoc when needed. Scott, let's regenerate them and talk about a regular generation of them offline. -b On Wed, Aug 3, 2011 at 7:49 AM, Kumar Gala wrote: > > On Aug 3, 2011, at 9:29 AM, Paul Eggleton wrote: > >> On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote: >>> On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote: Bug submitted: http://bugzilla.pokylinux.org/show_bug.cgi?id=1323 My question still stands even w/o it being in formal docs. >>> >>> FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. >>> I'd be interested to know where we've missed the references to it and >>> get to get those references fixed. >> >> git grep tells me we still have it in local.conf.sample in meta-yocto, as >> well >> as in the reference manual. > > Yep, and not sure if the online docs: > > http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html > > are generated nightly or not? > > - k > ___ > 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] Autobuilder issue status
Hi all, Richard requested a summary of the current issues shown up on the autobuilder, here it is: 1. sstate not getting cleared (autobuilder script fix needed - maybe just delete the whole sstate-cache dir?) http://autobuilder.yoctoproject.org:8010/builders/crownbay- noemgd/builds/27/steps/shell/logs/stdio 2. jasperforest and sugarbay need fixing for tune file changes: I have a first-pass patch for this, just a matter of fixing up the machine .conf files for these two layers. http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/29/steps/shell_10/logs/stdio 3. glibc-utils PREFERRED_PROVIDER clash: (There's a patch merged in master for this already) http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/57/steps/shell_6/logs/stdio 4. manifest file missing in sdk build: http://autobuilder.yoctoproject.org:8010/builders/nightly-external- toolchain/builds/52/steps/shell_7/logs/stdio 5. libXinerama missing when building gtk+ Not sure if this is a result of previous errors? http://autobuilder.yoctoproject.org:8010/builders/nightly- internal/builds/50/steps/shell_21/logs/stdio 6. "perl isn't executable!": http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/60/steps/shell_26/logs/stdio 7. -live images still being built: Beth was fixing (has fixed?) this. It did bring up an interesting issue in that -k makes the build look like it succeeded - have filed bug #1322 for this one. http://autobuilder.yoctoproject.org:8010/builders/crownbay- noemgd/builds/27/steps/shell_10/logs/stdio 8. meta-toolchain "/bin/sh" dependency errors: Richard thinks he knows what's wrong here but is unsure of the fix. http://autobuilder.yoctoproject.org:8010/builders/nightly-external- toolchain/builds/55/steps/shell_14/logs/stdio 9. aclocal .m4 file issue (bug #861) Richard has some potential suggestions, actual fix still needed though. http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/60/steps/shell_14/logs/stdio 10. beagleboard libzypp failure Richard has a patch for part of it, would like Mark to look into the rest: http://bugzilla.pokylinux.org/show_bug.cgi?id=1313 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Autobuilder issue status
On 03/08/2011 17:07, Paul Eggleton wrote: Hi all, Richard requested a summary of the current issues shown up on the autobuilder, here it is: 1. sstate not getting cleared (autobuilder script fix needed - maybe just delete the whole sstate-cache dir?) http://autobuilder.yoctoproject.org:8010/builders/crownbay- noemgd/builds/27/steps/shell/logs/stdio 2. jasperforest and sugarbay need fixing for tune file changes: I have a first-pass patch for this, just a matter of fixing up the machine .conf files for these two layers. http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/29/steps/shell_10/logs/stdio 3. glibc-utils PREFERRED_PROVIDER clash: (There's a patch merged in master for this already) http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/57/steps/shell_6/logs/stdio 4. manifest file missing in sdk build: http://autobuilder.yoctoproject.org:8010/builders/nightly-external- toolchain/builds/52/steps/shell_7/logs/stdio 5. libXinerama missing when building gtk+ Not sure if this is a result of previous errors? http://autobuilder.yoctoproject.org:8010/builders/nightly- internal/builds/50/steps/shell_21/logs/stdio 6. "perl isn't executable!": http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/60/steps/shell_26/logs/stdio I have seen possibly a similar issue: libxml-parser-perl failing to compile I tracked it down to two problems: a) using an sstate mirror results in the rpath that's compiled into the native-perl being hardcoded to the full path of whatever built the sstate-cache. The means the compiled in rpath is wrong on any other machine. b) perl MakeMaker is using perl.real instead of the wrapper script, this results in the PERL5LIB variable not being passed in to perl on execution. This in combination with problem A means perl cannot find it's libraries. I would recommend randomising the base directory for autobuilders if they are using an sstate mirror, in order to flush out bugs caused by problem A. I cannot figure out how to fix problem B at the moment and I'll be on holiday soon. So I thought I'd post about this issue before I go. 7. -live images still being built: Beth was fixing (has fixed?) this. It did bring up an interesting issue in that -k makes the build look like it succeeded - have filed bug #1322 for this one. http://autobuilder.yoctoproject.org:8010/builders/crownbay- noemgd/builds/27/steps/shell_10/logs/stdio 8. meta-toolchain "/bin/sh" dependency errors: Richard thinks he knows what's wrong here but is unsure of the fix. http://autobuilder.yoctoproject.org:8010/builders/nightly-external- toolchain/builds/55/steps/shell_14/logs/stdio 9. aclocal .m4 file issue (bug #861) Richard has some potential suggestions, actual fix still needed though. http://autobuilder.yoctoproject.org:8010/builders/nightly- external/builds/60/steps/shell_14/logs/stdio 10. beagleboard libzypp failure Richard has a patch for part of it, would like Mark to look into the rest: http://bugzilla.pokylinux.org/show_bug.cgi?id=1313 Cheers, Paul ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
Several installed scripts set the perl shebang that is too long
which can cause failures on certian older bash versions.
Signed-off-by: Matthew McClintock
---
meta/recipes-devtools/intltool/intltool.inc |2 +-
meta/recipes-devtools/intltool/intltool_0.40.6.bb |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/intltool/intltool.inc
b/meta/recipes-devtools/intltool/intltool.inc
index c934654..d8917ad 100644
--- a/meta/recipes-devtools/intltool/intltool.inc
+++ b/meta/recipes-devtools/intltool/intltool.inc
@@ -12,5 +12,5 @@ RRECOMMENDS_${PN} = "perl-modules"
inherit autotools pkgconfig perlnative
-export PERL_virtclass-native = "/usr/bin/env perl"
+export PERL = "/usr/bin/env perl"
BBCLASSEXTEND = "native"
diff --git a/meta/recipes-devtools/intltool/intltool_0.40.6.bb
b/meta/recipes-devtools/intltool/intltool_0.40.6.bb
index c7938e5..8b52cf8 100644
--- a/meta/recipes-devtools/intltool/intltool_0.40.6.bb
+++ b/meta/recipes-devtools/intltool/intltool_0.40.6.bb
@@ -1,7 +1,7 @@
require intltool.inc
LICENSE="GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-PR = "r3"
+PR = "r4"
SRC_URI_append = " file://intltool-nowarn-0.40.0.patch"
--
1.7.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
On 2011-08-03 10:33, Matthew McClintock wrote:
Several installed scripts set the perl shebang that is too long
which can cause failures on certian older bash versions.
How does the change below correspond to this comment? It's not
clear [at least to me] how changing that environment variable
affects shebang constructs. Can you give a more thorough explanation?
Signed-off-by: Matthew McClintock
---
meta/recipes-devtools/intltool/intltool.inc |2 +-
meta/recipes-devtools/intltool/intltool_0.40.6.bb |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/intltool/intltool.inc
b/meta/recipes-devtools/intltool/intltool.inc
index c934654..d8917ad 100644
--- a/meta/recipes-devtools/intltool/intltool.inc
+++ b/meta/recipes-devtools/intltool/intltool.inc
@@ -12,5 +12,5 @@ RRECOMMENDS_${PN} = "perl-modules"
inherit autotools pkgconfig perlnative
-export PERL_virtclass-native = "/usr/bin/env perl"
+export PERL = "/usr/bin/env perl"
BBCLASSEXTEND = "native"
diff --git a/meta/recipes-devtools/intltool/intltool_0.40.6.bb
b/meta/recipes-devtools/intltool/intltool_0.40.6.bb
index c7938e5..8b52cf8 100644
--- a/meta/recipes-devtools/intltool/intltool_0.40.6.bb
+++ b/meta/recipes-devtools/intltool/intltool_0.40.6.bb
@@ -1,7 +1,7 @@
require intltool.inc
LICENSE="GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
-PR = "r3"
+PR = "r4"
SRC_URI_append = " file://intltool-nowarn-0.40.0.patch"
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Autobuilder issue status
On Wed, Aug 3, 2011 at 9:07 AM, Paul Eggleton wrote: > Hi all, > > Richard requested a summary of the current issues shown up on the autobuilder, > here it is: > > 1. sstate not getting cleared (autobuilder script fix needed - maybe just > delete the whole sstate-cache dir?) > http://autobuilder.yoctoproject.org:8010/builders/crownbay- > noemgd/builds/27/steps/shell/logs/stdio I'll look at this today. > 7. -live images still being built: > Beth was fixing (has fixed?) this. It did bring up an interesting issue in > that > -k makes the build look like it succeeded - have filed bug #1322 for this one. > http://autobuilder.yoctoproject.org:8010/builders/crownbay- > noemgd/builds/27/steps/shell_10/logs/stdio This is a bug in the current buildbot. make reconfig blows up. I'm waiting to bring the builder down and back up once our current nightly is done > Cheers, > Paul Thanks, I'll get this done ASAP -b ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Autobuilder issue status
On Wed, 2011-08-03 at 17:07 +0100, Paul Eggleton wrote: > Richard requested a summary of the current issues shown up on the > autobuilder, > here it is: > > 1. sstate not getting cleared (autobuilder script fix needed - maybe just > delete the whole sstate-cache dir?) > http://autobuilder.yoctoproject.org:8010/builders/crownbay- > noemgd/builds/27/steps/shell/logs/stdio Beth needs to take a look at that one I suspect. > 2. jasperforest and sugarbay need fixing for tune file changes: > I have a first-pass patch for this, just a matter of fixing up the machine > .conf > files for these two layers. > http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/29/steps/shell_10/logs/stdio There is a fix in master to clean up the TARGET_ARCH* variables on x86_64. If we could follow that through into meta-intel it should resolve much of these kinds of issues. > 3. glibc-utils PREFERRED_PROVIDER clash: > (There's a patch merged in master for this already) > http://autobuilder.yoctoproject.org:8010/builders/nightly- > external/builds/57/steps/shell_6/logs/stdio Fix should be in master. > 4. manifest file missing in sdk build: > http://autobuilder.yoctoproject.org:8010/builders/nightly-external- > toolchain/builds/52/steps/shell_7/logs/stdio > > 5. libXinerama missing when building gtk+ > Not sure if this is a result of previous errors? > http://autobuilder.yoctoproject.org:8010/builders/nightly- > internal/builds/50/steps/shell_21/logs/stdio > > 6. "perl isn't executable!": > http://autobuilder.yoctoproject.org:8010/builders/nightly- > external/builds/60/steps/shell_26/logs/stdio I haven't looked at these three. > 7. -live images still being built: > Beth was fixing (has fixed?) this. It did bring up an interesting issue in > that > -k makes the build look like it succeeded - have filed bug #1322 for this one. > http://autobuilder.yoctoproject.org:8010/builders/crownbay- > noemgd/builds/27/steps/shell_10/logs/stdio Beth should have fixed the AB issue? The bug is a lower priority but we'll get to that. I merged the change to make atom-pc generate live images. > 8. meta-toolchain "/bin/sh" dependency errors: > Richard thinks he knows what's wrong here but is unsure of the fix. > http://autobuilder.yoctoproject.org:8010/builders/nightly-external- > toolchain/builds/55/steps/shell_14/logs/stdio Fix should be in master. > 9. aclocal .m4 file issue (bug #861) > Richard has some potential suggestions, actual fix still needed though. > http://autobuilder.yoctoproject.org:8010/builders/nightly- > external/builds/60/steps/shell_14/logs/stdio Fix should be in master. > 10. beagleboard libzypp failure > Richard has a patch for part of it, would like Mark to look into the rest: > http://bugzilla.pokylinux.org/show_bug.cgi?id=1313 Partial fix in master, waiting on the other part from Mark. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Autobuilder issue status
On Wed, Aug 3, 2011 at 9:57 AM, Flanagan, Elizabeth wrote: > On Wed, Aug 3, 2011 at 9:07 AM, Paul Eggleton > wrote: >> Hi all, >> >> Richard requested a summary of the current issues shown up on the >> autobuilder, >> here it is: >> >> 1. sstate not getting cleared (autobuilder script fix needed - maybe just >> delete the whole sstate-cache dir?) >> http://autobuilder.yoctoproject.org:8010/builders/crownbay- >> noemgd/builds/27/steps/shell/logs/stdio > > I'll look at this today. Looked at. This is an issue with ARG_MAX on the host. rming the dir and then doing a mkdir solves it. Which means there is a LOT of files in sstate-cache and it just recently pushed over the ARG_MAX limit (like, a few builds ago). >> 7. -live images still being built: >> Beth was fixing (has fixed?) this. It did bring up an interesting issue in >> that >> -k makes the build look like it succeeded - have filed bug #1322 for this >> one. >> http://autobuilder.yoctoproject.org:8010/builders/crownbay- >> noemgd/builds/27/steps/shell_10/logs/stdio > > This is a bug in the current buildbot. make reconfig blows up. I'm > waiting to bring the builder down and back up once our current nightly > is done And fixed. >> Cheers, >> Paul > > Thanks, I'll get this done ASAP > -b > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/3] meta-intel: crownbay updates
From: Tom Zanussi A few updates for meta-crownbay dealing with the new tune file and live image changes, and a minor cleanup item. Both crownbay and crownbay-emgd live images boot tested successfully. The following changes since commit e2fda0b69db2a93a32cea84a4ece7ba25c20b6c3: Tom Zanussi (1): meta-fri2: add 3g and wifi features are available in the git repository at: git://git.yoctoproject.org/meta-intel.git tzanussi/crownbay-tunelive-updates http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/crownbay-tunelive-updates Tom Zanussi (3): meta-crownbay: remove tune-related assignments from machine conf meta-crownbay: add live fstype meta-crownbay: remove obsolete dir meta-crownbay/conf/machine/crownbay-noemgd.conf|4 +--- meta-crownbay/conf/machine/crownbay.conf |4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) delete mode 100644 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/3] meta-crownbay: remove tune-related assignments from machine conf
From: Tom Zanussi These are all now handled or obsoleted by tune-atom.inc, so remove them here. Signed-off-by: Tom Zanussi --- meta-crownbay/conf/machine/crownbay-noemgd.conf |2 -- meta-crownbay/conf/machine/crownbay.conf|2 -- 2 files changed, 0 insertions(+), 4 deletions(-) diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf index cc0b2eb..315357d 100644 --- a/meta-crownbay/conf/machine/crownbay-noemgd.conf +++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf @@ -4,8 +4,6 @@ #@DESCRIPTION: Machine configuration for Crown Bay systems, without Intel-proprietary graphics bits # i.e. E660 + EG20T -TARGET_ARCH = "i586" - include conf/machine/include/tune-atom.inc MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \ diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf index c66b859..dcdc758 100644 --- a/meta-crownbay/conf/machine/crownbay.conf +++ b/meta-crownbay/conf/machine/crownbay.conf @@ -4,8 +4,6 @@ #@DESCRIPTION: Machine configuration for Crown Bay systems # i.e. E660 + EG20T -TARGET_ARCH = "i586" - include conf/machine/include/tune-atom.inc MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \ -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/3] meta-crownbay: add live fstype
From: Tom Zanussi Most of the time, we want a -live image, so add it to the IMAGE_FSTYPES by default. Signed-off-by: Tom Zanussi --- meta-crownbay/conf/machine/crownbay-noemgd.conf |2 +- meta-crownbay/conf/machine/crownbay.conf|2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf index 315357d..7b8a7f2 100644 --- a/meta-crownbay/conf/machine/crownbay-noemgd.conf +++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf @@ -28,7 +28,7 @@ SERIAL_CONSOLE = "115200 ttyS0" MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts" -IMAGE_FSTYPES ?= "ext3 cpio.gz" +IMAGE_FSTYPES ?= "ext3 cpio.gz live" GLIBC_ADDONS = "nptl" GLIBC_EXTRA_OECONF = "--with-tls" diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf index dcdc758..fd53dbb 100644 --- a/meta-crownbay/conf/machine/crownbay.conf +++ b/meta-crownbay/conf/machine/crownbay.conf @@ -32,7 +32,7 @@ SERIAL_CONSOLE = "115200 ttyS0" MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts" -IMAGE_FSTYPES ?= "ext3 cpio.gz" +IMAGE_FSTYPES ?= "ext3 cpio.gz live" GLIBC_ADDONS = "nptl" GLIBC_EXTRA_OECONF = "--with-tls" -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 3/3] meta-crownbay: remove obsolete dir
From: Tom Zanussi remove recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin, since it's no longer used. Signed-off-by: Tom Zanussi --- 0 files changed, 0 insertions(+), 0 deletions(-) delete mode 100644 meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore diff --git a/meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore b/meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore deleted file mode 100644 index e69de29..000 -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
(Sorry if this get sent twice...)
On Wed, Aug 3, 2011 at 11:44 AM, Gary Thomas wrote:
> On 2011-08-03 10:33, Matthew McClintock wrote:
>>
>> Several installed scripts set the perl shebang that is too long
>> which can cause failures on certian older bash versions.
>
> How does the change below correspond to this comment? It's not
> clear [at least to me] how changing that environment variable
> affects shebang constructs. Can you give a more thorough explanation?
The scripts intltool-{update,etc} installed in sysroot end up having
*really* long shebangs without this change. On older distros this
causes the intltool scripts to just fail usually during the configure
task. intltools recipe itself will
build and install fine. However, when a package that requires
intltool's is being configured they will all fail withing invoking
intltools.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
On 2011-08-03 13:52, McClintock Matthew-B29882 wrote:
(Sorry if this get sent twice...)
On Wed, Aug 3, 2011 at 11:44 AM, Gary Thomas wrote:
On 2011-08-03 10:33, Matthew McClintock wrote:
Several installed scripts set the perl shebang that is too long
which can cause failures on certian older bash versions.
How does the change below correspond to this comment? It's not
clear [at least to me] how changing that environment variable
affects shebang constructs. Can you give a more thorough explanation?
The scripts intltool-{update,etc} installed in sysroot end up having
*really* long shebangs without this change. On older distros this
causes the intltool scripts to just fail usually during the configure
task. intltools recipe itself will
build and install fine. However, when a package that requires
intltool's is being configured they will all fail withing invoking
intltools.
This much was already clear from your explanation - the "what happens and
why it needs fixing" part.
What I don't see is the "why" - why does defining PERL vs PERL_virtclass-native
have this effect?
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [PATCH] Update intltool to set perl shebang correctly for installed tools
On Wed, Aug 3, 2011 at 3:01 PM, Gary Thomas wrote: > What I don't see is the "why" - why does defining PERL vs > PERL_virtclass-native > have this effect? That's an I don't know. -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/2] meta-emenlow: add live fstype
From: Tom Zanussi Most of the time, we want a -live image, so add it to the IMAGE_FSTYPES by default. Signed-off-by: Tom Zanussi --- meta-emenlow/conf/machine/emenlow.conf |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf index dfe20cb..21b314f 100644 --- a/meta-emenlow/conf/machine/emenlow.conf +++ b/meta-emenlow/conf/machine/emenlow.conf @@ -30,7 +30,7 @@ SERIAL_CONSOLE = "115200 ttyS0" MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts" -IMAGE_FSTYPES ?= "ext3 cpio.gz" +IMAGE_FSTYPES ?= "ext3 cpio.gz live" GLIBC_ADDONS = "nptl" GLIBC_EXTRA_OECONF = "--with-tls" -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/2] meta-emenlow: remove tune-related assignments from machine conf
From: Tom Zanussi These are all now handled or obsoleted by tune-atom.inc, so remove them here. Signed-off-by: Tom Zanussi --- meta-emenlow/conf/machine/emenlow.conf |4 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf index b0b7d5e..dfe20cb 100644 --- a/meta-emenlow/conf/machine/emenlow.conf +++ b/meta-emenlow/conf/machine/emenlow.conf @@ -4,12 +4,8 @@ #@DESCRIPTION: Machine configuration for eMenlow based systems, like the # Webs-2120 box. -TARGET_ARCH = "i586" - include conf/machine/include/tune-atom.inc -BASE_PACKAGE_ARCH="core2" - MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \ acpi serial usbgadget" -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/2] meta-intel: emenlow updates
From: Tom Zanussi A couple updates for meta-emenlow dealing with the new tune file and live image changes. Boot tested successfully with the emenlow live sato image. The following changes since commit 567c3b6436b4cb9551c23845c15ab544542b5083: Tom Zanussi (1): meta-crownbay: remove obsolete dir are available in the git repository at: git://git.yoctoproject.org/meta-intel.git tzanussi/emenlow-tunelive-updates http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/emenlow-tunelive-updates Tom Zanussi (2): meta-emenlow: remove tune-related assignments from machine conf meta-emenlow: add live fstype meta-emenlow/conf/machine/emenlow.conf |6 +- 1 files changed, 1 insertions(+), 5 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build failure on recent yocto download
Hi all, I'm not sure where to report this, but I tried again to build Yocto, without success. I downloaded poky-bernard-4.0.tar.bz2, and followed instructions for installing it. I am using 'MACHINE ?= qemuarm' and doing 'bitbake poky-image-sato' bitbake error messages follow below. The first error is a failure to fetch the kernel, and a follow-on failure to do a git-clone on the kernel. I'm behind a firewall and this is a perennial problem for me. Is there another way to get this code? If I do a git-clone on a remote machine and copy it over to my development host, where do I put it? (Why did the first http-based fetch fail, anyway?) Any help would be appreciated. Assuming the second error (a cairo build problem with a mutex) is not a cascade from the first, does anyone have any idea what I should do with this? Possible the failure with libpseudo.so is the start of the problem, but if so, how do I investigate and resolve that? Thanks for any help. -- Tim $ bitbake poky-image-sato Loading cache: 100% |###| ETA: 00:00:00 Loaded 957 entries from dependency cache. Parsing recipes: 100% |#| Time: 00:00:00 Parsing of 783 .bb files complete (749 cached, 34 parsed). 991 targets, 34 skipped, 0 masked, 0 errors. OE Build Configuration: BB_VERSION= "1.11.0" METADATA_BRANCH = "" METADATA_REVISION = "" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "qemuarm" DISTRO= "poky" DISTRO_VERSION= "1.0" TARGET_FPU= "soft" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Running task 1305 of 4708 (ID: 562, /a/home/tbird/work/yocto/poky-bernard-5.0/meta/recipes-kernel/linux/linux-yocto_git.bb, do_fetch) NOTE: Running task 1356 of 4708 (ID: 3657, /a/home/tbird/work/yocto/poky-bernard-5.0/meta/recipes-graphics/cairo/cairo_1.10.2.bb, do_compile) NOTE: package linux-yocto-2.6.37+git1+212cae404e57ff9dc58c808035770d51325c3512_1+233213a1e09eae3de7047ff406b156608788ec17-r16: task do_fetch: Started ERROR: Function 'Fetcher failure for URL: 'git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;nocheckout=1;branch=yocto/standard/arm-versatile-926ejs,meta;name=machine,meta'. Unable to fetch URL git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;nocheckout=1;branch=yocto/standard/arm-versatile-926ejs,meta;name=machine,meta from any source.' failed ERROR: Logfile of failure stored in: /a/home/tbird/work/yocto/poky-5.0-build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto-2.6.37+git1+212cae404e57ff9dc58c808035770d51325c3512_1+233213a1e09eae3de7047ff406b156608788ec17-r16/temp/log.do_fetch.16756 Log data follows: | NOTE: fetch http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz | git.pokylinux.org[0: 140.211.169.125]: errno=Connection refused | fatal: unable to connect a socket (Connection refused) | Cloning into bare repository /a/home/tbird/work/yocto/poky-5.0-build/downloads/git2/git.pokylinux.org.linux-yocto-2.6.37... | ERROR: Function 'Fetcher failure for URL: 'git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;nocheckout=1;branch=yocto/standard/arm-versatile-926ejs,meta;name=machine,meta'. Unable to fetch URL git://git.pokylinux.org/linux-yocto-2.6.37;protocol=git;nocheckout=1;branch=yocto/standard/arm-versatile-926ejs,meta;name=machine,meta from any source.' failed | NOTE: package linux-yocto-2.6.37+git1+212cae404e57ff9dc58c808035770d51325c3512_1+233213a1e09eae3de7047ff406b156608788ec17-r16: task do_fetch: Failed NOTE: package cairo-1.10.2-r0: task do_compile: Started ERROR: Function 'do_compile' failed (see /a/home/tbird/work/yocto/poky-5.0-build/tmp/work/armv5te-poky-linux-gnueabi/cairo-1.10.2-r0/temp/log.do_compile.16757 for further information) ERROR: Logfile of failure stored in: /a/home/tbird/work/yocto/poky-5.0-build/tmp/work/armv5te-poky-linux-gnueabi/cairo-1.10.2-r0/temp/log.do_compile.16757 Log data follows: | NOTE: make -j 6 | make all-recursive | make[1]: Entering directory `/a/home/tbird/work/yocto/poky-5.0-build/tmp/work/armv5te-poky-linux-gnueabi/cairo-1.10.2-r0/cairo-1.10.2' | Making all in src | make[2]: Entering directory `/a/home/tbird/work/yocto/poky-5.0-build/tmp/work/armv5te-poky-linux-gnueabi/cairo-1.10.2-r0/cairo-1.10.2/src' | make all-am | make[3]: Entering directory `/a/home/tbird/work/yocto/poky-5.0-build/tmp/work/armv5te-poky-linux-gnueabi/cairo-1.10.2-r0/cairo-1.10.2/src' | CC cairo-analysis-surface.lo | CC cairo-arc.lo | CC cairo-array.lo | CC cairo-atomic.lo | CC cairo-base64-stream.lo | CC cairo-base85-stream.lo | ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot
Re: [yocto] Build failure on recent yocto download
On 08/03/2011 05:08 PM, Tim Bird wrote: > Hi all, > > I'm not sure where to report this, but I tried again to build > Yocto, without success. > > I downloaded poky-bernard-4.0.tar.bz2, and followed instructions > for installing it. Silly me. poky-bernard-5.0.tar.bz2 -- Tim = Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
> -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Tim Bird > Sent: Wednesday, August 03, 2011 5:11 PM > To: yocto@yoctoproject.org > Subject: Re: [yocto] Build failure on recent yocto download > > On 08/03/2011 05:08 PM, Tim Bird wrote: > > Hi all, > > > > I'm not sure where to report this, but I tried again to build Yocto, > > without success. > > > > I downloaded poky-bernard-4.0.tar.bz2, and followed instructions for > > installing it. > Silly me. poky-bernard-5.0.tar.bz2 > -- Tim Hey Tim - couple of things - The current release is http://autobuilder.yoctoproject.org/downloads/poky/poky-bernard-5.0.1.tar.bz2 - so I would hope you might try 5.0.1 instead of 5.0. The other thing is that we could use a little more detail on what distro & version you are trying this on and what problem you had... Thanks. :-) > = > Tim Bird > Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff > Engineer, Sony Network Entertainment > = > > ___ > 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] Build failure on recent yocto download
On Wed, 2011-08-03 at 17:08 -0700, Tim Bird wrote: > Hi all, > > I'm not sure where to report this, but I tried again to build > Yocto, without success. > > I downloaded poky-bernard-4.0.tar.bz2, and followed instructions > for installing it. > > I am using 'MACHINE ?= qemuarm' and doing 'bitbake poky-image-sato' > > bitbake error messages follow below. > > The first error is a failure to fetch the kernel, and a follow-on > failure to do a git-clone on the kernel. I'm behind a firewall and > this is a perennial problem for me. Is there another way to get this > code? If I do a git-clone on a remote machine and copy it over to > my development host, where do I put it? (Why did the first http-based > fetch fail, anyway?) Any help would be appreciated. We seem to be missing the kernel tarball on our sources mirror... Let me try and chase that. Regards, Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
On Wed, 2011-08-03 at 17:40 -0700, Joshua Lock wrote: > On Wed, 2011-08-03 at 17:08 -0700, Tim Bird wrote: > > Hi all, > > > > I'm not sure where to report this, but I tried again to build > > Yocto, without success. > > > > I downloaded poky-bernard-4.0.tar.bz2, and followed instructions > > for installing it. > > > > I am using 'MACHINE ?= qemuarm' and doing 'bitbake poky-image-sato' > > > > bitbake error messages follow below. > > > > The first error is a failure to fetch the kernel, and a follow-on > > failure to do a git-clone on the kernel. I'm behind a firewall and > > this is a perennial problem for me. Is there another way to get this > > code? If I do a git-clone on a remote machine and copy it over to > > my development host, where do I put it? (Why did the first http-based > > fetch fail, anyway?) Any help would be appreciated. > > We seem to be missing the kernel tarball on our sources mirror... Let me > try and chase that. Chased and caught: joshual@scimitar:~/mess/31 $ wget http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz --2011-08-03 17:50:18-- http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz Resolving autobuilder.yoctoproject.org... 140.211.169.118 Connecting to autobuilder.yoctoproject.org|140.211.169.118|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 449232265 (428M) [application/x-gzip] Saving to: `git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz.1' Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
Tim, On Wed, 2011-08-03 at 17:08 -0700, Tim Bird wrote: > The first error is a failure to fetch the kernel, and a follow-on > failure to do a git-clone on the kernel. I'm behind a firewall and > this is a perennial problem for me. We have a Spartan page on the project wiki trying to collect the required setup information for users on controlled networks. Perhaps it can help you get further? https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy Regards, Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
On Wednesday, August 03, 2011 05:08:43 PM Tim Bird wrote: > | from cairo-scaled-font-private.h:45, > | from cairoint.h:380, > | > | from cairo-arc.c:37: > | cairo-mutex-impl-private.h:262:3: error: #error "XXX: No mutex > | implementation found. Cairo will not work with multiple > | threads. Define CAIRO_NO_MUTEX to 1 to acknowledge and accept this > | limitation > and compile cairo without thread-safety support." > > | In file included from cairo-mutex-type-private.h:45:0, > | > | from cairo-scaled-font-private.h:45, > | from cairoint.h:380, > | > | from cairo-arc.c:37: > | cairo-mutex-impl-private.h:271:30: error: expected '=', ',', ';', 'asm' > | or '__attribute__' before 'cairo_recursive_mutex_impl_t' In file > | included from cairo-scaled-font-private.h:45:0, > | > | from cairoint.h:380, > | > | from cairo-arc.c:37: > | cairo-mutex-type-private.h:49:3: error: #error "CAIRO_MUTEX_IMPL_LOCK > | not defined. Check cairo-mutex-impl-private.h." > | cairo-mutex-type-private.h:52:3: error: #error "CAIRO_MUTEX_IMPL_UNLOCK > | not defined. Check cairo-mutex-impl-private.h." > | cairo-mutex-type-private.h:55:3: error: #error > | "CAIRO_MUTEX_IMPL_NIL_INITIALIZER not defined. Check > | cairo-mutex-impl-private.h." cairo-mutex-type-private.h:139:3: error: > | #error "CAIRO_MUTEX_IMPL_LOCK not defined" > | cairo-mutex-type-private.h:142:3: error: #error > | "CAIRO_MUTEX_IMPL_UNLOCK not defined" cairo-mutex-type-private.h:151:3: > | error: #error "CAIRO_MUTEX_IMPL_NIL_INITIALIZER not defined" > | cairo-mutex-type-private.h:161:28: error: expected '=', ',', ';', 'asm' > | or '__attribute__' before 'cairo_mutex_t' > | cairo-mutex-type-private.h:162:38: error: expected '=', ',', ';', 'asm' > | or '__attribute__' before 'cairo_recursive_mutex_t' In file included > | from cairoint.h:380:0, > | > | from cairo-arc.c:37: > | cairo-scaled-font-private.h:108:5: error: expected > | specifier-qualifier-list before 'cairo_mutex_t' In file included from > | cairo-mutex-type-private.h:45:0, > | > | from cairo-scaled-font-private.h:45, > | from cairoint.h:380, > | > | from cairo-base64-stream.c:39: > | cairo-mutex-impl-private.h:262:3: error: #error "XXX: No mutex > | implementation found. Cairo will not work with multiple > | threads. Define CAIRO_NO_MUTEX to 1 to acknowledge and accept this > | limitation > and compile cairo without thread-safety support." hmmm this error means you dont have libc headers installed properly. Seems something is broken in your environment. Its probably using some tools from your build system which are not quite in line with what configure wanted Can you post the config.log of cairo somewhere ? -- Khem Raj ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
On 8/3/2011 5:50 PM, Joshua Lock wrote: On Wed, 2011-08-03 at 17:40 -0700, Joshua Lock wrote: On Wed, 2011-08-03 at 17:08 -0700, Tim Bird wrote: Hi all, I'm not sure where to report this, but I tried again to build Yocto, without success. I downloaded poky-bernard-4.0.tar.bz2, and followed instructions for installing it. I am using 'MACHINE ?= qemuarm' and doing 'bitbake poky-image-sato' bitbake error messages follow below. The first error is a failure to fetch the kernel, and a follow-on failure to do a git-clone on the kernel. I'm behind a firewall and this is a perennial problem for me. Is there another way to get this code? If I do a git-clone on a remote machine and copy it over to my development host, where do I put it? (Why did the first http-based fetch fail, anyway?) Any help would be appreciated. We seem to be missing the kernel tarball on our sources mirror... Let me try and chase that. Chased and caught: joshual@scimitar:~/mess/31 $ wget http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz --2011-08-03 17:50:18-- http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz Resolving autobuilder.yoctoproject.org... 140.211.169.118 Connecting to autobuilder.yoctoproject.org|140.211.169.118|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 449232265 (428M) [application/x-gzip] Saving to: `git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz.1' Thanks very much. I'll give it another try. I've visited the "behind a proxy" help page before. I guess I should have checked that for an update before asking. -- Tim ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build failure on recent yocto download
On 8/3/2011 5:33 PM, Stewart, David C wrote: The current release is http://autobuilder.yoctoproject.org/downloads/poky/poky-bernard-5.0.1.tar.bz2 - so I would hope you might try 5.0.1 instead of 5.0. OK - I'll see if I have time to try again. I was following the instructions at: http://www.yoctoproject.org/docs/yocto-quick-start/yocto-project-qs.html You might want to update that, or add instructions there for checking for the latest version. The other thing is that we could use a little more detail on what distro& version you are trying this on and what problem you had... Thanks. :-) I'm guessing you missed my first message. But I should have added my distro. It is Fedora 12 (which is old, I know, but I've prepared it for Yocto use previously). Anyway, I think Joshua's response should resolve the issue. Thanks! :-) -- Tim ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Update intltool to set perl shebang correctly for installed tools
On Wed, Aug 3, 2011 at 11:44 AM, Gary Thomas wrote:
> On 2011-08-03 10:33, Matthew McClintock wrote:
>>
>> Several installed scripts set the perl shebang that is too long
>> which can cause failures on certian older bash versions.
>
> How does the change below correspond to this comment? It's not
> clear [at least to me] how changing that environment variable
> affects shebang constructs. Can you give a more thorough explanation?
The scripts intltool-{update,etc} installed in sysroot end up having
*really* long shebangs without this change. On older distros this
causes the intltool scripts to just fail. intltools recipe itself will
build and install fine. However, when a package that requires
intltool's is being configured they will all fail withing invoking
intltools.
-M
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
