Heiko, All,
On 2021-02-05 15:42 +0100, Heiko Thiery spake thusly:
Am Fr., 5. Feb. 2021 um 09:18 Uhr schrieb Thomas Petazzoni
[off-list ref]:
quoted
xtensa | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/e21834d4d2ee580f00f0fdcbd3728787148c0da9
nios2 | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/e9bfe730da3faec5884e8950855a34541c3408a9
microblazeel | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/99ca5aa18074b19f2e6a311c2d38addb697f552b
powerpc | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/2b9ad4626a1b6918a8e8d586521626306f5f8133
microblazeel | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/65108399fb6d7b02d812bc15d5074bfd404764c5
nios2 | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/6730e1e6ceebec94a9ad27deac0a4d1bf4661536
powerpc | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/16bf1c3b4059a159480d23e6e132dcff05bd9b96
powerpc64le | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/985aac8fd746c64e4ad0e093028164d8ae637409
mipsel | netopeer2-1.1.53 | http://autobuild.buildroot.net/results/da0e36543cf68e4e9bbe819945a884193f33819a
I checked the reason for the build failure on the netopeer2 package.
It is caused by some files that are created in /dev/shm/sr_* during
the installation process.
I tried to find a solution for that. My first intention was to do a
PRE_INSTALL_HOOK that deletes these files before the installation. But
YANN disclaimed that because we should never delete files in
*Yann, please. ;-)
So, first, there was a misunderstanding on my side. I thought /dev/shm
would contain system-level nodes. But I was confused, probably with pts
et al. Anyway, /dev/shm is the place where glibc will first look at to
create the files that backs shared memoru (shm). Removing files in there
is in fact not an issue per-se (although leftover files means something
is not cleaning up nicely behind them, and misses calling shm_unlink()).
Second, once I noticed that, my oposition to removing files in there is
that it can remove more than expected, and espcially, it may removes
frils from another, concurrent run. So we can not removes files using
wildcards.
Removing /dev/shm/sr_* is wrong.
/dev/shm/. This could lead to failures when doing concurrent parallel
builds.
That.
To be more detailed what is going on:
The netopeer2 package can install the required yang models for runtime
during installation. Therefore an additional script (setup.sh) is
invoked. There the sysrepocfg host tool is used to do the installation
of these yang models. sysrepo will then create this /dev/shm files and
leave them. But with the updated netopeer2 package the shm files are
incompatible and the build errors appear.
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.
What do you think?
4. Fix sysrepo to clean up when it quits.
And also make sure nothing is left running that still have those shared
ememory opened (e.g. a forked sysrepo still lurking in the background?)
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. |
'------------------------------^-------^------------------^--------------------'