Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
Date: Wed, 01 Oct 2014 21:41:16 +0200	[thread overview]
Message-ID: <542C58DC.2080704@posteo.de> (raw)
In-Reply-To: <20141001213513.1dedb82c@free-electrons.com>


On 10/01/2014 09:35 PM, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Wed, 01 Oct 2014 21:31:16 +0200, J?rg Krause wrote:
>> On 10/01/2014 08:30 AM, Thomas Petazzoni wrote:
>>> Build statistics for 2014-09-30
>>> ===============================
>>>
>>>            sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/e5be8fe46a30f0b417fe5fc19a27c480d885791e/
>> missing <cstdio>.
>>
>>>            sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/a3453afddff4fc03681f7fbdff3ccab9706eb189/
>> same.
>>
>> I will inform the developer of upmpdcli and submit a patch soon.
> Great, thanks a lot!
>

Hi Thomas,

I have a question to the patch you added to upmpdcli some month ago. You 
added among other things #define _GNU_SOURCE to upmpd/upmpdutils.cxx. 
Can you remember why?

The developer of upmpdcli asked me...he wants to submit the patch upstream.

Best regards
J?rg Krause

      parent reply	other threads:[~2014-10-01 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30 Thomas Petazzoni
2014-10-01 12:51 ` Mike Zick
2014-10-01 16:23   ` Thomas Petazzoni
2014-10-01 16:38     ` Mike Zick
2014-10-02  8:54     ` Luca Ceresoli
     [not found] ` <542C5684.8050201@posteo.de>
     [not found]   ` <20141001213513.1dedb82c@free-electrons.com>
2014-10-01 19:41     ` Jörg Krause [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=542C58DC.2080704@posteo.de \
    --to=jkrause@posteo.de \
    --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