From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] support/dependencies: ensure we have 'file' on the host
Date: Tue, 27 Dec 2016 18:07:46 +0100 [thread overview]
Message-ID: <20161227180746.438a98a6@free-electrons.com> (raw)
In-Reply-To: <1482775110-24421-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Mon, 26 Dec 2016 18:58:30 +0100, Yann E. MORIN wrote:
> Recently, the autoconf macros for libtool started using '/usr/bin/file'
> to determine the type of library that is generated by the toolchain.
> Packages that use this recent version of the libtool autoconf macros
> will fail in a rather dramatic way when /usr/bin/file is not present
> on the host: the package will still build but no shared library is
> generated, which in turn may cause build failures in other packages
> that link with it.
>
> For example, libpng's configure determines that it is not possible to
> build a shared library on MIPS64 because the expected output from 'file'
> is not present. Therefore, only a static libpng.a is built. Later,
> bandwithd links with -lpng but it doesn't use the pkg-config's
> Private-Libs (because it's not linking statically) and it doesn't have
> access to the NEEDED reference from the shared library. Therefore, it
> doesn't link with zlib and fails with
>
> pngrutil.c:(.text+0x55c): undefined reference to `inflate'
>
> We cant use host-file because it is itself an autotools package and is
> itself using libtool, so this would be a chicken-n-egg problem. Besides,
> the libtool script really wants to call /usr/bin/file, so it would not
> even find our host-file anyway.
>
> So, just require that '/usr/bin/file' is present on the host.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Baruch Siach <baruch@tkos.co.il>
>
> ---
> Changes v2 -> v3:
> - explicitly check for /usr/bin/file (arnout)
> - reword commit log (Arnout)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-27 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 17:58 [Buildroot] [PATCH v3] support/dependencies: ensure we have 'file' on the host Yann E. MORIN
2016-12-27 9:35 ` Arnout Vandecappelle
2016-12-27 17:07 ` Thomas Petazzoni [this message]
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=20161227180746.438a98a6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox