Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-22 Thread Martin Michlmayr
reopen 812287
reassign 812287 gcc-6 6-20160117-1
retitle 812287 test suites segfault / constexpr leaves reference member var 
uninitialized
forwarded 812287 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69327
thanks

* Rene Engelhard  [2016-01-22 13:01]:
> That reminds me of
> https://whatofhow.wordpress.com/2016/01/20/gcc-6/

Thanks for tracking that down!  Let's reassign the bug against gcc-6.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise



Bug#811686: Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-22 Thread Rene Engelhard
notfound 812287 0.1.6-1
close 812287
thanks

Hi,

On Thu, Jan 21, 2016 at 08:03:11PM -0800, Martin Michlmayr wrote:
> Unfortunately, it's not clear from the log why the build failed.
> It's possible there's a bug in this package or in GCC.  It's also

Seems as GCC. See below.

> possible I reported a non-issue, although I tried to avoid that.

It probably is. See below.

> I apologize in advance if this is the case.

No problem.

> If you have some time to look into this issue, that'd be great.  If
> not, I can re-test the package with GCC 6 in a few weeks time.
[...]

That reminds me of

https://whatofhow.wordpress.com/2016/01/20/gcc-6/

Especially the

"PR69327 “constexpr leaves reference member var uninitialized”—that one took a 
long time to track down and reduce, because it hid in boost::fusion code called 
from boost::spirit code called from external libetonyek code. Patch at “GCC 6 
PR69327 workaround.”"

Interestingly, the test Stephan mentions in LO does NOT crash for me...
But still even with uptodate gcc snapshot for Stephan.

But as it ringed a bell I tried a build with libetonyek with a unnpatched boost
(fails, as described in this report) and a patched boost.
Wasn't able to rebuild boost with gcc6 as #811651 blocks that but I patched
the headers in-place and libetonyek builds after that.

Now either boost gets the above-mentioned patch or gcc gets fixed.. Then
libetonyek will build without changes..

So this is (IMHO) no bug in libetonyek and this bug should be closed.

Regards,

Rene



Bug#812287: libetonyek: FTBFS with GCC 6: test suite segfaults

2016-01-21 Thread Martin Michlmayr
Package: libetonyek
Version: 0.1.6-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[4]: Leaving directory '/<>/src/test'
> make  check-TESTS
> make[4]: Entering directory '/<>/src/test'
> make[5]: Entering directory '/<>/src/test'
> PASS: detection
> ../../test-driver: line 107: 12919 Segmentation fault  "$@" > $log_file 
> 2>&1
> FAIL: test
> 
> Testsuite summary for libetonyek 0.1.6
> 
> # TOTAL: 2
> # PASS:  1
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See src/test/test-suite.log
> 
> Makefile:1127: recipe for target 'test-suite.log' failed
> make[5]: *** [test-suite.log] Error 1
> make[5]: Leaving directory '/<>/src/test'
> Makefile:1233: recipe for target 'check-TESTS' failed
> make[4]: *** [check-TESTS] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise