From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-17
Date: Wed, 18 Aug 2021 22:18:42 +0200 [thread overview]
Message-ID: <20210818221842.5926641d@windsurf> (raw)
In-Reply-To: <20210818110558.GY27036@scaer>
Hello,
On Wed, 18 Aug 2021 13:05:58 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Not sure the exact reason, but notice that the failures occur at install
> time, not build time.
I did try with "make host-libcap", which includes the installation
step, and I even tried to do a full build of one of the failing
defconfigs. The build failed, but much much later, on a completely
unrelated package. And manually checking the RPATH of the host-libcap
binaries: they are correct.
> And even then, the Makefile is still trying to
> compile some stuff.
>
> libcap is a generic package, and I noticed that the build and install
> commands do not use the same environment:
>
> define HOST_LIBCAP_BUILD_CMDS
> $(HOST_MAKE_ENV) $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) \
> $(HOST_LIBCAP_MAKE_FLAGS)
> endef
>
> define HOST_LIBCAP_INSTALL_CMDS
> $(HOST_MAKE_ENV) $(MAKE) -C $(@D) $(HOST_LIBCAP_MAKE_FLAGS) install
> endef
>
> So I wonder if, at least for sanity sake, we should not just add
> $(HOST_CONFIGURE_OPTS) in the environment for the install commands too.
I'm not sure how that could cause an issue, as I'm building on the same
machine, same defconfig.
> Also, notice spurious errors from ldconfig:
>
> /sbin/ldconfig
> /sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Permission denied
> make[5]: [Makefile:162: install-shared-psx] Error 1 (ignored)
>
> (ldconfig is a wrapper around ldconfig.real, specific to debian and.or
> ubuntu I guess)
Right, but the absence/presence of the RPATH should normally not be
affected by this, I believe.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-18 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 6:57 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-17 Thomas Petazzoni
2021-08-18 10:25 ` Thomas Petazzoni
2021-08-18 11:05 ` Yann E. MORIN
2021-08-18 20:18 ` Thomas Petazzoni [this message]
2021-08-18 21:04 ` Yann E. MORIN
2021-08-23 20:55 ` Arnout Vandecappelle
2021-08-23 22:06 ` Thomas Petazzoni
2021-08-23 22:16 ` Arnout Vandecappelle
2021-08-18 21:44 ` [Buildroot] Analysis of build " Thomas Petazzoni
2021-08-18 22:24 ` Giulio Benetti
2021-08-18 22:26 ` Giulio Benetti
2021-08-19 0:01 ` Giulio Benetti
2021-08-19 13:28 ` Thomas Petazzoni
2021-08-20 14:26 ` Giulio Benetti
2021-08-20 22:00 ` Giulio Benetti
2021-08-21 23:08 ` Giulio Benetti
2021-08-19 9:27 ` Arnout Vandecappelle
2021-08-19 13:24 ` Thomas Petazzoni
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=20210818221842.5926641d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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