[yocto] Yocto Project 1.7_M1.rc1 now available for testing
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M1.rc1 bitbake b82f724c271c43218dc28440219adcea968e2a26 eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37 eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904 meta-fsl-arm ab90b896f4bf09a8ced37c6e1511686217d053b9 meta-fsl-ppc b920491d60752ffc38098266f260dacaa2c35e7a meta-intel 76f529881208811e314dba1478cc3a70abf3160f meta-minnow 7bdcd1140b729598bae6246a4bbc21c3950aadd8 meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45 oecore b4cd268cf7506a521d7800112cb775bd49e1ef09 poky 68824d9b8f6e290da078383316b3f4b732585f2b -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto on X86 Question
Hi, I am a newbie and would like help to point me the right direction with regards to yocto project on X86 system with CF card as boot disk with AMI or Phoenix Bios. I have a few questions listed below 1) How do i build a project with read-only filesystem with an overylay filesystem ? something similar to squashfs and jffs2 or something else. 2) How to i update the firmware after the initial burn to CF? A web interface update would be appreciated. 3) Is there a recipe or build-in function to reset the firmware to factory setting via serial console or SSH, etc? Thank you for helping. Regards. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] seek help: I want to get SRC_URI, SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes
I see. Thank you ^_^
Thanks
Yao Xinpan
> On 06/26/2014 10:45 AM, ya...@cn.fujitsu.com wrote:
> >>
> >> On 06/26/2014 09:44 AM, ya...@cn.fujitsu.com wrote:
> >>> Hi everyone
> >>>
> >>> I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
> >> compiled recipes.
> >>> How to achieve it?
> >>>
> >>> e.g.
> >>> # bitbake core-image-minimal
> >>>
> >>> I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
> >> compiled BB files, including native BB files.
> >>
> >> I think that you can get them one by one, perhaps you can add something
> like:
> >>
> >> d.getVar('SRC_URI', True)
> >> d.getVarFlag('SRC_URI', 'md5sum', True) d.getVarFlag('SRC_URI',
> >> 'sha256sum', True)
> >>
> >> to the base_do_fetch in meta/classes/base.bbclass.
> >
> > I see. Thank you very much.
> >
> > Will Yocto add this functionality?
>
> I think no:-) since this is not a common function.
>
> >
> > I think Yocto should achieve the following functions:
> > 1. Allows the developmenter to easily know which recipes were compiled and
> the information of compiled recipes.
> >Such as all the information listed in a file.
>
> Maybe you can try the archiver.bbclass, check
> meta-yocto/conf/local.conf.sample.extended
>
> for more info.
>
> > 2. Which recipes will be compiled before really compile.
>
> bitbake -g core-image-minimal
>
> Then I think that the pn-buildlist is what you need.
>
> // Robert
>
> >
> > Thanks
> > Yao Xinpan
> >
> >>
> >> // Robert
> >>
> >>>
> >>>
> >>> --
> >>> NAME: Yao Xinpan
> >>> TEL:8559
> >>>
> >>>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] seek help: I want to get SRC_URI, SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes
On 06/26/2014 10:45 AM, ya...@cn.fujitsu.com wrote:
On 06/26/2014 09:44 AM, ya...@cn.fujitsu.com wrote:
Hi everyone
I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
compiled recipes.
How to achieve it?
e.g.
# bitbake core-image-minimal
I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
compiled BB files, including native BB files.
I think that you can get them one by one, perhaps you can add something like:
d.getVar('SRC_URI', True)
d.getVarFlag('SRC_URI', 'md5sum', True)
d.getVarFlag('SRC_URI', 'sha256sum', True)
to the base_do_fetch in meta/classes/base.bbclass.
I see. Thank you very much.
Will Yocto add this functionality?
I think no:-) since this is not a common function.
I think Yocto should achieve the following functions:
1. Allows the developmenter to easily know which recipes were compiled and the
information of compiled recipes.
Such as all the information listed in a file.
Maybe you can try the archiver.bbclass, check
meta-yocto/conf/local.conf.sample.extended
for more info.
2. Which recipes will be compiled before really compile.
bitbake -g core-image-minimal
Then I think that the pn-buildlist is what you need.
// Robert
Thanks
Yao Xinpan
// Robert
--
NAME: Yao Xinpan
TEL:8559
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] seek help: I want to get SRC_URI, SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes
>
> On 06/26/2014 09:44 AM, ya...@cn.fujitsu.com wrote:
> > Hi everyone
> >
> > I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
> compiled recipes.
> > How to achieve it?
> >
> > e.g.
> > # bitbake core-image-minimal
> >
> > I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of
> compiled BB files, including native BB files.
>
> I think that you can get them one by one, perhaps you can add something like:
>
> d.getVar('SRC_URI', True)
> d.getVarFlag('SRC_URI', 'md5sum', True)
> d.getVarFlag('SRC_URI', 'sha256sum', True)
>
> to the base_do_fetch in meta/classes/base.bbclass.
I see. Thank you very much.
Will Yocto add this functionality?
I think Yocto should achieve the following functions:
1. Allows the developmenter to easily know which recipes were compiled and the
information of compiled recipes.
Such as all the information listed in a file.
2. Which recipes will be compiled before really compile.
Thanks
Yao Xinpan
>
> // Robert
>
> >
> >
> > --
> > NAME: Yao Xinpan
> > TEL:8559
> >
> >
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] seek help: I want to get SRC_URI, SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes
On 06/26/2014 09:44 AM, ya...@cn.fujitsu.com wrote:
Hi everyone
I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled
recipes.
How to achieve it?
e.g.
# bitbake core-image-minimal
I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled BB
files, including native BB files.
I think that you can get them one by one, perhaps you can add something like:
d.getVar('SRC_URI', True)
d.getVarFlag('SRC_URI', 'md5sum', True)
d.getVarFlag('SRC_URI', 'sha256sum', True)
to the base_do_fetch in meta/classes/base.bbclass.
// Robert
--
NAME: Yao Xinpan
TEL:8559
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] seek help: I want to get SRC_URI, SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes
Hi everyone I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled recipes. How to achieve it? e.g. # bitbake core-image-minimal I want to get SRC_URI,SRC_URI[md5sum] and SRC_URI[sha256sum] of compiled BB files, including native BB files. -- NAME: Yao Xinpan TEL:8559 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Create own image type
Hello Isak, You are no the right way. You have to add IMAGE_CLASSES += "myImage" somewhere in your conf files. I prefer distro.conf for my own distro, but perhaps you can add it to local.conf as well. BR, Maxim. On Wed, Jun 25, 2014 at 5:04 PM, Isak Lichtenstein < isak.lichtenst...@kistler.com> wrote: > Hi all, > > > > I’m trying to create my own image type. I thought that it would be enough > to create a myImage.bbclass file implementing IMAGE_CMD_myImage and > extending IMAGE_TYPES += “ myImage”. > > > > But this isn’t working and I didn’t find anything in the manual. > > > > It this possible at all ( can’t imagine that it isn’t) ? > > > > Would appreciate any hint possible. > > > > Best regards > > > > Isak > > -- > ___ > 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] Bitbake: error in cachedpath.py
Dear all,
I am setting up Yocto to compile my kernel for odroid xu. During the
package phase of building the kernel, I get an error in cachedpath.py
DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing python function do_package
DEBUG: Executing python function package_get_auto_pr
DEBUG: Python function package_get_auto_pr finished
DEBUG: Executing python function perform_packagecopy
DEBUG: Python function perform_packagecopy finished
DEBUG: Executing python function split_and_strip_files
ERROR: Error executing a python function in
/home/eich/yocto/poky/meta-odroid/recipes-kernel/linux/linux-hardkernel_3.4.bb:
The stack trace of python calls that resulted in this exception/failure
was:
File: 'split_and_strip_files', lineno: 222, function:
0218:# End of strip
0219:#
0220:
0221:
*** 0222:split_and_strip_files(d)
0223:
File: 'split_and_strip_files', lineno: 85, function: split_and_strip_files
0081:if debugdir and debugdir in
os.path.dirname(file[len(dvar):]):
0082:continue
0083:
0084:try:
*** 0085:ltarget = cpath.realpath(file, dvar, False)
0086:s = cpath.lstat(ltarget)
0087:except OSError as e:
0088:(err, strerror) = e.args
0089:if err != errno.ENOENT:
File: '/home/eich/yocto/poky/meta/lib/oe/cachedpath.py', lineno: 229,
function: realpath
0225:# be printed a backtrace with 100s of OSError
exceptions
0226:# else
0227:raise OSError(errno.ELOOP,
0228: "too much recursions while
resolving '%s'; loop in '%s'" %
*** 0229: (file, e.strerror))
0230:
0231:raise
0232:
0233:return file
Exception: OSError: [Errno 40] too much recursions while resolving
'/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4-r0/package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release';
loop in
'/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4-r0/package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release'
DEBUG: Python function split_and_strip_files finished
DEBUG: Python function do_package finished
ERROR: Function failed: split_and_strip_files
Seems that the path is to deep?
To track the error, I have attached my kernel.bb
==
require recipes-kernel/linux/linux-yocto.inc
KERNEL_IMAGETYPE = "uImage"
COMPATIBLE_MACHINE = "odroid-xu"
LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"
FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"
S = "${WORKDIR}/git"
# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"
SRCREV = "${AUTOREV}"
SRC_URI = " \
${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
file://defconfig \
"
Any ideas ?
Cheers,
Markus
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Multilib
Hi All, I am trying to build toolchain for arm architecture with multilib support. And my requirement is i need different library file for different features and architecture. Could anyone please help me on the same. Thanks and regards, Atul -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
On Wednesday 25 June 2014 15:22:29 Bollinger, Seth wrote: > >Are you sure? IMAGE_POSTPROCESS_COMMAND runs after all of the image files > >have > >been created; at that time, the contents of the image has already been > >compressed or otherwise combined into the final output file(s), so I > >would think > >that would be too late to modify the contents. > > I just unzipped the bz2 and most dirs were removed, only /var/lib/opkg > remains. Is there any workaround for this, or should I wait for the bug > fix? I'm not sure without digging into it further (which I'm unable to do at the moment, perhaps someone else can.) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
>Are you sure? IMAGE_POSTPROCESS_COMMAND runs after all of the image files >have >been created; at that time, the contents of the image has already been >compressed or otherwise combined into the final output file(s), so I >would think >that would be too late to modify the contents. I just unzipped the bz2 and most dirs were removed, only /var/lib/opkg remains. Is there any workaround for this, or should I wait for the bug fix? Seth -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Create own image type
Hello, I can’t directly help you with this, however I recommend taking a look at meta-raspberrypi ( https://github.com/djwillis/meta-raspberrypi ) as it adds it’s own image type “rpi-sdimg”. Lukas On 25 Jun 2014, at 16:04, Isak Lichtenstein wrote: > Hi all, > > I’m trying to create my own image type. I thought that it would be enough to > create a myImage.bbclass file implementing IMAGE_CMD_myImage and extending > IMAGE_TYPES += “ myImage”. > > But this isn’t working and I didn’t find anything in the manual. > > It this possible at all ( can’t imagine that it isn’t) ? > > Would appreciate any hint possible. > > Best regards > > Isak > -- > ___ > 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] File system for alternate partition
On Wednesday 25 June 2014 13:33:46 Bollinger, Seth wrote: > >It looks like the POSTPROCESS commands are run too early. Subsequent > >actions depend on that directory structure (pre-linking, etc.). It looks > >like I would need some way to hook _cleanup() in the RootFS subclass. > > Actually scratch the above comment. I wasn¹t reading the log spew > correctly. The problem comes in at the image process. So, I was able to > add an IMAGE_POSTPROCESS_COMMAND and that works. Are you sure? IMAGE_POSTPROCESS_COMMAND runs after all of the image files have been created; at that time, the contents of the image has already been compressed or otherwise combined into the final output file(s), so I would think that would be too late to modify the contents. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Create own image type
Hi all, I'm trying to create my own image type. I thought that it would be enough to create a myImage.bbclass file implementing IMAGE_CMD_myImage and extending IMAGE_TYPES += " myImage". But this isn't working and I didn't find anything in the manual. It this possible at all ( can't imagine that it isn't) ? Would appreciate any hint possible. Best regards Isak -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
>It looks like the POSTPROCESS commands are run too early. Subsequent >actions depend on that directory structure (pre-linking, etc.). It looks >like I would need some way to hook _cleanup() in the RootFS subclass. Actually scratch the above comment. I wasn¹t reading the log spew correctly. The problem comes in at the image process. So, I was able to add an IMAGE_POSTPROCESS_COMMAND and that works. Thanks! Seth -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
>You could just delete these within a function added to >ROOTFS_POSTPROCESS_COMMAND, and that's probably the way to deal with it >for >now; however for the future I do think the build system ought to be able >to >clean these files up itself if they aren't supposed to be there. I've >created a >bug to track the issue: > >https://bugzilla.yoctoproject.org/show_bug.cgi?id=6478 It looks like the POSTPROCESS commands are run too early. Subsequent actions depend on that directory structure (pre-linking, etc.). It looks like I would need some way to hook _cleanup() in the RootFS subclass. Seth -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Unable to parse conf/bitbake.conf
Trying to build Cross Compile toolchain
$ bitbake meta-ide-support
ERROR: Traceback (most recent call last):
File "/home/kashyap/kashyap/yocto/poky/bitbake/lib/bb/cookerdata.py",
line 163, in wrapped
return func(fn, *args)
File "/home/kashyap/kashyap/yocto/poky/bitbake/lib/bb/cookerdata.py",
line 173, in parse_config_file
return bb.parse.handle(fn, data, include)
File "/home/kashyap/kashyap/yocto/poky/bitbake/lib/bb/parse/__init__.py",
line 99, in handle
return h['handle'](fn, data, include)
File
"/home/kashyap/kashyap/yocto/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py",
line 120, in handle
abs_fn = resolve_file(fn, data)
File "/home/kashyap/kashyap/yocto/poky/bitbake/lib/bb/parse/__init__.py",
line 117, in resolve_file
raise IOError("file %s not found in %s" % (fn, bbpath))
IOError: file conf/bitbake.conf not found in
/home/kashyap/kashyap/yocto/poky/pi_1
ERROR: Unable to parse conf/bitbake.conf: file conf/bitbake.conf not found
in /home/kashyap/kashyap/yocto/poky/pi_1
any idea?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] File system for alternate partition
On Tuesday 24 June 2014 17:09:29 Bollinger, Seth wrote: > >I guess I didn¹t think about using a full image as I would need to remove > >a bunch of stuff, but maybe that is the best way. That way I can keep the > >flexibility of defining recipes that would be installed to my data > >partition image. I will give it a try. > > > So I created an empty image without any packages being added. As I > suspected, there’s cruft that I don’t really need in the FS. What’s the > best way to remove these, post processing? > > data-image-base/1.0-r0/rootfs/ > ├── etc > │ └── rcS.d > ├── lib > │ └── modules > │ └── 3.10.16-dey+gf167640 > └── var > └── lib > └── opkg You could just delete these within a function added to ROOTFS_POSTPROCESS_COMMAND, and that's probably the way to deal with it for now; however for the future I do think the build system ought to be able to clean these files up itself if they aren't supposed to be there. I've created a bug to track the issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6478 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
