Re: [yocto] Questions regarding adding a new llvm based cross-compiler
On Friday, October 17, 2014, Paul Barker wrote: > On 16 October 2014 18:46, Cody P Schafer > > wrote: > > Hi all, > > > > I'm working on creating a layer for the rust compiler (which uses > > llvm) and was wondering if there were any best practices and/or > > examples people could point me at. > > I can't really offer much help on the LLVM side, but I can say this > will be really useful work. I'm slowly learning Rust and researching > how it can be used for embedded development and it will be excellent > to have a rust compiler working as part of OpenEmbedded/Yocto. > > If you need any testing of this layer once it's created, just let me know. I have started to integrate clang into oe Which probably is quitquite similar to this effortwise. Its very prelimpreliminary. Check my github repo. I should add it to layer index > > Cheers, > > -- > Paul Barker > > Email: p...@paulbarker.me.uk > http://www.paulbarker.me.uk > -- > ___ > 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] [meta-raspberrypi][PATCH] gstreamer1.0-plugins-bad: raname bbappend to work with any version in oe-core
Signed-off-by: Laurentiu Palcu
---
...bappend => gstreamer1.0-plugins-bad_%.bbappend} |0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-multimedia/gstreamer/{gstreamer1.0-plugins-bad_1.4.0.bbappend
=> gstreamer1.0-plugins-bad_%.bbappend} (100%)
diff --git
a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.4.0.bbappend
b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
similarity index 100%
rename from recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.4.0.bbappend
rename to recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_%.bbappend
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Poky X11
Hello, When I build 'core-image-x11' on Poky, X on wont start. I am using the standard Poky clone with no added layers. When I manually start x I get the following error: startx /etc/X11/xinit/xinitrc: line 95: twm : command not found /etc/X11/xinit/xinitrc: line 96: xclock : command not found /etc/X11/xinit/xinitrc: line 97: xterm : command not found /etc/X11/xinit/xinitrc: line 98: xterm : command not found /etc/X11/xinit/xinitrc: line 99: exec : command not found I suspect I am doing something wrong. I found that the missing files are in meta-openembedded/meta-oe/recipes-graphics/*. If this is a bug, which direction should I go to address the problem? 1) move missing recipes to oe-core 2) remove core-image-x11 from oe-core 3) remove files from xinitrc 4) none of the above, issue some where else. regards, Armin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Release Candidate Build for yocto-1.7.rc4 now available.
The QA_MAIL_CC value in ./config/autobuilder.conf needed to be comma separated. I think it is fixed now. Thanks for the report. Michael Halstead Yocto Project / SysAdmin On 10/12/2014 04:33 AM, Paul Barker wrote: > On 12 October 2014 01:51, Poky Build User > wrote: >> This is an automated message from >> The Yocto Project Autobuilder >> Git: git://git.yoctoproject.org/yocto-autobuilder >> Email: elizabeth.flana...@intel.com > Beth, > > I noticed that the Cc list for the original email looks to be corrupted: > Cc: ""@ossystems.com.bryi.zhao, elizabeth.flanagan@intel.comyocto, > ""@windriver.com, ""@yoctoproject.orgalexandru.c.georgescu, > ""@intel.comotavio > > Just letting you know incase you missed this and it needs attention, > signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason Manual Check Count: 0 Manual Need Check Count: 0 Any problem, please contact Saul Wold -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable" You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason Upgradable Count: 0 Upgrade Total Count: 0 The based commit merge time is: Tue Jul 30 10:57:24 2013 +0300 The based commit is: The based commit is: commit ed19bcca194318e267bc7d11771ad1664bd44022 Author: Emilia Ciobanu Date: Mon Jul 29 15:33:12 2013 +0300 commit ed19bcca194318e267bc7d11771ad1664bd44022 Author: Emilia Ciobanu Date: Mon Jul 29 15:33:12 2013 +0300 Any problem, please contact Saul Wold recipe_color.inc/17: RECIPE_COLOR = "green" recipe_color.inc/17: RECIPE_COLOR = "green" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] create_image.tar fail
Hello,
* I need to creat a new recipes to add libtdb to rootfs. The
source code of tdb is Makefile-Base Package. Bitbake make will run the makefile
automatically to finish the do_compile. But , I must to
execute one "configure" file of source code in
do_configure task before do_compile. How to execute the "configure" in
do_configure task ?
*
* do_configure{
* /*how to execure the configure
file*/
*}
How to solve the problem? If you know , please help me. Thank you.
Thank you&Best regards
Neil Wu
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Remote Debug Issue
Hi, I am trying to remote debug on my Atmel SAMA5D3 Xplained board which "Poky (Yocto Project Reference Distro) 1.5.1" is prebuilt. First I tried to use TCP/IP. I connected my board to my laptop and type "ifconfig", I got following information: eth0 Link encap:Ethernet HWaddr 2e:da:b6:48:b6:47 inet6 addr: fe80::2cda:b6ff:fe48:b647/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:138 (138.0 B) TX bytes:328 (328.0 B) Interrupt:26 Base address:0x8000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) It seems there is only ipv6 address for eth0. Then I type "gdbserver localhost:2001 Test3", I got : Process Test3 created; pid = 937 Listening on port 2001 Then on my laptop I started arm-poky-linux-gnueabi-gdb of 1.5.1 toolchain. In the gdb command line I typed "target remote fe80::2cda:b6ff:fe48:b647:2001". I got error information : fe80: unknown host fe80::2cda:b6ff:fe48:b647:2001: No such file or directory. Actually I can use this ipv6 address to establish ssh remote target in eclipse, so I don't know why it doesn't work for remote debug using TCP/IP. After that I tried to use serial port to establish remote debug. I connect my board to laptop through usb serial port. When I start minicom in terminal, I get "Poky (Yocto Project Reference Distro) 1.5.1 sama5d3_xplained /dev/ttyGS0". So I typed "gdbserver /dev/ttyGS0 Test3". Then in gdb command line I typed "target remote /dev/ttyACM0". "ttyACM0" is the port of the usb serial port. However, in the minicom window it kept printing: Remote dRemote debugging using /dev /ttyGS0 Remote side has terminated connection. GDBRemote side has terminated connectiRemote side has terminated coRemote debugging using /dev/ttyGS0 readchar: Input/output error Now I can't remote debug on my board. Thanks for any help! Kevin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
