From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-16
Date: Mon, 20 Feb 2017 23:40:39 +0100 [thread overview]
Message-ID: <87a89gpjtk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170220134111.1bc02a9f@free-electrons.com> (Thomas Petazzoni's message of "Mon, 20 Feb 2017 13:41:11 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> > x86_64 | oracle-mysql-5.1.73 | NOK |
>> > http://autobuild.buildroot.net/results/e9ff38bea523df79331de3004939ee39b446d723
>>
>> error: narrowing conversion [...] from 'char' to 'uchar...'
>>
>> Damn gcc6... ;-) Should be easy; any taker?
> I had a quick look, it's not that trivial if you want the correct fix.
> And of course, mysql 5.1.73 is very very old, upstream is now at 5.7.17
> (https://dev.mysql.com/downloads/mysql/). So I would like to suggest
> that we mark oracle-mysql as BR2_BROKEN, and wait to see if anyone is
> interested to fix this during the next release cycle.
I agree. There has also recently been some security issues, but like you
say our package is ancient.
Will you send a patch?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-02-20 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-16 Thomas Petazzoni
2017-02-17 21:12 ` Yann E. MORIN
2017-02-17 22:01 ` Yann E. MORIN
2017-02-17 22:02 ` Waldemar Brodkorb
2017-02-18 8:49 ` Peter Korsgaard
2017-02-20 12:41 ` Thomas Petazzoni
2017-02-20 14:59 ` Waldemar Brodkorb
2017-02-20 15:10 ` Thomas Petazzoni
2017-02-20 18:14 ` Bernd Kuhls
2017-02-20 22:40 ` Peter Korsgaard [this message]
2017-02-20 22:46 ` Thomas Petazzoni
2017-02-20 22:59 ` Peter Korsgaard
2017-02-21 8:05 ` Arnout Vandecappelle
2017-02-21 8:27 ` Thomas Petazzoni
2017-02-21 8:46 ` Arnout Vandecappelle
2017-02-21 8:55 ` Thomas Petazzoni
2017-02-24 14:37 ` Julien Boibessot
2017-02-24 14:48 ` Thomas Petazzoni
2017-02-25 1:47 ` Waldemar Brodkorb
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=87a89gpjtk.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