From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libgdiplus: new package
Date: Fri, 18 Dec 2015 11:41:17 +0100 [thread overview]
Message-ID: <20151218114117.5d273ce1@free-electrons.com> (raw)
In-Reply-To: <20151217222952.28cfb35c@free-electrons.com>
Hello,
On Thu, 17 Dec 2015 22:29:52 +0100, Thomas Petazzoni wrote:
> Other than that, I couldn't spot any issue, so I applied. Don't
> hesitate to monitor http://autobuild.buildroot.org and/or the daily
> autobuild report e-mails to see if there are any libgdiplus related
> failures.
There are some build issues:
http://autobuild.buildroot.org/?reason=libgdiplus-3.12
There is a -L/lib somewhere which is wrong. Could you have a look?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-18 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 0:15 [Buildroot] [PATCH v3] libgdiplus: new package Sergio Prado
2015-12-17 21:29 ` Thomas Petazzoni
2015-12-17 23:45 ` Sergio Prado
2015-12-18 10:41 ` Thomas Petazzoni [this message]
2015-12-18 10:56 ` Sergio Prado
2015-12-18 18:12 ` Sergio Prado
2015-12-18 19:04 ` Thomas Petazzoni
2015-12-18 19:13 ` Sergio Prado
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=20151218114117.5d273ce1@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