Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
On 16/11/2013 16:24, Jack lemon wrote: > Hi everybody, > > I worked with P1022DS-PB and then designed my custom board according to its > documents. For sd card I adjust u-boot to 115200 baud rate and compile it > with ELDK independently. However in Nor-flash we haven't u-boot.bin > independently. For Nor-Flash I need to adjust baud rate in .ext2.gz.u-boot > image, because for Nor-Flash only kernel,rootfs,dtb files are needed. > How can I modify u-boot in fsl-image-minimal-p1022ds.ext2.gz.u-boot for > adjusting baud rate to 115200? Is it not enough to add SERIAL_CONSOLE = "115200 ttyS0" (or which serial you use as console) to your machine conf ? Best regards, Stefano Babic -- = DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
Stefano Babic writes: > Is it not enough to add SERIAL_CONSOLE = "115200 ttyS0" (or which serial > you use as console) to your machine conf ? > > Best regards, > Stefano Babic > Thank you Stefano for your reply. Does it not any need to edit u-boot source code? just adding SERIAL_CONSOLE = "115200 ttyS0" to local.conf? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
On 19/11/2013 10:59, Jack Lemon wrote: > Stefano Babic writes: > > >> Is it not enough to add SERIAL_CONSOLE = "115200 ttyS0" (or which serial >> you use as console) to your machine conf ? >> >> Best regards, >> Stefano Babic >> > > Thank you Stefano for your reply. > Does it not any need to edit u-boot source code? just adding SERIAL_CONSOLE > = "115200 ttyS0" to local.conf? You asked to change your rootfs (initrd, I presume) fsl-image-minimal-p1022ds.ext2.gz.u-boot, and setting SERIAL_CONSOLE adjusts the parameters for inittab. If you want to change u-boot as well (but this is outside fsl-image-minimal-*) and you do not want to compile it outside Yocto, you have to put the patch you already have in your bsp directory and adjust your u-boot receipe. Best regards Stefano Babic -- = DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
On Tue, 19 Nov 2013, Jack Lemon wrote: > Stefano Babic writes: > > > > Is it not enough to add SERIAL_CONSOLE = "115200 ttyS0" (or which serial > > you use as console) to your machine conf ? > > > > Best regards, > > Stefano Babic > > > > Thank you Stefano for your reply. > Does it not any need to edit u-boot source code? just adding SERIAL_CONSOLE > = "115200 ttyS0" to local.conf? the current documentation states that SERIAL_CONSOLE has been deprecated in favour of the newer SERIAL_CONSOLES: http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-SERIAL_CONSOLE rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
Stefano Babic writes: > > On 19/11/2013 10:59, Jack Lemon wrote: > > Stefano Babic ...> writes: > > > > > >> Is it not enough to add SERIAL_CONSOLE = "115200 ttyS0" (or which serial > >> you use as console) to your machine conf ? > >> > >> Best regards, > >> Stefano Babic > >> > > > > Thank you Stefano for your reply. > > Does it not any need to edit u-boot source code? just adding SERIAL_CONSOLE > > = "115200 ttyS0" to local.conf? > > You asked to change your rootfs (initrd, I presume) > fsl-image-minimal-p1022ds.ext2.gz.u-boot, and setting SERIAL_CONSOLE > adjusts the parameters for inittab. > > If you want to change u-boot as well (but this is outside > fsl-image-minimal-*) and you do not want to compile it outside Yocto, > you have to put the patch you already have in your bsp directory and > adjust your u-boot receipe. > > Best regards > Stefano Babic > For Nor-Flash we have only three files(kernel,rootfs,dtb). Where is u-boot? I think it is inside the fsl-image-minimal-p1022ds.ext2.gz.u-boot rootfs file. Is it true? So, for modifying u-boot to adujst serial boaudrate, I understand that I can add SERIAL_CONSOLE = "115200 ttyS0" to my local.conf according to your reply and it doesnt need to modify u-boot source code. Am I in the right place? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
Hi Jack, On 19/11/2013 12:25, Jack wrote: > For Nor-Flash we have only three files(kernel,rootfs,dtb). Where is u-boot? > I think it is inside the fsl-image-minimal-p1022ds.ext2.gz.u-boot rootfs > file. Is it true? I do not think so, but you are the best to answer this question: unzip the file and check inside. However, even if it contains a u-boot.bin or whatever is your u-boot file, you have to extract it to write the bootloader at the right address. In most cases, you will see a separate image for u-boot in tmp/deploy/images diurectory. > > So, for modifying u-boot to adujst serial boaudrate, No. To modify the serial console under linux. > I understand that I can > add SERIAL_CONSOLE = "115200 ttyS0" to my local.conf according to your reply See Robert reply. SERIAL_CONSOLE is deprecated, uses SERIAL_CONSOLES instead. > and it doesnt need to modify u-boot source code. > > Am I in the right place? Mmmhh..there is something missing. Usually you have a separate file for u-boot. Of course, if u-boot is part of the filesystem, you cannot use for a first installation because u-boot must be copied at a specific address. Best regards, Stefano Babic -- = DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de = ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cloud-services][PATCH] erlang: skip the host library path check to fix cross-compile issue
Thanks for the patch!
A couple of requests.
Can you list the compile issue here ? i.e. just a bit of the error
message showing it clearly. Someone else searching for a problem will
find it very useful!
On 13-11-19 05:27 AM, Zhenhua Luo wrote:
Signed-off-by: Zhenhua Luo
---
.../erlang/erlang-fix-build-issue-in-Yocto.patch | 25 ++
.../recipes-devtools/erlang/erlang_R15B.bb | 2 ++
2 files changed, 27 insertions(+)
create mode 100644
meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
diff --git
a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
new file mode 100644
index 000..2d4b7b5
--- /dev/null
+++
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
@@ -0,0 +1,25 @@
+Upstream-Status: Inappropriate [The fix is specific to Yocto build env]
+
+Skip host library path check to fix following Yocto insane check issue:
+ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
+Rerun configure task after fixing this.
+
+Signed-off-by: Zhenhua Luo
+
+--- otp_src_R15B/erts/configure.in.orig2011-12-14 04:22:11.0
-0600
otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -0600
+@@ -1469,10 +1469,10 @@
+ # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
+ ])
+fi
+- LDFLAGS="-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS"
+- unset -v try_dlpi_lib
+- AC_MSG_NOTICE([Extending the search to include /lib])
+- AC_CHECK_LIB(dlpi, dlpi_open)
++# LDFLAGS="-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS"
++# unset -v try_dlpi_lib
++# AC_MSG_NOTICE([Extending the search to include /lib])
++# AC_CHECK_LIB(dlpi, dlpi_open)
+if test x"$ac_cv_lib_dlpi_dlpi_open" = x"no"; then
+ LDFLAGS="$save_ldflags"
+fi
diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
index 68d144b..8d8e28b 100644
--- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
+++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
@@ -9,6 +9,7 @@ EXTRA_OEMAKE = "BUILD_CC='${BUILD_CC}'"
EXTRA_OECONF = "--with-ssl=${STAGING_DIR_HOST}${layout_exec_prefix}"
+EXTRA_OECONF_append_powerpc = " --disable-smp-support --disable-hipe"
This should be a separate patch. Can you split the commit and send
this as a two part series ?
Bruce
EXTRA_OECONF_append_arm = " --disable-smp-support --disable-hipe"
EXTRA_OECONF_append_armeb = " --disable-smp-support --disable-hipe"
EXTRA_OECONF_append_mipsel = " --disable-smp-support --disable-hipe"
@@ -55,5 +56,6 @@ FILES_${PN}-staticdev += "${libdir}/*/*/*/*.a
${libdir}/*/*/*/*/*.a ${libdir}/*/
FILES_${PN}-libs-dbg += " ${libdir}/erlang/*/.debug ${libdir}/erlang/*/*/.debug
${libdir}/erlang/*/*/*/.debug ${libdir}/erlang/*/*/*/*/.debug
${libdir}/erlang/*/*/*/*/*/.debug "
+SRC_URI += "file://erlang-fix-build-issue-in-Yocto.patch"
SRC_URI[md5sum] = "dd6c2a4807551b4a8a536067bde31d73"
SRC_URI[sha256sum] =
"5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Compile on recipe works the second time
All, I'm on poky/dylan-9.0.1 and I've created a layer for a separate open source project to include in my image. The layer is at https://github.com/evensonbryan/meta-bacnet for those of you who want to try and duplicate my results. Just add this layer to your setup and build the recipe "bacnet-stack". I have a very odd build issue. The first time I build the recipe, the build fails during the compile step. However, if I then build the recipe again, the compile completes without errors. For example: 1. bitbake -c clean bacnet-stack 2. bitbake bacnet-stack (compile fails) 3. bitbake bacnet-stack (compile succeeds, rest of image packaging works) Additionally, the following order compiles without error: 1. bitbake -c clean bacnet-stack 2. bitbake -c devshell bacnet-stack 3. (from devshell) make all (compile succeeds) This project is divided into a static library and multiple demo applications. The static library needs to be built first, and then the demo applications include the static library in their build. I suspect I have an issue with either populating the static library or the related include files in the sysroot which causes the demo applications to fail to build the first time but work the second. However, I can't figure out how to fix the issue. Any pointers on what is setup wrong with this recipe? Thanks, Bryan ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Compile on recipe works the second time
Hi Bryan,
On Tuesday 19 November 2013 08:57:40 Bryan Evenson wrote:
> I'm on poky/dylan-9.0.1 and I've created a layer for a separate open source
> project to include in my image. The layer is at
> https://github.com/evensonbryan/meta-bacnet for those of you who want to
> try and duplicate my results. Just add this layer to your setup and build
> the recipe "bacnet-stack".
>
> I have a very odd build issue. The first time I build the recipe, the build
> fails during the compile step. However, if I then build the recipe again,
> the compile completes without errors. For example:
>
> 1. bitbake -c clean bacnet-stack
> 2. bitbake bacnet-stack (compile fails)
> 3. bitbake bacnet-stack (compile succeeds, rest of image packaging works)
>
> Additionally, the following order compiles without error:
> 1. bitbake -c clean bacnet-stack
> 2. bitbake -c devshell bacnet-stack
> 3. (from devshell) make all (compile succeeds)
>
> This project is divided into a static library and multiple demo
> applications. The static library needs to be built first, and then the
> demo applications include the static library in their build. I suspect I
> have an issue with either populating the static library or the related
> include files in the sysroot which causes the demo applications to fail to
> build the first time but work the second. However, I can't figure out how
> to fix the issue. Any pointers on what is setup wrong with this recipe?
>From bacnet-stack.inc:
> do_install () {
> install -d ${D}${bindir} ${D}${datadir} ${D}${libdir} >
${STAGING_INCDIR}/${PN}
> ...
> install -m 0644 ${S}/include/* ${STAGING_INCDIR}/${PN}
> }
Don't poke files directly into the sysroot like this. Install the headers to
${D}${incdir} instead, and they will be staged to the sysroot for you.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi] Using the camera
Hello, To get my C920 camera to work with the zedboard I needed to add v4l-utils and then I need several modules that I add to 3.6 kernel https://github.com/Digilent/linux-digilent.git 3.6.0-digilent-13.01-2-g06b3889/ ├── kernel │ └── drivers │ ├── media │ │ └── video │ │ ├── gspca │ │ │ └── gspca_main.ko │ │ ├── uvc │ │ │ └── uvcvideo.ko │ │ ├── v4l2-common.ko │ │ ├── v4l2-int-device.ko │ │ ├── videobuf2-core.ko │ │ ├── videobuf2-memops.ko │ │ ├── videobuf2-vmalloc.ko │ │ └── videodev.ko Hope this helps ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Compile on recipe works the second time
Paul,
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: Tuesday, November 19, 2013 10:47 AM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Compile on recipe works the second time
>
> Hi Bryan,
>
> On Tuesday 19 November 2013 08:57:40 Bryan Evenson wrote:
> > I'm on poky/dylan-9.0.1 and I've created a layer for a separate open
> > source project to include in my image. The layer is at
> > https://github.com/evensonbryan/meta-bacnet for those of you who want
> > to try and duplicate my results. Just add this layer to your setup
> > and build the recipe "bacnet-stack".
> >
> > I have a very odd build issue. The first time I build the recipe,
> the
> > build fails during the compile step. However, if I then build the
> > recipe again, the compile completes without errors. For example:
> >
> > 1. bitbake -c clean bacnet-stack
> > 2. bitbake bacnet-stack (compile fails) 3. bitbake bacnet-stack
> > (compile succeeds, rest of image packaging works)
> >
> > Additionally, the following order compiles without error:
> > 1. bitbake -c clean bacnet-stack
> > 2. bitbake -c devshell bacnet-stack
> > 3. (from devshell) make all (compile succeeds)
> >
> > This project is divided into a static library and multiple demo
> > applications. The static library needs to be built first, and then
> > the demo applications include the static library in their build. I
> > suspect I have an issue with either populating the static library or
> > the related include files in the sysroot which causes the demo
> > applications to fail to build the first time but work the second.
> > However, I can't figure out how to fix the issue. Any pointers on
> what is setup wrong with this recipe?
>
> From bacnet-stack.inc:
> > do_install () {
> > install -d ${D}${bindir} ${D}${datadir} ${D}${libdir} >
> ${STAGING_INCDIR}/${PN}
> > ...
> > install -m 0644 ${S}/include/* ${STAGING_INCDIR}/${PN} }
>
> Don't poke files directly into the sysroot like this. Install the
> headers to ${D}${incdir} instead, and they will be staged to the
> sysroot for you.
I made the suggested change and I'm still having the same build issue. I
pulled the applicable lines from the compile log when I get the failure.
...
make[3]: *** No rule to make target `../../ports/linux/bip-init.o', needed by
`libbacnet.a'. Stop.
make[3]: Leaving directory
`/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/lib'
make[2]: *** [../../lib/libbacnet.a] Error 2
make[2]: Leaving directory
`/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/demo/readprop'
make[1]: *** [readprop.all] Error 2
make[1]: Leaving directory
`/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/demo'
make: *** [demos] Error 2
make: *** Waiting for unfinished jobs
arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork
-mtune=arm926ej-s -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
--sysroot=/media/sda3/poky/poky-build/tmp/sysroots/at91sam9x5ek -c -Wall
-Wmissing-prototypes -Os
-I/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/ports/linux
-I/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/demo/object
-I/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/demo/handler
-Iusr/include/glib-2.0
-I/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/include
`pkg-config --cflags --libs glib-2.0 uuid` -DPRINT_ENABLED=1 -DBACAPP_ALL
-DBACFILE -DINTRINSIC_REPORTING -DBAC_ROUTING -DBACDL_BIP=1 -DBBMD_ENABLED=1
-DWEAK_FUNC= -O2 -pipe -g -feliminate-unused-debug-types
/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-
stack/bacnet-stack-0-7-1/ports/linux/bip-init.c -o
/media/sda3/poky/poky-build/tmp/work/arm926ejste-poky-linux-gnueabi/bacnet-stack/bacnet-stack-0-7-1/ports/linux/bip-init.o
...
If I'm reading this right, the build of the static library fails because it
doesn't know how to build bip-init.o, but immediately after the static library
build fails then bip-init.o gets built. Any thoughts on what could be wrong?
Thanks,
Bryan
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] Using the camera
On 2013-11-19 09:18, Edward Vidal wrote: Hello, To get my C920 camera to work with the zedboard I needed to add v4l-utils and then I need several modules that I add to 3.6 kernel https://github.com/Digilent/linux-digilent.git 3.6.0-digilent-13.01-2-g06b3889/ ├── kernel │ └── drivers │ ├── media │ │ └── video │ │ ├── gspca │ │ │ └── gspca_main.ko │ │ ├── uvc │ │ │ └── uvcvideo.ko │ │ ├── v4l2-common.ko │ │ ├── v4l2-int-device.ko │ │ ├── videobuf2-core.ko │ │ ├── videobuf2-memops.ko │ │ ├── videobuf2-vmalloc.ko │ │ └── videodev.ko Hope this helps Thanks for the reply, but this is not what I'm looking for. The camera module I'm using is directly connected to the RaspberryPi via the CSI interface, not USB like your C920 and it uses very different drivers to access. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ptest Wiki Page Updated with lists
Folks, I have updated the ptest wiki page (https://wiki.yoctoproject.org/wiki/Ptest) with lists of those packages already completed and those that are in progress by various team members that have informed me in the past. If you are interested in helping to enable ptest on packages, please add the recipes that your working on to the wiki so as to not duplicate work. Thanks -- Sau! Saul Wold Yocto Component Wrangler @ Intel Yocto Project / Poky Build System ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cloud-services][PATCH] erlang: skip the host library path check to fix cross-compile issue
Signed-off-by: Zhenhua Luo
---
.../erlang/erlang-fix-build-issue-in-Yocto.patch | 25 ++
.../recipes-devtools/erlang/erlang_R15B.bb | 2 ++
2 files changed, 27 insertions(+)
create mode 100644
meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
diff --git
a/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
new file mode 100644
index 000..2d4b7b5
--- /dev/null
+++
b/meta-openstack/recipes-devtools/erlang/erlang/erlang-fix-build-issue-in-Yocto.patch
@@ -0,0 +1,25 @@
+Upstream-Status: Inappropriate [The fix is specific to Yocto build env]
+
+Skip host library path check to fix following Yocto insane check issue:
+ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
+Rerun configure task after fixing this.
+
+Signed-off-by: Zhenhua Luo
+
+--- otp_src_R15B/erts/configure.in.orig2011-12-14 04:22:11.0
-0600
otp_src_R15B/erts/configure.in 2013-11-19 04:15:33.694334610 -0600
+@@ -1469,10 +1469,10 @@
+ # ln -s libdlpi.so.1 $try_dlpi_lib/libdlpi.so
+ ])
+fi
+- LDFLAGS="-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS"
+- unset -v try_dlpi_lib
+- AC_MSG_NOTICE([Extending the search to include /lib])
+- AC_CHECK_LIB(dlpi, dlpi_open)
++# LDFLAGS="-L$try_dlpi_lib -R$try_dlpi_lib $LDFLAGS"
++# unset -v try_dlpi_lib
++# AC_MSG_NOTICE([Extending the search to include /lib])
++# AC_CHECK_LIB(dlpi, dlpi_open)
+if test x"$ac_cv_lib_dlpi_dlpi_open" = x"no"; then
+ LDFLAGS="$save_ldflags"
+fi
diff --git a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
index 68d144b..8d8e28b 100644
--- a/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
+++ b/meta-openstack/recipes-devtools/erlang/erlang_R15B.bb
@@ -9,6 +9,7 @@ EXTRA_OEMAKE = "BUILD_CC='${BUILD_CC}'"
EXTRA_OECONF = "--with-ssl=${STAGING_DIR_HOST}${layout_exec_prefix}"
+EXTRA_OECONF_append_powerpc = " --disable-smp-support --disable-hipe"
EXTRA_OECONF_append_arm = " --disable-smp-support --disable-hipe"
EXTRA_OECONF_append_armeb = " --disable-smp-support --disable-hipe"
EXTRA_OECONF_append_mipsel = " --disable-smp-support --disable-hipe"
@@ -55,5 +56,6 @@ FILES_${PN}-staticdev += "${libdir}/*/*/*/*.a
${libdir}/*/*/*/*/*.a ${libdir}/*/
FILES_${PN}-libs-dbg += " ${libdir}/erlang/*/.debug
${libdir}/erlang/*/*/.debug ${libdir}/erlang/*/*/*/.debug
${libdir}/erlang/*/*/*/*/.debug ${libdir}/erlang/*/*/*/*/*/.debug "
+SRC_URI += "file://erlang-fix-build-issue-in-Yocto.patch"
SRC_URI[md5sum] = "dd6c2a4807551b4a8a536067bde31d73"
SRC_URI[sha256sum] =
"5bc34fc34fc890f84bae7ff1f7c81fbec2c9aa28a0ef51a57d7a8192204d8aa2"
--
1.8.3.1
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cloud-services][PATCH] python-horizon: remove nodejs from RDEPENDS of powerpc arch
Nodejs only supports arm, x86 and ia32 archs, it doesn't support powerpc.
Signed-off-by: Zhenhua Luo
---
meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
index fdd0bd0..edd8dae 100644
--- a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
+++ b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
@@ -63,8 +63,7 @@ FILES_${SRCNAME} = "${bindir}/* \
${datadir}/* \
"
-RDEPENDS_${PN} += "nodejs \
-python-django \
+RDEPENDS_${PN} += " python-django \
python-django-appconf \
python-django-compressor \
python-django-openstack-auth \
@@ -80,6 +79,11 @@ RDEPENDS_${PN} += "nodejs \
python-lockfile \
"
+RDEPENDS_${PN}_arm += " nodejs"
+RDEPENDS_${PN}_i686 += " nodejs"
+RDEPENDS_${PN}_x86-64 += " nodejs"
+RDEPENDS_${PN}_ia32 += " nodejs"
+
RDEPENDS_${SRCNAME} = "${PN}"
INITSCRIPT_PACKAGES = "${SRCNAME}"
--
1.8.3.1
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to modify u-boot in Root File System rootfs.ext2.gz.u-boot ?
Thanks a lot for your answers Stefano, I put the patch in my bsp directory and adjust my u-boot receipe. On Tue, Nov 19, 2013 at 3:40 PM, Stefano Babic wrote: > Hi Jack, > > On 19/11/2013 12:25, Jack wrote: > > > For Nor-Flash we have only three files(kernel,rootfs,dtb). Where is > u-boot? > > I think it is inside the fsl-image-minimal-p1022ds.ext2.gz.u-boot rootfs > > file. Is it true? > > I do not think so, but you are the best to answer this question: unzip > the file and check inside. > > However, even if it contains a u-boot.bin or whatever is your u-boot > file, you have to extract it to write the bootloader at the right address. > > In most cases, you will see a separate image for u-boot in > tmp/deploy/images diurectory. > > > > > So, for modifying u-boot to adujst serial boaudrate, > > No. To modify the serial console under linux. > > > I understand that I can > > add SERIAL_CONSOLE = "115200 ttyS0" to my local.conf according to your > reply > > See Robert reply. SERIAL_CONSOLE is deprecated, uses SERIAL_CONSOLES > instead. > > > and it doesnt need to modify u-boot source code. > > > > Am I in the right place? > > Mmmhh..there is something missing. Usually you have a separate file for > u-boot. Of course, if u-boot is part of the filesystem, you cannot use > for a first installation because u-boot must be copied at a specific > address. > Best regards, > Stefano Babic > > -- > = > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de > = > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA Tests in Yocto development environment block diagram
Dear Alex, Thank you for your response. And I need to know one more thing whether these QA tests are done manually or it's automated during the build or its done separately by Yocto for particular distribution? Is there any QA tests done during the build procedure locally? regards dilip kumar b On 14-Nov-2013 12:15 am, "Georgescu, Alexandru C" < alexandru.c.george...@intel.com> wrote: > Hi, > > Our overall testing plan is available here: > https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan. Since we > are in the last phase of planning for 1.6, this is not the final version > yet. > > > > Regarding the test cases, all you have to do is to have an account in our > bug tracking website https://bugzilla.yoctoproject.org/ and follow the > instructions in the Testopia wiki, our test case platform management > system: https://wiki.yoctoproject.org/wiki/Testopia. There you can find > the tests performed against the Yocto Project components. > > > > Regards, > > *--* > > *Alexandru Georgescu* > > > > *From:* yocto-boun...@yoctoproject.org [mailto: > yocto-boun...@yoctoproject.org] *On Behalf Of *Dilip Kumar > *Sent:* Wednesday, November 13, 2013 06:27 > *To:* yocto@yoctoproject.org > *Subject:* [yocto] QA Tests in Yocto development environment block diagram > > > > Dear all, > > I need know what is QA tests and what all the tests it will do and need to > know more information about QA please help me out in this. > > regards > dilip kumar b > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] meta-intel Released for Yocto Project 1.5
All, I am pleased to announce the release of meta-intel for the Yocto Project's 1.5 release. Thank you for the meta-intel maintainers and contributors for all their hard work. -b Release Name: meta-intel Repo: git://git.yoctoproject.org/meta-intel Branch: dora Tag: dora-10.0.0 Hash: c86e39dd06571458c7dee6cf289d5b470c98f4bd Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/meta-intel-dora-10.0.0.tar.bz2 Board Support Packages chiefriver Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/chiefriver/meta-chiefriver-dora-10.0.0.tar.bz2 Md5sum: 53ddf64f85e5c9134c1e4ce318d61e7a crownbay Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/crownbay/meta-crownbay-dora-10.0.0.tar.bz2 Md5sum: 92bcf9b94e1a3752b0879e3f2f15afee crownbay-noemgd Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/crownbay-noemgd/meta-crownbay-noemgd-dora-10.0.0.tar.bz2 Md5sum: 7da983a218afbfdc75c90447e4667e38 crystalforest Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/crystalforest/meta-crystalforest-dora-10.0.0.tar.bz2 Md5sum: 5a3bc6a78f3cdf1dfd0fcb93a42ab1e0 emenlow Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/emenlow/meta-emenlow-dora-10.0.0.tar.bz2 Md5sum: 225199fe9685f972b43c0860f8dc6f3c emenlow-noemgd Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/emenlow-noemgd/meta-emenlow-noemgd-dora-10.0.0.tar.bz2 Md5sum: 6e653f29786cc0a21a6551f71b83beaa fri2 Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/fri2/meta-fri2-dora-10.0.0.tar.bz2 Md5sum: e1c9e48f91616904603852a0ed2750e7 fri2-noemgd Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/fri2-noemgd/meta-fri2-noemgd-dora-10.0.0.tar.bz2 Md5sum: 71aac59dad80379dbf6842ded206d6fb jasperforest Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/jasperforest/meta-jasperforest-dora-10.0.0.tar.bz2 Md5sum: a0a0a25d288ff976f25c881ce82405e8 haswell-wc Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/haswell-wc/meta-haswell-wc-dora-10.0.0.tar.bz2 Md5sum: f095e8dfd74fa0056de79f16a58bf376 n450 Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/n450/meta-n450-dora-10.0.0.tar.bz2 Md5sum: 6d96fecb8b2cd5d90e5534ef56cb2177 nuc Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/nuc/meta-nuc-dora-10.0.0.tar.bz2 Md5sum: e626337289a4f3f23f0c846984c2b499 romley Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/romley/meta-romley-dora-10.0.0.tar.bz2 Md5sum: 06b82d7fd942e83dff1219fcaf206595 sugarbay Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/sugarbay/meta-sugarbay-dora-10.0.0.tar.bz2 Md5sum: 1dc884b9277e1b88c5f99575a374b661 sys940x Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/sys940x/meta-sys940x-dora-10.0.0.tar.bz2 Md5sum: f3cf53d6001df37f24323b723a159a0f sys940x-noemgd Download: http://Downloads.yoctoproject.org/releases/yocto/yocto-1.5/machines/sys940x-noemgd/meta-sys940x-noemgd-dora-10.0.0.tar.bz2 Md5sum: 396dba8c8801f20e85f092cf8966 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Weekly build availability
All, The next weekly build will be available in a few hours at: http://autobuilder.yoctoproject.org/pub/nightly/20131119-7 poky 215dab864e7cf74394840621ad0754db593708f1 bitbake a66ee0994645aa5658b2f5ea134ed17d89f8751a eclipse-poky-juno 7b50b0cee840092b4a575c239ddf11ba50d78327 eclipse-poky-kepler 84c1361ee96b781666a23f068244d4f1252be712 meta-fsl-arm 987115d6d099a5e87d9d5b3c4e6567a5e6309fd0 meta-fsl-ppc 768c6ef13546e0f977847bc1fbb5957571fbf724 meta-intel f5c2786e7ca190308523379706130e0c2be793c9 meta-minnow 91cff9475081a5625c1c0bb49c17c6f3130ec503 meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222 oecore 0eb947454e1c92467283e6f1adeca67c7c57698b Please begin scheduled testing when it completes. -b -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] connman
Hi All, Can anyone help with wifi not being enabled with connman? I have to use "ifup wlan0" to start my wifi interface, connman refuses to bring it up on start, even though I have the ethernet cable un-plugged. I have enabled wifi in the settings file and have a wifi.conf that is used because when I manually bring it up, it connects to the network specified in there. Thanks, Bernie ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] connman
On 19 November 2013 20:52, Bernard Mentink wrote: > Can anyone help with wifi not being enabled with connman? > > I have to use "ifup wlan0" to start my wifi interface, connman refuses to > bring it up on start, even though I have the ethernet cable un-plugged. > > I have enabled wifi in the settings file and have a wifi.conf that is used > because when I manually bring it up, it connects to the network specified in > there. Really this is for the connman list as it's a connman-specific question. The answer is that connman defaults to turning the wifi "technology" off by default. If you want it to be on out of the box then you'll need to tell connman that. As an example, have a look at the connman bbappend (specifically the guacamayo/settings file) here: https://github.com/Guacamayo/meta-guacamayo/tree/master/meta-guacamayo/recipes-connectivity/connman Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cloud-services][PATCH] python-horizon: remove nodejs from RDEPENDS of powerpc arch
On 11/19/2013, 4:28 AM, Zhenhua Luo wrote:
Nodejs only supports arm, x86 and ia32 archs, it doesn't support powerpc.
This looks good. I'm making some other significant changes at the
moment, but I've queued the patch.
Bruce
Signed-off-by: Zhenhua Luo
---
meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
index fdd0bd0..edd8dae 100644
--- a/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
+++ b/meta-openstack/recipes-devtools/python/python-horizon_2013.1.3.bb
@@ -63,8 +63,7 @@ FILES_${SRCNAME} = "${bindir}/* \
${datadir}/* \
"
-RDEPENDS_${PN} += "nodejs \
-python-django \
+RDEPENDS_${PN} += " python-django \
python-django-appconf \
python-django-compressor \
python-django-openstack-auth \
@@ -80,6 +79,11 @@ RDEPENDS_${PN} += "nodejs \
python-lockfile \
"
+RDEPENDS_${PN}_arm += " nodejs"
+RDEPENDS_${PN}_i686 += " nodejs"
+RDEPENDS_${PN}_x86-64 += " nodejs"
+RDEPENDS_${PN}_ia32 += " nodejs"
+
RDEPENDS_${SRCNAME} = "${PN}"
INITSCRIPT_PACKAGES = "${SRCNAME}"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
