From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libgdiplus: fix cross-compilation error
Date: Fri, 18 Dec 2015 22:05:11 +0100 [thread overview]
Message-ID: <20151218220511.10f22648@free-electrons.com> (raw)
In-Reply-To: <1450461645-28534-1-git-send-email-sergio.prado@e-labworks.com>
Dear Sergio Prado,
On Fri, 18 Dec 2015 16:00:45 -0200, Sergio Prado wrote:
> When cross-compiling with toolchains that validate things like headers
> and libraries paths, we were getting errors like:
>
> sh-linux-gnu-gcc: ERROR: unsafe header/library path used in
> cross-compilation: '/lib'
>
> That's because there was an error in the configure script that was not
> generating ldflags correctly, and the generated Makefile was trying to
> link with -L/lib.
>
> Also, it is necessary to pass a prefix when compiling with libjpeg and
> libtiff support.
>
> A patch has already been sent upstream.
>
> Fixes:
> http://autobuild.buildroot.org/results/58cad610b1bde68de82e44bf3c87d7bfcc1fa816/
> http://autobuild.buildroot.org/results/649c258c05293fa5203d7d2c7b20a4265c2815ab/
>
> Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
> ---
> ...01-Fix-compile-error-when-cross-compiling.patch | 35 ++++++++++++++++++++++
> package/libgdiplus/libgdiplus.mk | 4 +--
> 2 files changed, 37 insertions(+), 2 deletions(-)
> create mode 100644 package/libgdiplus/0001-Fix-compile-error-when-cross-compiling.patch
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-18 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 18:00 [Buildroot] [PATCH 1/1] libgdiplus: fix cross-compilation error Sergio Prado
2015-12-18 21:05 ` 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=20151218220511.10f22648@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