[yocto] Force nostamp from recipe
Hi I have a recipe using externalsrc, and with the version of poky I'm running, it nostamps do_compile. Can I force other nostamp tasks from my recipe? E.g. do_configure? I'm building this recipe for one MACHINE and then rerun the compilation for another MACHINE. The recipe is setup to build for tune, which is equal. The latter run fails linking because it's referring to the first machine's sysroot, not the second. This would have been fixed if the second run would call the do_configure task. Best regards, Svein -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build a toolchain compiler with ARM hard-float support
Hi, I'm using Poky Jethro to build on Toradex Colibri-T20 (armv7). I want to build my own SDK Installer to have a toolchain and a sysroot. Currently, I realied that the toolchain installer files do not provide an arm-poky-linux-gnuabi compiler with hard-float support. For example, while compiling my project: /opt/poky/2.0.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/include/gnu/stubs.h:10:29: fatal error: gnu/stubs-hard.h: No such file or directory Therefore: How to be sure that the compiler generated by "bitbake -c populate_sdk" will support hard-float ? Is there a configuration file ? Karim -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cgl][PATCH] resource-agents: 3.9.6 -> 3.9.7
On tor, 2016-09-22 at 01:45 +, Wang, Xin wrote:
> ping
>
> -Original Message-
> From: Wang, Xin/王 鑫
> Sent: Thursday, September 01, 2016 12:24 PM
> To: yocto@yoctoproject.org
> Cc: Wang, Xin/王 鑫
> Subject: [yocto][meta-cgl][PATCH] resource-agents: 3.9.6 -> 3.9.7
>
> Upgrade resource-agents from 3.9.6 to 3.9.7.
>
> Signed-off-by: Wang Xin
> ---
> .../{resource-agents_3.9.6.bb => resource-agents_3.9.7.bb}| 4
> ++--
> 1 file changed, 2 insertions(+), 2 deletions(-) rename
> meta-cgl-common/recipes-cgl/cluster-resource-agents/{resource-agents_3.9.6.bb
> => resource-agents_3.9.7.bb} (95%)
>
> diff --git
> a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
>
> b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
> similarity index 95%
> rename from
> meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
> rename to
> meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.7.bb
> index 18ef1e8..a0d4e1f 100644
> ---
> a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_3.9.6.bb
> +++ b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agent
> +++ s_3.9.7.bb
> @@ -20,8 +20,8 @@ SRC_URI =
> "https://codeload.github.com/ClusterLabs/resource-agents/tar.gz/v${PV}
> file://03-fix-header-defs-lookup.patch \
>"
>
> -SRC_URI[md5sum] = "6873d5a217aee3026193fb85bfa18a4a"
> -SRC_URI[sha256sum] =
> "39722cdee68ff96d06788f05f325bd21ec2fc59c59d847e5e4b23c6df23bf678"
> +SRC_URI[md5sum] = "c59096b1bacc704e8a5a285f15729109"
> +SRC_URI[sha256sum] =
> "e5bd62658fbc236acb83b709f64b2cd9fae52aa4a420a44fed5eb667e928b152"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
> file://COPYING.LGPL;md5=4fbd65380cdd255951079008b364516c
> \
> --
> 2.7.4
>
>
>
Hi Wang
This patch has already been merged to master
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-cgl/commit/?id=7b0cd876eb215335a9fa6bfdfd0f0cfd14fbf2b9)
as well as the other two.
Cheers,
--Adrian
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build a toolchain compiler with ARM hard-float support
On Thu, 2016-09-29 at 09:10 +, Karim ATIKI wrote: > Hi, > > I'm using Poky Jethro to build on Toradex Colibri-T20 (armv7). > > I want to build my own SDK Installer to have a toolchain and a > sysroot. > > Currently, I realied that the toolchain installer files do not > provide an arm-poky-linux-gnuabi compiler with hard-float support. > For example, while compiling my project: > > /opt/poky/2.0.1/sysroots/armv7a-vfp-neon-poky-linux- > gnueabi/usr/include/gnu/stubs.h:10:29: fatal error: gnu/stubs-hard.h: > No such file or directory > > Therefore: > > How to be sure that the compiler generated by "bitbake -c > populate_sdk" will support hard-float ? Is there a configuration file > ? You need to choose a MACHINE which uses hard-float. Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Force nostamp from recipe
Hi, do_configure[noexec] = "1" http://www.crashcourse.ca/wiki/index.php/BitBake_task_flags On Thu, Sep 29, 2016 at 10:23 AM, Svein Seldal wrote: > Hi > > I have a recipe using externalsrc, and with the version of poky I'm > running, it nostamps do_compile. > > Can I force other nostamp tasks from my recipe? E.g. do_configure? > > I'm building this recipe for one MACHINE and then rerun the compilation > for another MACHINE. The recipe is setup to build for tune, which is equal. > The latter run fails linking because it's referring to the first machine's > sysroot, not the second. This would have been fixed if the second run would > call the do_configure task. > > > Best regards, > Svein > -- > ___ > 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] Force nostamp from recipe
Hi, Sorry it should be: do_configure[nostamp] = "1" Br, Chris Z On Thu, Sep 29, 2016 at 2:29 PM, Chris Z. wrote: > Hi, > > do_configure[noexec] = "1" > > > > http://www.crashcourse.ca/wiki/index.php/BitBake_task_flags > > On Thu, Sep 29, 2016 at 10:23 AM, Svein Seldal wrote: > >> Hi >> >> I have a recipe using externalsrc, and with the version of poky I'm >> running, it nostamps do_compile. >> >> Can I force other nostamp tasks from my recipe? E.g. do_configure? >> >> I'm building this recipe for one MACHINE and then rerun the compilation >> for another MACHINE. The recipe is setup to build for tune, which is equal. >> The latter run fails linking because it's referring to the first machine's >> sysroot, not the second. This would have been fixed if the second run would >> call the do_configure task. >> >> >> Best regards, >> Svein >> -- >> ___ >> 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 a toolchain compiler with ARM hard-float support
On 9/29/16 5:31 AM, Richard Purdie wrote: > On Thu, 2016-09-29 at 09:10 +, Karim ATIKI wrote: >> Hi, >> >> I'm using Poky Jethro to build on Toradex Colibri-T20 (armv7). >> >> I want to build my own SDK Installer to have a toolchain and a >> sysroot. >> >> Currently, I realied that the toolchain installer files do not >> provide an arm-poky-linux-gnuabi compiler with hard-float support. >> For example, while compiling my project: >> >> /opt/poky/2.0.1/sysroots/armv7a-vfp-neon-poky-linux- >> gnueabi/usr/include/gnu/stubs.h:10:29: fatal error: gnu/stubs-hard.h: >> No such file or directory >> >> Therefore: >> >> How to be sure that the compiler generated by "bitbake -c >> populate_sdk" will support hard-float ? Is there a configuration file >> ? > > You need to choose a MACHINE which uses hard-float. The machine configuration file should be setting the 'DEFAULTTUNE' variable to an appropriate ISA and ABI (hard float) for your configuration. If it is not, you may have to create your own variant and change the DEFAULTTUNE setting -- assuming the board supports the necessary hard float components. (And yes, there are some armv7a variants that people removed the VFP instructions from -- even though it's theoretically against spec.) --Mark > Cheers, > > Richard > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build a toolchain compiler with ARM hard-float support
Thanks for your feeback. I've attempted to generate the sdk (populate_sdk) having only MACHINE=colibri-t20 in the local.conf. Fortunately, the generated installer has all the necessary features with hard-float support. Karim De : Mark Hatle Envoyé : jeudi 29 septembre 2016 15:17 À : Richard Purdie; Karim ATIKI; yocto Objet : Re: [yocto] build a toolchain compiler with ARM hard-float support On 9/29/16 5:31 AM, Richard Purdie wrote: > On Thu, 2016-09-29 at 09:10 +, Karim ATIKI wrote: >> Hi, >> >> I'm using Poky Jethro to build on Toradex Colibri-T20 (armv7). >> >> I want to build my own SDK Installer to have a toolchain and a >> sysroot. >> >> Currently, I realied that the toolchain installer files do not >> provide an arm-poky-linux-gnuabi compiler with hard-float support. >> For example, while compiling my project: >> >> /opt/poky/2.0.1/sysroots/armv7a-vfp-neon-poky-linux- >> gnueabi/usr/include/gnu/stubs.h:10:29: fatal error: gnu/stubs-hard.h: >> No such file or directory >> >> Therefore: >> >> How to be sure that the compiler generated by "bitbake -c >> populate_sdk" will support hard-float ? Is there a configuration file >> ? > > You need to choose a MACHINE which uses hard-float. The machine configuration file should be setting the 'DEFAULTTUNE' variable to an appropriate ISA and ABI (hard float) for your configuration. If it is not, you may have to create your own variant and change the DEFAULTTUNE setting -- assuming the board supports the necessary hard float components. (And yes, there are some armv7a variants that people removed the VFP instructions from -- even though it's theoretically against spec.) --Mark > Cheers, > > Richard > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] missing glxext.h header file in core-image-x11 // toolchain SDK
hi, I have generated a core-image-x11 image for a Toradex Colibri T20 board. I aim to compile and execute our application that normally runs under X11 + OpenGL. I'm not an expert of X11 and gles technologies. Therefore, I need to have the necessary libraries in the linux image I have generated. I have therefore added in my local.conf: DISTRO_FEATURES_append = "opengl" In order to compile our application, I have generated the respective toolchain with bitbake -c populate_sdk core-image-x11. It worked fine as well. But as I launched the makefiles, I got some ...xxx.cpp :188:25: fatal error: GL/glxext.h: No such file or directory #include Indeed, I have no glxext.h file in the generated toolchain sdk, neither in the sysroots. In my sysroot, I have only: ./GL ??? glxint.h ??? glxmd.h ??? glxproto.h ??? glxtokens.h ??? internal ??? glcore.h ./GLES ??? egl.h ??? glext.h ??? gl.h ??? glplatform.h ./GLES2 ??? gl2ext.h ??? gl2.h ??? gl2platform.h So, I suppose that something is missing in the features of my core-image-x11 (and subsequently in the respective toolchain). Should I add something in some features ? Cheers, Karim -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] missing glxext.h header file in core-image-x11 // toolchain SDK
On 29 September 2016 at 15:46, Karim ATIKI wrote: > I have generated a core-image-x11 image for a Toradex Colibri T20 board. > I aim to compile and execute our application that normally runs under X11 > + OpenGL. > What sort of GPU does this board have, and what GL drivers are you using? Mesa ships a glxext.h but the choice of GL stack is generally BSP-specific so this is entirely down to what your BSP's GL stack is doing. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-security][PATCH] scapy: upgrade to 2.3.2
On 09/28/2016 10:38 PM, jackie.hu...@windriver.com wrote:
From: Jackie Huang
* update the SRC_URI since it's been moved
from bitbucket to github.
* add ptest support
Merged.
thanks,
Armin
Signed-off-by: Jackie Huang
---
recipes-security/scapy/scapy/run-ptest| 4
recipes-security/scapy/{scapy_2.3.1.bb => scapy_2.3.2.bb} | 15 +++
2 files changed, 15 insertions(+), 4 deletions(-)
create mode 100755 recipes-security/scapy/scapy/run-ptest
rename recipes-security/scapy/{scapy_2.3.1.bb => scapy_2.3.2.bb} (71%)
diff --git a/recipes-security/scapy/scapy/run-ptest
b/recipes-security/scapy/scapy/run-ptest
new file mode 100755
index 000..91b29f9
--- /dev/null
+++ b/recipes-security/scapy/scapy/run-ptest
@@ -0,0 +1,4 @@
+#!/bin/sh
+UTscapy -t regression.uts -f text -l -C \
+-o @PTEST_PATH@/scapy_ptest_$(date +%Y%m%d-%H%M%S).log \
+2>&1 | sed -e 's/^passed None/PASS:/' -e 's/^failed None/FAIL:/'
diff --git a/recipes-security/scapy/scapy_2.3.1.bb
b/recipes-security/scapy/scapy_2.3.2.bb
similarity index 71%
rename from recipes-security/scapy/scapy_2.3.1.bb
rename to recipes-security/scapy/scapy_2.3.2.bb
index d8c731b..0a42ad9 100644
--- a/recipes-security/scapy/scapy_2.3.1.bb
+++ b/recipes-security/scapy/scapy_2.3.2.bb
@@ -5,12 +5,19 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
-SRC_URI = "https://bitbucket.org/secdev/${PN}/downloads/${BP}.zip";
+SRC_URI =
"https://github.com/secdev/${BPN}/archive/v${PV}.tar.gz;downloadfilename=${BP}.tar.gz
\
+ file://run-ptest \
+"
-SRC_URI[md5sum] = "a30d828e59801d1d092219b349f1da9e"
-SRC_URI[sha256sum] =
"8972c02e39a826a10c02c2bdd5025f7251dce9589c57befd9bb55c65f02e4934"
+SRC_URI[md5sum] = "00f11df3d6b46fe6ac306efd757486f9"
+SRC_URI[sha256sum] =
"1b8a86d687feb8ed01114c0c016b428674cbfec04e3eb6f5249a018c427c4f6a"
-inherit setuptools
+inherit setuptools ptest
+
+do_install_ptest() {
+install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
+sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
+}
RDEPENDS_${PN} = "tcpdump python-subprocess python-compression python-netclient \
python-netserver python-pydoc python-pkgutil python-shell \
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] new system booting directly to halt
I've been working on setting up a poky distro on an older intel XScale system, and I finally got a working kernel and root filesystem. However, when I boot the box it zips through runlevel 5, then halts. It seems to me like maybe init isn't kicking off getty or some sort of interactive login. Has anyone else run into this problem? I'll post the boot output below. -Max Bootloader Initialization Successful. Copyright (c) 2010 InHand Electronics (www.inhand.com) FT4: Fingertip4 v.0A211004 (Oct 21 2010, 10:04:57) IBL: InHandBoot_4.9 BETA v.0A211004 (Oct 21 2010, 10:04:19) CPLD Version: 5.10 DRAM Size: 128 MBytes SRAM Size: 240 KBytes IBC Start Page:/nor/512 Platform Post-Init ac97 Autorun '/cf/autoexec.brc' '/cf/autoexec.brc' not found Autorun '/sd/autoexec.brc' '/sd/autoexec.brc' not found Autorun '/nor/config.brc' >> bootlin Starting Linux Copying image (2689792 bytes) to RAM: 0xa0008000 Copying file /nor/zImage to /ram/os Source File: 2689792 bytes Destination Space:4194304 bytes Copying 2689792 bytes pct remaining time --- - - 100%0 0:00 Copied 2689792B (3MB) Setting up Kernel tags at: 0xa100 Kernel tags used 36 bytes Disabling MMU Jumping to Linux kernel @ 0xa0008000 Uncompressing Linux... done, booting the kernel. [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 3.14.4 (m...@tsunami.pacs.agpea.army.mil) (gcc version 4.9.2 (GCC) ) #1 PREEMPT Wed Sep 28 16:29:41 EDT 2016 [0.00] CPU: XScale-PXA270 [69054118] revision 8 (ARMv5TE), cr=397f [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: InHand Fingertip4 Development Platform (aka FT4) [0.00] Memory policy: Data cache writeback [0.00] BUG: mapping for 0x at 0xff00 out of vmalloc space [0.00] Run Mode clock: 208.00MHz (*16) [0.00] Turbo Mode clock: 520.00MHz (*2.5, active) [0.00] Memory clock: 208.00MHz (/2) [0.00] System bus clock: 208.00MHz [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock0 rw rootfstype=jffs2 mem=64M earlyprintk=serial,ttyS0,115200 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Memory: 59616K/65536K available (3732K kernel code, 184K rwdata, 1132K rodata, 139K init, 94K bss, 5920K reserved) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xc480 - 0xff00 ( 936 MB) [0.00] lowmem : 0xc000 - 0xc400 ( 64 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc04c83fc (4865 kB) [0.00] .init : 0xc04c9000 - 0xc04ebcd4 ( 140 kB) [0.00] .data : 0xc04ec000 - 0xc051a180 ( 185 kB) [0.00].bss : 0xc051a18c - 0xc0531b90 ( 95 kB) [0.00] Preemptible hierarchical RCU implementation. [0.00] NR_IRQS:16 nr_irqs:304 304 [0.46] sched_clock: 32 bits at 3250kHz, resolution 307ns, wraps every 1321528397516ns [0.000691] Console: colour dummy device 80x30 [0.000769] Calibrating delay loop... 518.55 BogoMIPS (lpj=2592768) [0.060347] pid_max: default: 32768 minimum: 301 [0.060594] Security Framework initialized [0.060741] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.060774] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.062150] CPU: Testing write buffer coherency: ok [0.063287] Setting up static identity map for 0xa038e6d8 - 0xa038e744 [0.069844] NET: Registered protocol family 16 [0.071694] DMA: preallocated 256 KiB pool for atomic coherent allocations [0.095946] Configure Fingertip4... [0.188992] bio: create slab at 0 [0.197249] usbcore: registered new interface driver usbfs [0.198138] usbcore: registered new interface driver hub [0.199246] usbcore: registered new device driver usb [0.210323] cfg80211: Calling CRDA to update world regulatory domain [0.211077] Switched to clocksource oscr0 [0.282781] NET: Registered protocol family 2 [0.284302] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.284382] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.284426] TCP: Hash tables configured (established 1024 bind 1024) [0.284648] TCP: reno registered [0.284673] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.284717] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.285236] NET: Registered protocol family 1 [0.286343] RPC: Registered named UNIX
Re: [yocto] new system booting directly to halt
You could sell this as a very secure box ;) Kidding aside, it didn't "zip" through runlevel 5, in fact, you don't know what runlevel it is actually in. 11 seconds after your file system is mounted, a reboot is issued. From your trace, nothing running in userspace displayed any messages to the console. You didn't mention what type of init system you are using, systemd or sysV. It almost looks like a console problem. But...i don't know why a reboot would be issued. That's not normal behavior if you simply have a min-configured console. Maybe init will do that under certain circumstances, I am not sure. Just for FYI, notice that your serial port is instantiating on ttyS0. (I do see that agrees with your kernel command line so at least that much is correct.) First thing I would try is to see if I can get anything on userspace. Try using init= on your kernel command line to just spawn a shell. (init=/bin/sh) Do you have a way to examine the flash after a reboot to see if a syslog was populated on the file system and examine its contents? ie JTAG? Make sure your root file system is sane, ie mount it on a development box and make sure it's contents make sense to you. ie for sysV /sbin/init should point to init, and it should contain a /etc/inittab and that should have sane contents, etc. For systemd, /sbin/init should point (possibly through /etc/alternatives) to a systemd executable. You get the idea. Good luck, Chris On Thu, Sep 29, 2016 at 3:18 PM, Maxwell Bottiger < sleepyli...@jive-turkey.net> wrote: > I've been working on setting up a poky distro on an older intel XScale > system, and I finally got a working kernel and root filesystem. However, > when I boot the box it zips through runlevel 5, then halts. It seems to me > like maybe init isn't kicking off getty or some sort of interactive login. > Has anyone else run into this problem? I'll post the boot output below. > > -Max > > Bootloader Initialization Successful. > Copyright (c) 2010 InHand Electronics (www.inhand.com) > FT4: Fingertip4 v.0A211004 (Oct 21 2010, 10:04:57) > IBL: InHandBoot_4.9 BETA v.0A211004 (Oct 21 2010, 10:04:19) > > CPLD Version: 5.10 > DRAM Size: 128 MBytes > SRAM Size: 240 KBytes > IBC Start Page:/nor/512 > > Platform Post-Init > ac97 > > Autorun '/cf/autoexec.brc' > '/cf/autoexec.brc' not found > > Autorun '/sd/autoexec.brc' > '/sd/autoexec.brc' not found > > Autorun '/nor/config.brc' > >> bootlin > Starting Linux > Copying image (2689792 bytes) to RAM: 0xa0008000 > > Copying file /nor/zImage to /ram/os > Source File: 2689792 bytes > Destination Space:4194304 bytes > > Copying 2689792 bytes > pct remaining time > --- - - > 100%0 0:00 > Copied 2689792B (3MB) > Setting up Kernel tags at: 0xa100 > Kernel tags used 36 bytes > Disabling MMU > Jumping to Linux kernel @ 0xa0008000 > Uncompressing Linux... done, booting the kernel. > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Linux version 3.14.4 (m...@tsunami.pacs.agpea.army.mil) > (gcc version 4.9.2 (GCC) ) #1 PREEMPT Wed Sep 28 16:29:41 EDT 2016 > [0.00] CPU: XScale-PXA270 [69054118] revision 8 (ARMv5TE), > cr=397f > [0.00] CPU: VIVT data cache, VIVT instruction cache > [0.00] Machine: InHand Fingertip4 Development Platform (aka FT4) > [0.00] Memory policy: Data cache writeback > [0.00] BUG: mapping for 0x at 0xff00 out of vmalloc > space > [0.00] Run Mode clock: 208.00MHz (*16) > [0.00] Turbo Mode clock: 520.00MHz (*2.5, active) > [0.00] Memory clock: 208.00MHz (/2) > [0.00] System bus clock: 208.00MHz > [0.00] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 16256 > [0.00] Kernel command line: console=ttyS0,115200 > root=/dev/mtdblock0 rw rootfstype=jffs2 mem=64M earlyprintk=serial,ttyS0, > 115200 > [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) > [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 > bytes) > [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) > [0.00] Memory: 59616K/65536K available (3732K kernel code, 184K > rwdata, 1132K rodata, 139K init, 94K bss, 5920K reserved) > [0.00] Virtual kernel memory layout: > [0.00] vector : 0x - 0x1000 ( 4 kB) > [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) > [0.00] vmalloc : 0xc480 - 0xff00 ( 936 MB) > [0.00] lowmem : 0xc000 - 0xc400 ( 64 MB) > [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) > [0.00] .text : 0xc0008000 - 0xc04c83fc (4865 kB) > [0.00] .init : 0xc04c9000 - 0xc04ebcd4 ( 140 kB) > [0.00] .data : 0xc04ec000 - 0xc051a180 ( 185 kB) > [0.00].bss : 0xc051a18c - 0xc0531b90 ( 95 kB) > [0.00] Preemptible hierar
[yocto] [PATCH] Build sets to test new OS distribution in autobuilder
Signed-off-by: Monserrat Sedeno
---
nightly-qa-distro.conf | 45 +
1 file changed, 21 insertions(+), 24 deletions(-)
diff --git a/nightly-qa-distro.conf b/nightly-qa-distro.conf
index 2d2c828..8529345 100644
--- a/nightly-qa-distro.conf
+++ b/nightly-qa-distro.conf
@@ -7,9 +7,6 @@ repos: [{'poky':
{'meta-qt4':
{'repourl':'git://git.yoctoproject.org/meta-qt4',
'branch':'master'}},
-{'meta-qt4':
-{'repourl':'git://git.yoctoproject.org/meta-qt4',
- 'branch':'master'}},
{'meta-qt3':
{'repourl':'git://git.yoctoproject.org/meta-qt3',
'branch':'master'}}]
@@ -20,28 +17,28 @@ props: [{'fp_date':{'prop_type':'StringParameter',
steps: [{'SetDest':{}},
{'CheckOutLayers': {}},
{'RunPreamble': {}},
-{'TriggerBuilds': {'schedulerName': 'main-build',
+{'TriggerBuilds': {'schedulerName': 'dist-build',
'waitForFinish': 'True',
'schedulerNames': {
- 'nightly-oe-selftest': {},
- 'nightly-rpm': {}
- 'nightly-deb':{}
- 'nightly-ipk':{}
- 'nightly-world': {},
- 'buildtools': {},
- 'nightly-arm': {},
- 'nightly-mips': {},
- 'nightly-wic':{},
- 'nightly-multilib': {},
- 'nightly-x86-64': {},
- 'nightly-x86-64-lsb': {},
- 'nightly-x86': {},
- 'poky-tiny': {},
- 'nightly-qa-systemd': {},
- 'nightly-qa-extras': {},
- 'nightly-qa-targetbuilds': {},
- 'nightly-qa-logrotate': {},
- 'nightly-qa-pam': {},
- 'nightly-qa-skeleton': {}},
+ 'nightly-oe-selftest': {},
+ 'nightly-rpm': {},
+ 'nightly-deb': {},
+ 'nightly-ipk': {},
+ 'nightly-world': {},
+ 'buildtools': {},
+ 'nightly-arm': {},
+ 'nightly-mips': {},
+ 'nightly-wic':{},
+ 'nightly-multilib': {},
+ 'nightly-x86-64': {},
+ 'nightly-x86-64-lsb': {},
+ 'nightly-x86': {},
+ 'poky-tiny': {},
+ 'nightly-qa-systemd': {},
+ 'nightly-qa-extras': {},
+ 'nightly-qa-targetbuilds': {},
+ 'nightly-qa-logrotate': {},
+ 'nightly-qa-pam': {},
+ 'nightly-qa-skeleton': {}},
'schedulerNames_nowait': {}}},]
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
