All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Baumann, Michael" <Michael.Baumann@vector.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: how to create a named_pipe in my image
Date: Mon, 8 Feb 2016 16:12:04 +0000	[thread overview]
Message-ID: <D3B58608AFC8B244BA0ACD53B2AE612598EEF622@vistrex4.vi.vector.int> (raw)
In-Reply-To: <D3B58608AFC8B244BA0ACD53B2AE612598EEF5C6@vistrex4.vi.vector.int>

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 circumvent this?

Regards
Michael

>-----Original Message-----
>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>bounces@yoctoproject.org] On Behalf Of Baumann, Michael
>Sent: Monday, February 08, 2016 4:07 PM
>To: yocto@yoctoproject.org
>Subject: [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 <image>.bb file in the do_install() section with "mkfifo
><path_to_pipe_in_target_fs>"
>
>Any ideas gratefully received.
>
>Regards
>Michael
>--
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto


  reply	other threads:[~2016-02-08 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 15:06 how to create a named_pipe in my image Baumann, Michael
2016-02-08 16:12 ` Baumann, Michael [this message]
2016-02-08 16:14   ` Burton, Ross
2016-02-08 16:39     ` Baumann, Michael
2016-02-08 17:36       ` Burton, Ross
2016-02-08 20:36         ` Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D3B58608AFC8B244BA0ACD53B2AE612598EEF622@vistrex4.vi.vector.int \
    --to=michael.baumann@vector.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.