From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/efl/libevas: x-includes and x-libraries must be set for cross-compiling
Date: Sun, 3 May 2015 11:46:28 +0200 [thread overview]
Message-ID: <20150503114628.37e24683@free-electrons.com> (raw)
In-Reply-To: <1430597796-23584-1-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Sat, 2 May 2015 22:16:36 +0200, Romain Naour wrote:
> evas_engine_software_xlib_cflags and evas_engine_software_xlib_libs
> contains unsafe libraries paths if x-include and x-libraries are
> not set in libevas.mk.
>
> config.log:
> evas_engine_software_xlib_cflags='-I/usr/X11R6/include'
> evas_engine_software_xlib_libs='-L/usr/X11R6/lib -lX11 -lXext'
>
> Fixes:
> http://autobuild.buildroot.net/results/e5f/e5fb1e62cb634b20233751b4ea3b0630de70e9e0/
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> package/efl/libevas/libevas.mk | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Applied, thanks. I've done a second commit on libecore with the exact
same fix, because the exact same problem occurred on libecore in my
test build. See
http://git.buildroot.net/buildroot/commit/?id=0d9d8984a9240a27f5ed2e15f1977ada67266906.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-03 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 20:16 [Buildroot] [PATCH] package/efl/libevas: x-includes and x-libraries must be set for cross-compiling Romain Naour
2015-05-03 9:46 ` Thomas Petazzoni [this message]
2015-05-03 10:00 ` Romain Naour
2015-05-03 10:15 ` Thomas Petazzoni
2015-05-03 10:23 ` Romain Naour
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=20150503114628.37e24683@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 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.