On Wed, 21 Feb 2024 at 10:48, Ross Burton <ross.bur...@arm.com> wrote: > You _can_ export TMPDIR but that has to be done on a per-recipe/class basis > very carefully as TMPDIR means something else to Bitbake. > > The problem is recipes that use mktemp to write files and execute them (be it > shell scripts, or as a place to write C and then compile in the same > directory). These will be in /tmp (again, we can’t set TMPDIR because for > foolish historical reasons, TMPDIR is used by bitbake). > > We first noticed this with Meson where noexec /tmp meant the configure tests > failed. We worked around it at the time by assigning TMPDIR when calling > Meson, but since them Meson writes to its own build tree now. This has been > seen before though, but luckily noexec /tmp is fairly unusual so I doubt this > will break many builds.
I'm actually curious where noexec /tmp can be observed. It does seem rare, because I think it's the first time someone came up with a sanity check for it. Perhaps it should be treated as a bug in that respective environment/OS/container? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195965): https://lists.openembedded.org/g/openembedded-core/message/195965 Mute This Topic: https://lists.openembedded.org/mt/104258828/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
