From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3, 1/1] package/ecryptfs-utils: fix parallel build
Date: Thu, 26 Dec 2019 20:44:33 +0100 [thread overview]
Message-ID: <20191226204433.785cbbc2@windsurf> (raw)
In-Reply-To: <20191226164748.28083-1-fontaine.fabrice@gmail.com>
On Thu, 26 Dec 2019 17:47:48 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Build randomly fails since December 2017 on:
>
> make[5]: Entering directory '/home/buildroot/autobuild/instance-2/output-1/build/ecryptfs-utils-111/src/utils'
> /bin/mkdir -p '/home/buildroot/autobuild/instance-2/output-1/target/sbin'
> /bin/bash ../../libtool --mode=install /usr/bin/install -c mount.ecryptfs umount.ecryptfs mount.ecryptfs_private '/home/buildroot/autobuild/instance-2/output-1/target/sbin'
> libtool: install: /usr/bin/install -c mount.ecryptfs /home/buildroot/autobuild/instance-2/output-1/target/sbin/mount.ecryptfs
> /usr/bin/install: cannot create regular file '/home/buildroot/autobuild/instance-2/output-1/target/sbin/mount.ecryptfs': File exists
> Makefile:832: recipe for target 'install-rootsbinPROGRAMS' failed
> make[5]: *** [install-rootsbinPROGRAMS] Error 1
>
> Fixes:
> - http://autobuild.buildroot.org/results/2063bd18830ef02dca0bed889c43639009bc688e
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v2 -> v3 (after review of Thomas Petazzoni):
> - Update Makefile.in instead of Makefile.am to avoid running autoreconf
> which depends on AM_GLIB_GNU_GETTEXT
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-26 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 16:47 [Buildroot] [PATCH v3, 1/1] package/ecryptfs-utils: fix parallel build Fabrice Fontaine
2019-12-26 19:44 ` Thomas Petazzoni [this message]
2020-01-07 22:10 ` Peter Korsgaard
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=20191226204433.785cbbc2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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.