Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-02-25
Date: Mon, 26 Feb 2018 15:06:20 +0100	[thread overview]
Message-ID: <87bmgbsv4z.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180226140029.45325514@windsurf.lan> (Thomas Petazzoni's message of "Mon, 26 Feb 2018 14:00:29 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 >> > I guess this is fixed by the old patches submitted by Bernd, which are
 >> > still in patchwork. I'm still not super happy about these patches,
 >> > though (as I already expressed as a reply to those patches).  
 >> 
 >> Agreed, but what are the alternatives? Make the package unavailable for
 >> x86 or drop it completely, as it is afaik dead upstream.

 > mplayer upstream is dead ? If that is the case, then indeed we should
 > just take those patches as-is.

I haven't followed development in details, but the latest mplayer
release is more than 2 years old and several forks exists (E.G. mpv).


 >> > tools/qtextboundaryfinder.cpp:444:1: internal compiler error: in
 >> > validate_condition_mode, at config/rs6000/rs6000.c:18074  
 >> 
 >> > Someone to test this with newer gcc versions ?  
 >> 
 >> Or deprecate qt4?

 > Just because it's broken on powerpc?

Well, mainly because it is no longer maintained upstream. Even Debian is
removing Qt4:

https://wiki.debian.org/Qt4Removal

 >> Agreed, considering how close we are getting to 2018.02.

 > We also have the issue that systemd is currently broken anyway (see the
 > report from J?r?my Rosen, the attempt to fix it from Jan and Romain). I
 > don't think we can release until this problem is resolved.

Agreed!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-02-26 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-02-25 Thomas Petazzoni
2018-02-26 10:33 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-02-26 10:51   ` Johan Oudinet
2018-02-26 10:58     ` Thomas Petazzoni
2018-02-26 13:44     ` Frank Hunleth
2018-02-26 12:48   ` Peter Korsgaard
2018-02-26 13:00     ` Thomas Petazzoni
2018-02-26 14:06       ` Peter Korsgaard [this message]
2018-02-26 14:47         ` Thomas Petazzoni
2018-02-26 19:01           ` Peter Korsgaard
2018-03-01 19:41             ` Arnout Vandecappelle
2018-03-01 21:17               ` Peter Korsgaard
2018-02-27 12:08     ` Peter Seiderer
2018-02-27 13:12       ` Peter Korsgaard
2018-02-26 15:30   ` Mahyar Koshkouei
2018-02-26 15:40     ` 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=87bmgbsv4z.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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