Federico Bruni writes:
In fact, lilypond is another package affected:
https://bugzilla.redhat.com/show_bug.cgi?id=1568274
http://lists.gnu.org/archive/html/lilypond-user/2018-05/msg00081.html
It's been my experience, over the last decade, or so, that each successive
major gcc release has had
Il giorno lun 7 mag 2018 alle 13:28, John Pilkington
ha scritto:
On 07/05/18 12:14, Jakub Jelinek wrote:
On Mon, May 07, 2018 at 10:40:39AM +0100, John Pilkington wrote:
On 07/05/18 10:13, Jakub Jelinek wrote:
On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote:
The MythTV list
On 07/05/18 12:14, Jakub Jelinek wrote:
On Mon, May 07, 2018 at 10:40:39AM +0100, John Pilkington wrote:
On 07/05/18 10:13, Jakub Jelinek wrote:
On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote:
The MythTV lists have had several reports of problems apparently arising
from new (a
On Mon, May 07, 2018 at 10:40:39AM +0100, John Pilkington wrote:
> On 07/05/18 10:13, Jakub Jelinek wrote:
> > On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote:
> > > The MythTV lists have had several reports of problems apparently arising
> > > from new (and improved) vector-validat
On 07/05/18 10:13, Jakub Jelinek wrote:
On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote:
The MythTV lists have had several reports of problems apparently arising
from new (and improved) vector-validation in gcc8. Is there a temporary
workaround?
If you don't provide details (l
On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote:
> The MythTV lists have had several reports of problems apparently arising
> from new (and improved) vector-validation in gcc8. Is there a temporary
> workaround?
If you don't provide details (links to the reports, etc.), then it is
