Re: [yocto] Release Candidate Build for yocto-1.7.rc4 now available.

2014-10-20 Thread Georgescu, Alexandru C
Hi Michael,
Can you add me and Yi on the CC as well?

Thanks,
--
Alexandru Georgescu
Yocto QA Engineer
SSG/SSD Open Source Technology Center Romania




On 20/10/14 01:05, "Michael Halstead"  wrote:

>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,
>>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security] nmap build failed

2014-10-20 Thread Lai Eddy
build with yocto 1.6.1 on Ubuntu 12.04,
have add extra dep. to local.conf according to REAME
  /poky/openembedded-core/meta \
  /poky/meta-openembedded/meta-oe \
  /poky/meta-openembedded/meta-perl \
  /poky/meta-security \

but got following error message:

$ bitbake -k core-image-full-cmdline
ERROR: ExpansionError during parsing
/poky/meta-openembedded/meta-perl/recipes-perl/libtest/
libtest-harness-perl_3.30.bb: Failure expanding variable
do_fetch[file-checksums], expression was
${@bb.fetch.get_checksum_file_list(d)} which triggered exception
MalformedUrl: The URL:
'${CPAN_MIRROR}/authors/id/L/LE/LEONT/Test-Harness-3.30.tar.gz' is invalid
and cannot be interpreted

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [OE-core] Poky X11

2014-10-20 Thread Burton, Ross
On 19 October 2014 19:37, akuster808  wrote:
> 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

Did you at some point do a build with meta-oe enabled, and then not
enabled?  There's a known bad interaction between oe-core and
meta-oe's X init scripts which results in problems like this.  The
quick fix is to wipe your tmp and rebuild (using sstate this should
take just a few minutes).

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] create_image.tar fail

2014-10-20 Thread Burton, Ross
On 20 October 2014 03:24,   wrote:
> ·   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.

Just write the commands that you'd normally run to configure the
software.  However in this case libtdb (assuming you mean the tdb from
Samba) appears to use waf, so simply doing "inherit waf" will give you
configure/compile/install functions automatically.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-mono] Mono updated to 3.10.0

2014-10-20 Thread Alex J Lennon

I've updated support for Mono build in meta-mono master to 3.10.0 (the
current release).

I've performed basic build testing on an qemux86 build of
core-image-mono, based on core-image-sato, running a "Hello World"
console application and a "Hello World" Windows Forms application.

There has been feedback that issues with armhf support are addressed in
3.10.0 but I have not yet had time to investigate.

ref: https://bugzilla.xamarin.com/show_bug.cgi?id=20239

All feedback on testing and/or issues appreciated.

Regards,

Alex

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Issues creating /dev/ nodes in an initramfs

2014-10-20 Thread Mitchell Skiba
I've been building a kernel with an initramfs, by using INITRAMFS_IMAGE to
specify a recipe that generates an image as a .cpio.gz archive. I've been
having issues creating /dev/console (or any other device file) in the
image. (The 3.14 kernel panics if /dev/console is not a character device.)

It seems there is already a way to create dev nodes via the
IMAGE_DEVICE_TABLE and IMAGE_DEVICE_TABLES variables. However this
mechanism, through the makedevs utility, appears to require the building
user to have permission to call mknod. (Makedevs ignores the return code
from the mknod call, so it doesn't outright fail on the permissions error,
but device files will not be created.)

I've hacked around it in my image recipe by appending a step onto
do_rootfs, but I'm not too happy with the way I did it. It seems like the
proper way to fix this is to change the image commands in
image_types.bbclass. However, each image type would need a different way of
adding in the special files. (At this point I only care about cpio archives
for the initramfs.)


Does anyone have the current IMAGE_DEVICE_TABLE implementation working? (As
in, is there something that I have missed?)

I'm considering fixing this by changing the IMAGE_COMMAND_cpio function in
image_typyes.bbclass to generate a cpio archive with only the contents
described in IMAGE_DEIVCE_TABLE(S), then use the cpio utility's append mode
to add in the rootfs contents. (It is simpler to create a new archive with
a script than it is to append to an existing one, so I thought I'd let the
cpio utility handle the archive appending.)
Does this sound like a reasonable approach, and the correct place to fix it?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Error building x86_64-mingw32 SDK

2014-10-20 Thread Måns Andersson
Hi,
I encountered an error building the x86_64-mingw32 SDK using poky (daisy, 
bda51ee) and meta-mingw (daisy, e9208b8) which I can't solve. Has anyone 
experienced something similar?

Thanks,
// Måns

$ bitbake -c populate_sdk myboard-base-image
...
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 
'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function create_sdk_files
| ('movefile: Failed to move', 
'/oe/poky/myboard/tmp/work/myboard-poky-linux-gnueabi/myboard-base-image/1.0-r0/sdk/image/var/lib/opkg/lists',
 'to', 
'/oe/poky/myboard/tmp/work/myboard-poky-linux-gnueabi/myboard-base-image/1.0-r0/sdk/image/opt/poky/1.6.1/sysroots/x86_64-pokysdk-mingw32/var/lib/opkg',
 OSError(39, 'Directory not empty'))
| ('movefile: Failed to move', 
'/oe/poky/myboard/tmp/work/myboard-poky-linux-gnueabi/myboard-base-image/1.0-r0/sdk/image/var/lib/opkg/status',
 'to', 
'/oe/poky/myboard/tmp/work/myboard-poky-linux-gnueabi/myboard-base-image/1.0-r0/sdk/image/opt/poky/1.6.1/sysroots/x86_64-pokysdk-mingw32/var/lib/opkg',
 OSError(21, 'Is a directory'))
| DEBUG: Shell function create_sdk_files finished
| DEBUG: Executing shell function tar_sdk
| tar: ./sysroots/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/var/lock: File 
removed before we read it
| tar: ./sysroots/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/etc/mtab: File 
removed before we read it
| WARNING: exit code 1 from a shell command.
| DEBUG: Python function do_populate_sdk finished
| ERROR: Function failed: tar_sdk (log file is located at 
/oe/poky/myboard/tmp/work/myboard-poky-linux-gnueabi/myboard-base-image/1.0-r0/temp/log.do_populate_sdk.22271)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-security] nmap build failed

2014-10-20 Thread akuster808

On 10/20/14, 2:27 AM, Lai Eddy wrote:

Lai,

thanks for reporting this, I will take a look into this. I have not 
tried daisy on recent meta-security.


- Armin

build with yocto 1.6.1 on Ubuntu 12.04,
have add extra dep. to local.conf according to REAME
  /poky/openembedded-core/meta \
  /poky/meta-openembedded/meta-oe \
  /poky/meta-openembedded/meta-perl \
  /poky/meta-security \

but got following error message:

$ bitbake -k core-image-full-cmdline
ERROR: ExpansionError during parsing 
/poky/meta-openembedded/meta-perl/recipes-perl/libtest/libtest-harness-perl_3.30.bb 
: Failure expanding variable 
do_fetch[file-checksums], expression was 
${@bb.fetch.get_checksum_file_list(d)} which triggered exception 
MalformedUrl: The URL: 
'${CPAN_MIRROR}/authors/id/L/LE/LEONT/Test-Harness-3.30.tar.gz' is 
invalid and cannot be interpreted


Summary: There was 1 ERROR message shown, returning a non-zero exit code.






--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Questions regarding adding a new llvm based cross-compiler

2014-10-20 Thread Cody P Schafer
On Fri, Oct 17, 2014 at 1:48 PM, Martin Jansa  wrote:
> On Fri, Oct 17, 2014 at 09:07:19AM +0100, 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.
>
> Are you using llvm recipes from meta-oe (or at least starting from
> them)?

I wasn't. Rust packages a particular llvm version already (and ties it
into it's build scripts). I'm planning on just using that one.

> I haven't tried it yet, but I've asked Servo developer, how they do
> cross-builds and he said that it's really simple with Rust and Cargo,
> which support cross-compilation by design.

Well:

>From what I've found, crossbuilds work fine if you're using one of a
small set of blessed triples (ie: not arm-poky-linux-gnueabi, but
arm-unknown-linux-gnueabihf), and you don't set any special
CFLAGS/LDFLAGS variables (which oe does).
And the infrastructure is not in place to allow packagers to easily
add/use different triples and "linkers" (rustc calls gcc/cc to link
it's programs, and as a result needs to know where it is).
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Questions regarding adding a new llvm based cross-compiler

2014-10-20 Thread Cody P Schafer
On Sun, Oct 19, 2014 at 4:10 AM, Khem Raj  wrote:
>
[...]
> 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

(repo link for the interested: https://github.com/kraj/meta-clang)

Khem: the complication for me is rustc doesn't magically build for all
targets it supports (at the moment) when using gcc as the
compiler/linker (rustc calls an external binary, typically gcc or cc
to link it's code). As a result, I can't just build for -native. I'm
currently fighting with cross.bbclass to convince it to do what I
want.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, October 21, 2014 8:00 AM US Pacific Time

2014-10-20 Thread Jolley, Stephen K
Tuesday, October 21, 2014 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features

* SWAT team rotation: Paul -> Saul

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/weekly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [OE-core] Poky X11

2014-10-20 Thread akuster808



On 10/20/2014 02:40 AM, Burton, Ross wrote:

On 19 October 2014 19:37, akuster808  wrote:

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


Did you at some point do a build with meta-oe enabled, and then not
enabled?


I could not recall.

There's a known bad interaction between oe-core and

meta-oe's X init scripts which results in problems like this.  The
quick fix is to wipe your tmp and rebuild (using sstate this should
take just a few minutes).


Did that and still have the problem.

- Armin



Ross


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Release Candidate Build for yocto-1.7.rc4 now available.

2014-10-20 Thread Michael Halstead
You were both already in the CC list. You should receive copies when the
next release candidate is built.

Michael Halstead
Yocto Project / System Administrator

On 10/20/2014 12:13 AM, Georgescu, Alexandru C wrote:
> Hi Michael,
> Can you add me and Yi on the CC as well?
>
> Thanks,
> --
> Alexandru Georgescu
> Yocto QA Engineer
> SSG/SSD Open Source Technology Center Romania
>
>
>
>
> On 20/10/14 01:05, "Michael Halstead"  wrote:
>
>> 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


Re: [yocto] Release Candidate Build for yocto-1.7.rc4 now available.

2014-10-20 Thread Georgescu, Alexandru C
Thanks!
--
Alexandru Georgescu
Yocto QA Engineer
SSG/SSD Open Source Technology Center Romania




On 21/10/14 05:31, "Michael Halstead"  wrote:

>You were both already in the CC list. You should receive copies when the
>next release candidate is built.
>
>Michael Halstead
>Yocto Project / System Administrator
>
>On 10/20/2014 12:13 AM, Georgescu, Alexandru C wrote:
>> Hi Michael,
>> Can you add me and Yi on the CC as well?
>>
>> Thanks,
>> --
>> Alexandru Georgescu
>> Yocto QA Engineer
>> SSG/SSD Open Source Technology Center Romania
>>
>>
>>
>>
>> On 20/10/14 01:05, "Michael Halstead"  wrote:
>>
>>> 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,

>>>
>>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto