Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/freerdp: can not build on uClibc
Date: Wed, 1 Oct 2014 10:00:37 +0100	[thread overview]
Message-ID: <542BC2B5.80306@imgtec.com> (raw)
In-Reply-To: <20140930192604.6fab6f24@free-electrons.com>

Dear Thomas Petazzoni,

On 09/30/2014 06:26 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Mon, 29 Sep 2014 11:12:09 +0100, Vicente Olivert Riera wrote:
>
>> I sent this patch 5 days ago to add support for uClibc for this package
>> by applying an upstream patch:
>>
>> http://patchwork.ozlabs.org/patch/392966/
>>
>> Please, take it into consideration. I think it's better to fix the
>> package instead of disabling it.
>
> Agreed.
>
> Can you resend your patch, after taking into account the comments made
> by Yann, and also making sure to re-enable freerdp with uClibc as part
> of this patch (effectively reverting Yann's patch) ?
>
> Thanks,
>
> Thomas

Done: http://patchwork.ozlabs.org/patch/395466/

-- 
Vincent

  reply	other threads:[~2014-10-01  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28 16:26 [Buildroot] [PATCH 0/4] A few autobuilder fixes (branch yem/autobuild) Yann E. MORIN
2014-09-28 16:26 ` [Buildroot] [PATCH 1/4] docs/manual: add musl to toolchain dependency options Yann E. MORIN
2014-09-28 21:17   ` Peter Korsgaard
2014-09-28 16:26 ` [Buildroot] [PATCH 2/4] package/freerdp: can not build on uClibc Yann E. MORIN
2014-09-28 21:20   ` Peter Korsgaard
2014-09-29 10:12     ` Vicente Olivert Riera
2014-09-30 17:26       ` Thomas Petazzoni
2014-10-01  9:00         ` Vicente Olivert Riera [this message]
2014-09-28 16:26 ` [Buildroot] [PATCH 3/4] package/trace-cmd: does not build on static onl; y, needs dlopen() Yann E. MORIN
2014-09-28 21:21   ` Peter Korsgaard
2014-09-28 16:26 ` [Buildroot] [PATCH 4/4] package/vde2: does not build on static only, " Yann E. MORIN
2014-09-28 21:21   ` Peter Korsgaard

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=542BC2B5.80306@imgtec.com \
    --to=vincent.riera@imgtec.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