Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/mpd: add choice between version 0.19 and 0.20
Date: Thu, 16 Feb 2017 09:14:12 +0100	[thread overview]
Message-ID: <1487232852.7095.1.camel@embedded.rocks> (raw)
In-Reply-To: <20170215215533.72835dbf@free-electrons.com>

Hi Thomas,

On Wed, 2017-02-15 at 21:55 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 15 Feb 2017 15:51:02 +0100, J?rg Krause wrote:
> > MPD version 0.20 being affected by GCC PR libstdc++/64735 means no
> > mpd package
> > available in Buildroot for the architectures NIOSII, ARMv4, ARMv5
> > and SPARCv8
> > until GCC 7 is released.
> > 
> > As the next Buildroot release is in 2017.02, which is before GCC 7
> > is expected
> > to be finished we add hidden config symbols to select the version
> > branch to use.
> > 
> > Note, that we bumped the version from 0.19 to 0.20 quite recently
> > within the
> > current Buildroot release cycle. This way we can keep the support
> > for mpd on
> > the affected architectures, like ARMv5, until GCC 7 is out.
> > 
> > Note, that for the version 0.19 MPD requires libglib2.
> > 
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> > Note that this patch is targeted for the master branch.
> 
> Applied to master, thanks.

Many thanks! Unfortunately, I just discovered a mistake in the patch.
I'll send a patch to fix the issue.

J?rg

  reply	other threads:[~2017-02-16  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 14:51 [Buildroot] [PATCH v3] package/mpd: add choice between version 0.19 and 0.20 Jörg Krause
2017-02-15 20:55 ` Thomas Petazzoni
2017-02-16  8:14   ` Jörg Krause [this message]
2017-02-16  8:34     ` Thomas Petazzoni

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=1487232852.7095.1.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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