From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-02-04
Date: Fri, 5 Feb 2021 22:34:53 +0100 [thread overview]
Message-ID: <20210205213453.GZ2384@scaer> (raw)
In-Reply-To: <87lfc27474.fsf@dell.be.48ers.dk>
Peter, All,
On 2021-02-05 19:35 +0100, Peter Korsgaard spake thusly:
> >>>>> "Heiko" == Heiko Thiery <heiko.thiery@gmail.com> writes:
> >> mipsel | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/da0e36543cf68e4e9bbe819945a884193f33819a
[--SNIP--]
> > So I see here 3 possible solutions:
> > 1. do the PRE_INSTALL_HOOK to remove the files every time (disclaimed by Yann).
> > 2. remove this files by hand (no long term solution).
> > 3. disable the installation of the yang modules .. but then we have a
> > non functional installation available and we leave the installation of
> > the yang modules to the user.
>
> Ideally the package should be fixed to create those files in
> $DESTDIR/dev/shm rather than mess around with the host /dev/shm.
>
> But as /dev/shm is not persistent, how does this work at runtime? What
> do those files do exactly?
They are shared memory.
From shm_overview(7):
On Linux, shared memory objects are created in a (tmpfs(5)) virtual
filesystem, normally mounted under /dev/shm. [...]
There is in fact nothing wrong in creating such shm objects during the
build.
What is wrong, is leaving them lingering about...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-02-05 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <601cff45.1c69fb81.945af.db28SMTPIN_ADDED_MISSING@mx.google.com>
2021-02-05 14:42 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-02-04 Heiko Thiery
2021-02-05 17:58 ` Peter Seiderer
2021-02-05 18:35 ` Peter Korsgaard
2021-02-05 21:34 ` Yann E. MORIN [this message]
2021-02-05 21:41 ` Peter Korsgaard
2021-02-06 9:36 ` Heiko Thiery
2021-02-05 22:43 ` Peter Seiderer
2021-02-06 9:32 ` Heiko Thiery
2021-02-05 21:32 ` Yann E. MORIN
2021-02-05 23:37 ` Yann E. MORIN
2021-02-06 9:37 ` Heiko Thiery
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=20210205213453.GZ2384@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.