* Andreas Tille ti...@debian.org, 2015-07-09, 06:28:
So I'm tempted to close this bug
Too late, it's already closed. :)
since I do not see a good reason to stop the propagation of the latest
version to testing which has closed the original bug.
Testing migration is stopped only only by new
On Wed, Jul 01, 2015 at 01:04:06PM +0200, Jakub Wilk wrote:
* Andreas Tille andr...@an3as.eu, 2015-07-01, 09:32:
../mira/libmira.a(assembly_io.o): In function
`boost::re_detail::perl_matcher__gnu_cxx::__normal_iteratorchar const*,
std::__cxx11::basic_stringchar, std::char_traitschar,
Am Mittwoch, den 08.07.2015, 13:47 +0200 schrieb Andreas Tille:
On Wed, Jul 01, 2015 at 01:04:06PM +0200, Jakub Wilk wrote:
* Andreas Tille andr...@an3as.eu, 2015-07-01, 09:32:
../mira/libmira.a(assembly_io.o): In function
`boost::re_detail::perl_matcher__gnu_cxx::__normal_iteratorchar
On Wed, Jul 08, 2015 at 08:26:52PM +0200, Tobias Frost wrote:
My guess it that the only fix needed here is to rebuild Boost
against the
new C++ ABI (i.e. with GCC 5). :/
Is this a reason to re-assign this bug to Boost?
It's already reported as #790351 ;-)
So I'm tempted to close
Am Donnerstag, den 09.07.2015, 06:28 +0200 schrieb Andreas Tille:
On Wed, Jul 08, 2015 at 08:26:52PM +0200, Tobias Frost wrote:
My guess it that the only fix needed here is to rebuild Boost
against the
new C++ ABI (i.e. with GCC 5). :/
Is this a reason to re-assign this bug to
* Andreas Tille andr...@an3as.eu, 2015-07-01, 09:32:
../mira/libmira.a(assembly_io.o): In function `boost::re_detail::perl_matcher__gnu_cxx::__normal_iteratorchar const*,
std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar ,
Hi,
I tried to track down this problem but picked the latest upstream
version to see whether something regarding gcc-5 was done. In fact the
reported problem vanished and was replaced by a new one which I also
can't solve. Any help to track down the problem (see attachment) for
the packaging in
7 matches
Mail list logo
