From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Norbert Lange <nolange79@gmail.com>
Cc: joseph.kogut@gmail.com, "Adam Duskett" <aduskett@gmail.com>,
"Michał Łyszczek" <michal.lyszczek@bofc.pl>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] skeleton + init: prepare /run/lock and adjust compat symlinks
Date: Wed, 12 Jan 2022 09:14:22 +0100 [thread overview]
Message-ID: <20220112091422.1cd29c1f@windsurf> (raw)
In-Reply-To: <20201004224137.193808-1-nolange79@gmail.com>
Hello Norbert,
On Mon, 5 Oct 2020 00:41:36 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> Linux distros changed /var/run and /var/lock to reside on an tmpfs in
> /run a long time ago, and buildroot seems to agree by providing this
> tmpfs on all supported init systems.
I am not 100% sure but it seems like this patch has potentially broken
the build of vtun, which now fails with:
/usr/bin/install: cannot create directory '/home/giuliobenetti/autobuild/run/instance-0/output-1/target/var/lock': File exists
If you look at http://autobuild.buildroot.net/?reason=vtun%, vtun
version 3.0.4 restarted failing to build on January 10, with this error.
Could you have a look ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-12 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 22:41 [Buildroot] [PATCH] skeleton + init: prepare /run/lock and adjust compat symlinks Norbert Lange
2022-01-09 10:29 ` Arnout Vandecappelle
2022-01-12 8:14 ` Thomas Petazzoni [this message]
2022-01-12 8:53 ` Norbert Lange
2022-01-12 18:39 ` Arnout Vandecappelle
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=20220112091422.1cd29c1f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=joseph.kogut@gmail.com \
--cc=michal.lyszczek@bofc.pl \
--cc=nolange79@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox