Your message dated Wed, 2 Mar 2016 17:29:47 -0800
with message-id <[email protected]>
and subject line Re: Bug#811712: oolite: FTBFS with GCC 6: unknown type name
has caused the Debian Bug report #811712,
regarding oolite: FTBFS with GCC 6: unknown type name
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
811712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811712
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: oolite
Version: 1.82-1
Severity: important
User: [email protected]
Usertags: ftbfs-gcc-6 gcc-6-unknown-type-name
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.
Note that only the first error is reported; there might be more. 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
...
> src/Core/Entities/ShipEntity.m:844:2: error: unknown type name 'NSArray'
> NSArray *subs = [shipDict oo_arrayForKey:@"subentities"];
> ^~~~~~~
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
* Martin Michlmayr <[email protected]> [2016-01-19 17:33]:
> Package: oolite
> Version: 1.82-1
>
> 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.
The package builds fine with GCC 6 6-20160228-1. Since the package
itself didn't change, I guess that either a bug in GCC 6 got fixed or
possibly a header in another package.
It seems likely that this is the same issue that Matt Kraai explained
in #811710.
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
