[yocto] fortran in yocto

Hi, I want to add fortran support to yocto build. I try different way whitch describe in the ethernet but enyone does't work. I use fido branch and gcc 4.9. Can you describe me step by step how to enable fortran in yocto or where I can find work instruction. Thanks for help. Best regards, St

[yocto] Release Candidate Build for yocto-2.0.1.rc6.rc6 now available.

A release candidate build for yocto-2.0.1.rc6 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc6 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 4e87c59bdedaa8c3e44fc02fd23be726c4d1dfb9 meta-fsl-arm : 35b8b9bd9863d

Re: [yocto] fortran in yocto

Hi On Mon, 8 Feb 2016 08:19:53 + "Liubchynskyi, Stanislav (Nokia - PL/Wroclaw)" wrote: > Hi, > I want to add fortran support to yocto build. I try different way whitch > describe in the ethernet but enyone does't work. I use fido branch and gcc > 4.9. Can you describe me step by step how

Re: [yocto] Installing only part of linux-firmware

On 7 February 2016 at 21:49, Chris Tapp wrote: > I’ve now done this by creating a bbappend for linux-firmware: > > PACKAGES =+ "${PN}-rtl_nic" > > FILES_${PN}-rtl_nic = " \ > /lib/firmware/rtl_nic/* \ > “ > > Does what I want, but is that the best way of doing it? > This is the best way for yo

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

The problem is, it doesn't doit delirebately, when I run bitbake -f -c latest_link myrecipe , it works when the process is in the tasks batch running bitbake myrecipe it doesn't What am I doing wrong ? Kind regards, Bartosz Woronicz Engineer, Software Configuration (SCM) NSN - PL/Wroclaw On 0

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On pon, 2016-02-08 at 14:20 +0100, Woronicz, Bartosz ( NSN - PL/Wroclaw) wrote: > The problem is, it doesn't doit delirebately, > > when I run > > bitbake -f -c latest_link myrecipe , it works > > when the process is in the tasks batch running > bitbake myrecipe > it doesn't > What am I doing wr

[yocto] [Build dependencies]

Hello, I am trying to use some things from one recipe in another the things what I did: Defined default package with files the next step I added in another recipe dependencies field. So as I check defaul .rpms was generated with proper contain. But when I look to my child recipe there is no fi

[yocto] how to create a named_pipe in my image

Hi, I try to create a named pipe (fifo) for my target filesystem. I tried it in my .bb file in the do_install() section with "mkfifo " Any ideas gratefully received. Regards Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoc

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 5 February 2016 at 10:45, Reshetova, Elena wrote: > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > > > > or even simple: > > > > recipe.r_deps = d.getVar('RDEPENDS’, True) > > Did you mean RDEPENDS_ + package name? Ross -- ___ yocto ma

Re: [yocto] how to create a named_pipe in my image

To make my question more precise: mkfifo in the do_install() section works. I can see the named pipe in build/tmp-glibc/work/*/*/*/ but my bitbake hangs in the do_package_write_ipk and do_package_qa tasks. Possibly it's because named pipes cannot be packed into an archive? If yes, how can I ci

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:12, Baumann, Michael wrote: > Possibly it's because named pipes cannot be packed into an archive? If > yes, how can I circumvent this? > It would be interesting to see what happens if you change PACKAGE_CLASSES to use rpm instead of ipkg. One workaround would be to crea

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 5 February 2016 at 10:45, Reshetova, Elena mailto:elena.reshet...@intel.com> > wrote: recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) or even simple: recipe.r_deps = d.getVar('RDEPENDS’, True) >Did you mean RDEPENDS_ + package name? I have it lik

Re: [yocto] how to create a named_pipe in my image

Thank you Ross. Switching to rpm package showed the same behavior. Is there another workaround than a post install script? Regards, Michael From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Monday, February 08, 2016 5:15 PM To: Baumann, Michael Cc: yocto@yoctoproject.org Subject: Re: [yocto

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

On 8 February 2016 at 16:20, Reshetova, Elena wrote: > >Did you mean RDEPENDS_ + package name? > > > > I have it like this: > > > > recipe.name = d.getVar('PN', True) > > recipe.r_deps = d.getVar('RDEPENDS_' + recipe.name, True) > So I wasn't quite right - I think you also need to come after do_

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 16:39, Baumann, Michael wrote: > Switching to rpm package showed the same behavior. > > Is there another workaround than a post install script? > > So I had a quick look at this. The fifo certainly ends up in the resulting ipk at least, but as you say package_qa hangs. It'

[yocto] Release Candidate Build for yocto-2.0.1.rc6.rc6 now available.

-e A release candidate build for yocto-2.0.1.rc6 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc6 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 4e87c59bdedaa8c3e44fc02fd23be726c4d1dfb9 meta-fsl-arm : 35b8b9bd98

Re: [yocto] how to create a named_pipe in my image

On 8 February 2016 at 17:36, Burton, Ross wrote: > So I had a quick look at this. The fifo certainly ends up in the > resulting ipk at least, but as you say package_qa hangs. It's probably > encountering a non-file and breaking somewhere. A really nasty workaround > until this is fixed would b

Re: [yocto] What is the correct way to get a list of package run-time dependencies during the build process?

>So I wasn't quite right - I think you also need to come after do_packagedata >and also you'll need to read the subpackage metadata. Inspired by >insane.bbclass, this works: >addtask printrdeps before do_build after do_package do_packagedata >do_printrdeps[nostamp] = "1" >python do_printrde