[Aptitude-devel] Bug#777778: Bug#792681: cwidget ftbfs with GCC 5

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Mon Jul 20 15:02:00 UTC 2015


2015-07-20 15:24 GMT+01:00 Matthias Klose <doko at debian.org>:
> On 07/18/2015 11:29 PM, Manuel A. Fernandez Montecelo wrote:
>> Anyway, aptitude with GCC-5 and -std=c++98 also suffers the same problem as
>> cwidget, because it fails to compile the cwidget header, if nothing else.  But
>> if cwidget goes C++11, it forces aptitude to go C++11, and it doesn't work for
>> other reasons (that I am working to fix), so we are between a rock and a hard
>> place.
>>
>> Even if I can fix things in time before the deadline, maybe subtle changes like
>> the ABI problems make aptitude fail in catastrophic ways, there is not much time
>> to expose it and be tested before the deadline in experimental or similar.
>>
>> I am thinking that the best solution is to force them to stay with gcc-4.9 for
>> the time being, it looks the safest bet.  After that or in parallel, as soon as
>> I get things working, I can upload to experimental the changes that allow them
>> to work with C++11, and keep it there for a while before moving to unstable.
>
> no, this is definitely *not* an option.  cwidget and aptitude b-d on
> libsigc++-2, and this will be built using GCC 5.  There will be neither g++-4.9
> nor g++-4.8 in the archive once we finish this transition.  Maintainers don't
> have the choice to fall-back to an older version this time.

Right.  So I have been working through the weekend to get aptitude to
compile with -std=c++11 (working in my system but still not pushed).
As you reported, there are problems compiling aptitude with gcc-5 in
the default mode, and after the failure that you reported it will
stumble upon the same problem that cwidget when including that cwidget
header (for which passing "-std=c++11" is the simplest solution, and
also the only that I found so far).

In terms of C++-based dependencies, aptitude depends on libsigc++-2.0,
xapian-core (#791312, it will not be ready immediately but soon
enough, it seems), apt and boost (gcc-5 ready, it seems).  I don't
know the details about sigc++ and apt, but if all of them are going to
be compiled with gcc-5 soon after its move to unstable, cwidget and
aptitude will be ready as well.

Now we have to work out the details about how to upload the changes,
enable them in lockstep and avoid breakages as much as possible (e.g.
tighten versions on the compiler and lib dependencies).


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>



More information about the Aptitude-devel mailing list