Re: [yocto] RPM Packaging
Hi Prashant, This is wrong window to ask generic question. //Gaurang On Thu, Mar 26, 2015 at 12:51 PM, Prasant J pj0...@gmail.com wrote: Hi, I want to create custom rpm packages for the iMX6Q device (cortexa9hf-vfp-neon-mx6). I have to create two types of packages: either pre-built arm binaries to be packed or packages containing only bash scripts. There is no need of cross-compiling while packaging for my cases. I'm building the packages on my Ubuntu system. When I specify - BuildArch: cortexa9hf-vfp-neon-mx6, and try to create a package (rpmbuild -ba SPECS/foo.spec), it complains error: No compatible architectures found for build. For my case: rpm does not need to cross-compile but just do the packaging. How can I force rpm to believe the architecture that I'm specifying? Any inputs will be of help. Regards, Pj -- ___ 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] Hi..trouble booting
Hi I have been having a boot issue on my system. Here is a Paste from the machine im trying to boot linux. Its running Slackware at the moment. When I boot with a USB stick it says boot : followed by alpha symbols that seems to continue into eternity unless stopped. I have used DD on the hddimg files and i have tried using Rufus and TuxBoot with both hddimg and ISO files. bash-4.2# lscpu Architecture: i686 CPU op-mode(s):32-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 28 Stepping: 2 CPU MHz: 800.000 BogoMIPS: 3200.12 L1d cache: 24K L1i cache: 32K L2 cache: 512K NUMA node0 CPU(s): 0,1 I have used the normal Genericx86 and the Atom yocto build from the Yocto website with no luck. Can anybody help me with this issue? Thansk allot and kind regards Testo -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] GCC 4.9 to 5.0
On Wed, Mar 25, 2015 at 11:38 AM, Khem Raj raj.k...@gmail.com wrote: On Mar 25, 2015, at 9:28 AM, Victor Rodriguez vm.ro...@gmail.com wrote: HI everyone Does anybody knows if there is a best known method/plan/test suite for moving from one version of gcc to another ? we generate cross testing driver in the build tree for gcc-cross which should help in running the dejagnu in cross env. Unfortunately it has stopped working after libgcc was separated out. So it might need some fix. but you should see cross-testgcc script generated in build tree. Thanks a lot for the help .. I am not doing cross compiling. However all these help is really appreciated Regards I am in the middle of that painful task and wonder if yocto community has a plan every time yocto do this switch Thanks a lot for all the help Regards Victor Rodriguez -- ___ 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] [YOCTO]: About adding documentation in final SDK image
Hi Preeti,
On 03/19/2015 09:07 AM, Preeti P wrote:
Hi all,
I am working on adding the documents in to my SDK image.
Basically, I want to have the man and info documentation for the tool-chain
item in my SDK image.
As per my understanding, the install package for every recipe gets split
into different packages and finally shipped in to the SDK image.
To add the documents in my SDK image, I tried to add the '-doc' support in
'PACKAGES' variable but still the documentation related files are not there
in the final image.
I even tried by adding below lines in to the do_install function in my
recipe but my final image does not have those files:
do_install {
install -d ${D}${includedir}${doc}
install -m 644 ${S}/doc/*.info ${D}${includedir}${doc}
}
Can anyone provide me inputs on how to add the documentation for packages
in to the final SDK image?
I'm not sure whether you want them in the host sysroot or the target sysroot,
but will either TOOLCHAIN_HOST_TASK or TOOLCHAIN_TARGET_TASK do what you need?
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-TOOLCHAIN_HOST_TASK
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-TOOLCHAIN_TARGET_TASK
Thanks,
Preeti
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] nightly-arch*.conf: Add GetBitbakeVersion build step
[YOCTO #7519]
Add the GetBitbakeVersion build step to nightly-arch*.conf buildsets
in buildset_config.controller to enable toaster on autobuilder.
Signed-off-by: Graydon, Tracy tracy.gray...@intel.com
---
buildset-config.controller/nightly-arm-lsb.conf | 2 ++
buildset-config.controller/nightly-arm.conf | 2 ++
buildset-config.controller/nightly-arm64.conf | 1 +
buildset-config.controller/nightly-fsl-arm-lsb.conf | 3 +++
buildset-config.controller/nightly-fsl-arm.conf | 3 +++
buildset-config.controller/nightly-fsl-ppc-lsb.conf | 1 +
buildset-config.controller/nightly-fsl-ppc.conf | 1 +
buildset-config.controller/nightly-mips-lsb.conf| 2 ++
buildset-config.controller/nightly-mips.conf| 2 ++
buildset-config.controller/nightly-ppc-lsb.conf | 2 ++
buildset-config.controller/nightly-ppc.conf | 2 ++
buildset-config.controller/nightly-x86-64-lsb.conf | 2 ++
buildset-config.controller/nightly-x86-64.conf | 2 ++
buildset-config.controller/nightly-x86-lsb.conf | 2 ++
buildset-config.controller/nightly-x86.conf | 2 ++
15 files changed, 29 insertions(+)
diff --git a/buildset-config.controller/nightly-arm-lsb.conf
b/buildset-config.controller/nightly-arm-lsb.conf
index 261a1e3..1101803 100644
--- a/buildset-config.controller/nightly-arm-lsb.conf
+++ b/buildset-config.controller/nightly-arm-lsb.conf
@@ -15,8 +15,10 @@ steps: [{'SetDest':{}},
'distro': 'poky-lsb', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky-lsb'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev
core-image-lsb-sdk core-image-lsb-qt3'}},
{'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' : 'i686',
'distro': 'poky-lsb'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-sdk'}},
{'SyncPersistDB' : {'commit' : True, 'distro':'poky-lsb'}},
{'PublishLayerTarballs':{}},
diff --git a/buildset-config.controller/nightly-arm.conf
b/buildset-config.controller/nightly-arm.conf
index d705bbc..0ff654c 100644
--- a/buildset-config.controller/nightly-arm.conf
+++ b/buildset-config.controller/nightly-arm.conf
@@ -14,9 +14,11 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'qemuarm', 'SDKMACHINE' : 'i686',
'distro': 'poky', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
{'RunSanityTests': {'images': 'core-image-minimal core-image-sato
core-image-sato-sdk'}},
{'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' : 'i686',
'distro': 'poky'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
{'CreateAutoConf': {'machine': 'qemuarm', 'SDKMACHINE' : 'i686',
'distro': 'poky', 'buildhistory' : False}},
{'BuildToolchainImages': {}},
diff --git a/buildset-config.controller/nightly-arm64.conf
b/buildset-config.controller/nightly-arm64.conf
index 9595b3b..0b15ec8 100644
--- a/buildset-config.controller/nightly-arm64.conf
+++ b/buildset-config.controller/nightly-arm64.conf
@@ -14,6 +14,7 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' :'i686',
'distro': 'poky', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
{'RunSanityTests': {'images': 'core-image-minimal core-image-sato
core-image-sato-sdk'}},
{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' : 'i686',
'distro': 'poky', 'buildhistory' : False}},
diff --git a/buildset-config.controller/nightly-fsl-arm-lsb.conf
b/buildset-config.controller/nightly-fsl-arm-lsb.conf
index cccb7a1..5820cbb 100644
--- a/buildset-config.controller/nightly-fsl-arm-lsb.conf
+++ b/buildset-config.controller/nightly-fsl-arm-lsb.conf
@@ -19,16 +19,19 @@ steps: [{'SetDest':{}},
'atextprepend': 'ACCEPT_FSL_EULA = 1\n',
'devkernel' : False}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer' : True,
'bspprovider' : 'fsl-arm'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev
core-image-lsb-sdk core-image-lsb-qt3'}},
{'CreateAutoConf': {'machine': 'imx6qsabresd', 'SDKMACHINE' : 'x86_64',
Re: [yocto] Hi..trouble booting
On March 26, 2015 9:05:25 AM EDT, testlaster testlas...@gmail.com wrote: Hi I have been having a boot issue on my system. Here is a Paste from the machine im trying to boot linux. Its running Slackware at the moment. When I boot with a USB stick it says boot : followed by alpha symbols that seems to continue into eternity unless stopped. I have used DD on the hddimg files and i have tried using Rufus and TuxBoot with both hddimg and ISO files. bash-4.2# lscpu Architecture: i686 CPU op-mode(s):32-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 28 Stepping: 2 CPU MHz: 800.000 BogoMIPS: 3200.12 L1d cache: 24K L1i cache: 32K L2 cache: 512K NUMA node0 CPU(s): 0,1 I have used the normal Genericx86 and the Atom yocto build from the Yocto website with no luck. Can anybody help me with this issue? Thansk allot and kind regards Testo Testo, If you can send me either the dmesg or the kernel logs output from the hanging system I may be able to trace your issue. Nick -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Sharing sstate
I have two development servers, one running an older version of Fedora (x86 *), the other runs a recent Ubuntu (x86_64). Both are the same CPU core (Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz) I've just tried building the same target, using the same version of Poky/Yocto, sharing the sstate cache (fully populated) from the x86_64 machine with the x86 machine. This was done using HTTP. Sadly, there was not a single file found in the cache that could be used. Should this not be expected to work? Does sstate cache only work across like systems (32 vs 64 bit hosts)? Also, Mark Hatle mentioned a few days ago that there are ways to lock versions of the sstate cache. I still haven't found any info/documentation on this. Can someone please explain more? Thanks (*) I can't update my x86 machine to a more recent (x86_64) distribution as I have many older projects that only run on that hardware and no time/opportunity to upgrade, hence my desire to share in this manner. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Question about git tarballs
I built from Poky/Yocto master on 2015-02-22. I always create new tarballs from downloaded trees if they have changed BB_GENERATE_MIRROR_TARBALLS = 1 and I stash them in my local mirror. On that date, glibc had just been updated to version 2.21 so it made sense that the tarball was updated. Since that date, I've done dozens of [full] builds for my various platforms. The glibc recipe has not been touched (at least not the git revision) since then. However, the tarball for its git repository has been refetched/rebuilt a number of times and it seems pretty hit-or-miss. For example a build on 2015-03-03 changed the tarball but one just two days later did not. Is there any sense to this? If the downloaded git+tarball contains the desired revision, why would it be re-downloaded and rebuilt? Sadly, I'm not sure I can give a good recipe for causing the behaviour to happen so the problem can be examined in detail. Note: this behaviour seems to be limited to only a few git trees. These are most often being touched although I suspect the underlying git tree is not: git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz git2_sourceware.org.git.glibc.git.tar.gz ... very confused -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RPM Packaging
Hi, I want to create custom rpm packages for the iMX6Q device (cortexa9hf-vfp-neon-mx6). I have to create two types of packages: either pre-built arm binaries to be packed or packages containing only bash scripts. There is no need of cross-compiling while packaging for my cases. I'm building the packages on my Ubuntu system. When I specify - BuildArch: cortexa9hf-vfp-neon-mx6, and try to create a package (rpmbuild -ba SPECS/foo.spec), it complains error: No compatible architectures found for build. For my case: rpm does not need to cross-compile but just do the packaging. How can I force rpm to believe the architecture that I'm specifying? Any inputs will be of help. Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [PATCH 4/4] romley: remove common video and media config items
-Original Message- From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- boun...@yoctoproject.org] On Behalf Of Saul Wold Sent: Wednesday, March 25, 2015 1:36 AM To: linux-yocto@yoctoproject.org Cc: Haw Foo Chien; dvh...@linux.intel.com Subject: [linux-yocto] [PATCH 4/4] romley: remove common video and media config items These are already included via the media-all in common-pc Cc: Haw Foo Chien foo.chien@intel.com Signed-off-by: Saul Wold s...@linux.intel.com Acked-by: Ong Boon Leong boon.leong@intel.com -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] [YOCTO]: About adding documentation in final SDK image
Hi all,
Any inputs on below mail?
Regards,
Preeti
On 3/19/15, Preeti P itspreeti...@gmail.com wrote:
Hi all,
I am working on adding the documents in to my SDK image.
Basically, I want to have the man and info documentation for the tool-chain
item in my SDK image.
As per my understanding, the install package for every recipe gets split
into different packages and finally shipped in to the SDK image.
To add the documents in my SDK image, I tried to add the '-doc' support in
'PACKAGES' variable but still the documentation related files are not there
in the final image.
I even tried by adding below lines in to the do_install function in my
recipe but my final image does not have those files:
do_install {
install -d ${D}${includedir}${doc}
install -m 644 ${S}/doc/*.info ${D}${includedir}${doc}
}
Can anyone provide me inputs on how to add the documentation for packages
in to the final SDK image?
Thanks,
Preeti
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
