Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Fri, Aug 29, 2014 at 4:59 PM, Khem Raj wrote: > On Fri, Aug 29, 2014 at 5:18 AM, Richard Purdie > wrote: >> On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: >>> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: >>> > reproduced. will apprise as I have some fix. >>> >>> OK pushed another patch to the contrib tree that should take care of both >>> xf86-input-synaptics xf86-input-vmmouse >> >> https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/17/steps/BuildImages/logs/stdio >> >> xf86-video-imxfb has the same issue and will need the same fix. Otavio >> cc'd... >> > > I have sent a patch to meta-fsl-arm for this Until its installed, the patch is here http://patchwork.openembedded.org/patch/79443/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Fri, Aug 29, 2014 at 5:01 PM, Khem Raj wrote: > On Fri, Aug 29, 2014 at 3:39 AM, Richard Purdie > wrote: >> On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: >>> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: >>> > reproduced. will apprise as I have some fix. >>> >>> OK pushed another patch to the contrib tree that should take care of both >>> xf86-input-synaptics xf86-input-vmmouse >> >> Thanks. I'm having one heck of a problem unentangling all the different >> build failures (from these and other patches) but this one looks like >> glibc: >> >> https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/18/steps/BuildImages/logs/stdio >> > > Trying to reproduce it locally. Once I have, I will update. > Richard I have fixed this too and pushed the updates to same pull tree. Please give it another whirl -Khem -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Fri, Aug 29, 2014 at 3:39 AM, Richard Purdie wrote: > On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: >> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: >> > reproduced. will apprise as I have some fix. >> >> OK pushed another patch to the contrib tree that should take care of both >> xf86-input-synaptics xf86-input-vmmouse > > Thanks. I'm having one heck of a problem unentangling all the different > build failures (from these and other patches) but this one looks like > glibc: > > https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/18/steps/BuildImages/logs/stdio > Trying to reproduce it locally. Once I have, I will update. > Cheers, > > Richard > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Fri, Aug 29, 2014 at 5:20 AM, Richard Purdie wrote: > On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: >> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: >> > reproduced. will apprise as I have some fix. >> >> OK pushed another patch to the contrib tree that should take care of both >> xf86-input-synaptics xf86-input-vmmouse > > Also, meta-fsl-ppc fails: > > https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/17/steps/BuildImages/logs/stdio > > with a do_compile glibc failure. I have fixed this. The patchset is updated on the contrib tree. > > Cheers, > > Richard > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Fri, Aug 29, 2014 at 5:18 AM, Richard Purdie wrote: > On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: >> On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: >> > reproduced. will apprise as I have some fix. >> >> OK pushed another patch to the contrib tree that should take care of both >> xf86-input-synaptics xf86-input-vmmouse > > https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/17/steps/BuildImages/logs/stdio > > xf86-video-imxfb has the same issue and will need the same fix. Otavio > cc'd... > I have sent a patch to meta-fsl-arm for this > Cheers, > > Richard > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] tripwire: ppc64 build failure.
| configure: error: /bin/sh ./config.sub powerpc64-poky-linux failed
config.sub did not understand the powerpc64 par.
this patch adds that understanding.
Signed-off-by: Armin Kuster
---
.../tripwire/files/tripwire_add_ppc64.patch| 36 ++
recipes-security/tripwire/tripwire_2.4.2.2.bb | 1 +
2 files changed, 37 insertions(+)
create mode 100644 recipes-security/tripwire/files/tripwire_add_ppc64.patch
diff --git a/recipes-security/tripwire/files/tripwire_add_ppc64.patch
b/recipes-security/tripwire/files/tripwire_add_ppc64.patch
new file mode 100644
index 000..374e9ed
--- /dev/null
+++ b/recipes-security/tripwire/files/tripwire_add_ppc64.patch
@@ -0,0 +1,36 @@
+tripwire:
+
+Powerpc64 is not supported in the current tripwier release.
+
+ configure: error: /bin/sh ./config.sub powerpc64-poky-linux failed
+ | Configure failed. The contents of all config.log files follows to aid
debugging
+
+Submitted upstream to Tripwire devel mailing list
+
+http://sourceforge.net/p/tripwire/mailman/message/32776415/
+
+Signed-off-By: Armin Kuster
+
+
+Index: tripwire-2.4.2.2-src/config.sub
+===
+--- tripwire-2.4.2.2-src.orig/config.sub
tripwire-2.4.2.2-src/config.sub
+@@ -233,7 +233,7 @@ case $basic_machine in
+ | alpha | alphaev[4-8] | alphaev56 | alphapca5[67] \
+ | alphaev6[78] \
+ | we32k | ns16k | clipper | i370 | sh | sh[34] \
+- | powerpc | powerpcle |
++ | powerpc | powerpcle | powerpc64 \
+ | 1750a | dsp16xx | pdp10 | pdp11 \
+ | mips16 | mips64 | mipsel | mips64el \
+ | mips64orion | mips64orionel | mipstx39 | mipstx39el \
+@@ -280,7 +280,7 @@ case $basic_machine in
+ | we32k-* | cydra-* | ns16k-* | pn-* | np1-* | xps100-* \
+ | clipper-* | orion-* \
+ | sparclite-* | pdp10-* | pdp11-* | sh-* | sh[34]-* | sh[34]eb-* \
+-| powerpc-* | powerpcle-* | sparc64-* | sparcv9-* | sparcv9b-* |
sparc86x-* \
++| powerpc-* | powerpcle-* | powerpc64-* | sparc64-* | sparcv9-* |
sparcv9b-* | sparc86x-* \
+ | mips16-* | mips64-* | mipsel-* \
+ | mips64el-* | mips64orion-* | mips64orionel-* \
+ | mips64vr4100-* | mips64vr4100el-* | mips64vr4300-* |
mips64vr4300el-* \
diff --git a/recipes-security/tripwire/tripwire_2.4.2.2.bb
b/recipes-security/tripwire/tripwire_2.4.2.2.bb
index ad5363d..b9dc01c 100644
--- a/recipes-security/tripwire/tripwire_2.4.2.2.bb
+++ b/recipes-security/tripwire/tripwire_2.4.2.2.bb
@@ -13,6 +13,7 @@ SRC_URI =
"${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}-src/${BPN}-${PV}/${BPN}-$
file://twcfg.txt \
file://twinstall.sh \
file://twpol-yocto.txt \
+ file://tripwire_add_ppc64.patch \
"
SRC_URI[md5sum] = "2462ea16fb0b5ae810471011ad2f2dd6"
SRC_URI[sha256sum] =
"e09a7bdca9302e704cc62067399e0b584488f825b0e58c82ad6d54cd2e899fad"
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-docs] should I be able to make the docs without warnings?
Hello, I'm thinking about chasing down some of the warnings I see when I make the docs (pdf) in yocto-docs. However, it's not clear to me whether the warnings I get are to be expected or can be configured out. I don't see that the auto builder is used to build the docs. Therefore, can someone please point me to a known good log or at least let me know that I should be able to make the docs without warnings. Thanks, Bob -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is there a list of yocto-supported dev kits somewhere?
Am 29.08.2014 18:01, schrieb Robert P. J. Day: > On Fri, 29 Aug 2014, Rudolf Streif wrote: > >> I think this is a great idea and I volunteer to help with the effort. >> >> that is kinda what i was after. i realize it's an open-ended >> request, but it would be great if there was a list of "recommended" >> dev kits representing various architectures/processors that people new >> to YP could purchase for experimentation, *knowing* that those dev >> kits had a YP build that would work out of the box. not necessarily >> technically complete, but that it would just boot and let them start >> playing. >> >> The "work out of the box" part is the tricky one. Unfortunately, >> many YP BSP layers do not include instructions on what to do after >> the build has completed. If you don't know what to do with boot >> loader and kernel images, flattened device tree files, root file >> system archives and images then you are at a loss. Commonly the >> boards also require a special boot media partitioning and the like. > > exactly true, but without that final bit of information, i contend > that the YP build is utterly useless unless the developer is told what > to do with the final image objects. > >> While this type of info should be in the BSP readme files I think it >> would be good to have step by step instructions that gets one from >> setting up the build environment to building and creating bootable >> media for each board. > > and those step-by-step instructions don't need to be terribly > verbose. remember, you're not trying to explain how to use YP; you're > simply summarizing what it takes to get it running on a particular dev > kit. all of that should fit on a single page at most. > Robert Nelson has a good collection for ARM-Devkits in his eewiki: https://eewiki.net/display/linuxonarm/Home Maybe that could be a good starting point. > rday > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is there a list of yocto-supported dev kits somewhere?
On Fri, 29 Aug 2014, Rudolf Streif wrote: > I think this is a great idea and I volunteer to help with the effort. > > that is kinda what i was after. i realize it's an open-ended > request, but it would be great if there was a list of "recommended" > dev kits representing various architectures/processors that people new > to YP could purchase for experimentation, *knowing* that those dev > kits had a YP build that would work out of the box. not necessarily > technically complete, but that it would just boot and let them start > playing. > > The "work out of the box" part is the tricky one. Unfortunately, > many YP BSP layers do not include instructions on what to do after > the build has completed. If you don't know what to do with boot > loader and kernel images, flattened device tree files, root file > system archives and images then you are at a loss. Commonly the > boards also require a special boot media partitioning and the like. exactly true, but without that final bit of information, i contend that the YP build is utterly useless unless the developer is told what to do with the final image objects. > While this type of info should be in the BSP readme files I think it > would be good to have step by step instructions that gets one from > setting up the build environment to building and creating bootable > media for each board. and those step-by-step instructions don't need to be terribly verbose. remember, you're not trying to explain how to use YP; you're simply summarizing what it takes to get it running on a particular dev kit. all of that should fit on a single page at most. 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] is there a list of yocto-supported dev kits somewhere?
I think this is a great idea and I volunteer to help with the effort. > that is kinda what i was after. i realize it's an open-ended > request, but it would be great if there was a list of "recommended" > dev kits representing various architectures/processors that people new > to YP could purchase for experimentation, *knowing* that those dev > kits had a YP build that would work out of the box. not necessarily > technically complete, but that it would just boot and let them start > playing. > The "work out of the box" part is the tricky one. Unfortunately, many YP BSP layers do not include instructions on what to do after the build has completed. If you don't know what to do with boot loader and kernel images, flattened device tree files, root file system archives and images then you are at a loss. Commonly the boards also require a special boot media partitioning and the like. While this type of info should be in the BSP readme files I think it would be good to have step by step instructions that gets one from setting up the build environment to building and creating bootable media for each board. Cheers, Rudi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: > On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: > > reproduced. will apprise as I have some fix. > > OK pushed another patch to the contrib tree that should take care of both > xf86-input-synaptics xf86-input-vmmouse Also, meta-fsl-ppc fails: https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/17/steps/BuildImages/logs/stdio with a do_compile glibc failure. Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: > On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: > > reproduced. will apprise as I have some fix. > > OK pushed another patch to the contrib tree that should take care of both > xf86-input-synaptics xf86-input-vmmouse https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/17/steps/BuildImages/logs/stdio xf86-video-imxfb has the same issue and will need the same fix. Otavio cc'd... Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bitbake svn fetch download folder conflicts
On Fri, Aug 29, 2014 at 1:22 PM, Thomas Roos wrote: > Hi, I have several recipes checkout from one svn repo (same and other > subfolders) - there are sometimes svn command conflicts. I guess it's > because all svn data is stored in ONE FOLDER eg. > downloads/svn/ip/reponame/folder and concurred svn command instances > access this folder at the same time. > Is there an solution for this?For instance an parameter to specify a > tmp folder for an svn repo. Or global option to store svn repos > locally by recipe names they used in. > any help would be wonderful! > thank you, cheers Thomas > > P.S: think of same svn subfolders with different revisions as well!!! not a very helpful answer... but i have faced the same issue and just created artificial dependencies to avoid the 2 fetch tasks to run concurrently... e.g. if x.bb and y.bb both fetch from same SVN repo, in y.bb: do_fetch[depends] += "x:do_fetch" it's a poor's man workaround... but that might help.. cheers -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] bitbake svn fetch download folder conflicts
Hi, I have several recipes checkout from one svn repo (same and other subfolders) - there are sometimes svn command conflicts. I guess it's because all svn data is stored in ONE FOLDER eg. downloads/svn/ip/reponame/folder and concurred svn command instances access this folder at the same time. Is there an solution for this?For instance an parameter to specify a tmp folder for an svn repo. Or global option to store svn repos locally by recipe names they used in. any help would be wonderful! thank you, cheers Thomas P.S: think of same svn subfolders with different revisions as well!!! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is there a list of yocto-supported dev kits somewhere?
On Thu, 28 Aug 2014, Jeff Osier-Mixon wrote: > I think the machines list is a great start, http://layers.openembedded.org/layerindex/branch/master/machines/?q= > but it really lists actual machines, not dev kits. There isn't any > way to see immediately from that list which are $99 dev boards and > which are $ reference kits from the manufacturers. I think > Robert is right that a list of inexpensive YP-supported boards would > be extremely useful. I'll try to create such a list in the near > future. that is kinda what i was after. i realize it's an open-ended request, but it would be great if there was a list of "recommended" dev kits representing various architectures/processors that people new to YP could purchase for experimentation, *knowing* that those dev kits had a YP build that would work out of the box. not necessarily technically complete, but that it would just boot and let them start playing. and as i once suggested (and jefro clearly appreciates), at this point, dev kits like that should rarely cost more than a couple hundred dollars. 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] [OE-core] [RFT] Moving on from eglibc to glibc 2.20
On Thu, 2014-08-28 at 18:46 -0700, Khem Raj wrote: > On Thu, Aug 28, 2014 at 5:41 PM, Khem Raj wrote: > > reproduced. will apprise as I have some fix. > > OK pushed another patch to the contrib tree that should take care of both > xf86-input-synaptics xf86-input-vmmouse Thanks. I'm having one heck of a problem unentangling all the different build failures (from these and other patches) but this one looks like glibc: https://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/18/steps/BuildImages/logs/stdio Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
