Bug#676884: libffi: New upstream version available

[Daniel Schepler]

Source: libffi
Version: 3.0.10-3
Severity: wishlist

Hi, the current 3.0.10 Debian package builds a broken libffi library on x32, 
whereas on 3.0.11 it passes the testsuite with no problems.  (Although it 
would require an soname bump to libffi6.)
-- 
Daniel Schepler



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201206100253.22022.dschep...@gmail.com

Bug#676884: marked as done (libffi: New upstream version available)

[Debian Bug Tracking System]

Your message dated Sun, 10 Jun 2012 03:26:35 -0700
with message-id <201206100326.35851.dschep...@gmail.com>
and subject line libffi 3.0.11 is in experimental
has caused the Debian Bug report #676884,
regarding libffi: New upstream version available
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 ow...@bugs.debian.org
immediately.)


-- 
676884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libffi
Version: 3.0.10-3
Severity: wishlist

Hi, the current 3.0.10 Debian package builds a broken libffi library on x32, 
whereas on 3.0.11 it passes the testsuite with no problems.  (Although it 
would require an soname bump to libffi6.)
-- 
Daniel Schepler


--- End Message ---
--- Begin Message ---
Version: 3.0.11-1

Sorry for the noise, I somehow missed that there was already a 3.0.11 libffi 
package in experimental.
-- 
Daniel Schepler

--- End Message ---

Bug#618351: gcc-doc: Still depends on gcc-4.4-doc after the move to 4.5.

[Axel Beckert]

Hi,

Christian Ohm wrote on 14-Mar-2011:
> As the subject says, gcc-doc is still depending on the old docs.

Any news here?

We're now at gcc 4.7 for most architectures, the freeze is close and
gcc-doc still depends on gcc-4.4-doc.

IMHO this should be fixed for Wheezy.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120610115026.ga18...@sym.noone.org

Bug#618351: gcc-doc: Still depends on gcc-4.4-doc after the move to 4.5.

[Axel Beckert]

Hi,

I was too quick with replying:

Axel Beckert wrote:
> Christian Ohm wrote on 14-Mar-2011:
> > As the subject says, gcc-doc is still depending on the old docs.
> 
> Any news here?
> 
> We're now at gcc 4.7 for most architectures, the freeze is close and
> gcc-doc still depends on gcc-4.4-doc.

... because there doesn't seem to exist any gcc-4.x-doc package with
x >= 5. *puzzled*

> IMHO this should be fixed for Wheezy.

... maybe by removing the package from testing and not including it in
wheezy?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120610115558.gp3...@sym.noone.org

Fwd: Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

[Christophe Prud'homme]

Hello

I get an ice with gcc47 (see email below)

I am trying to reproduce it.
Shouldn't it be considered a gcc47 bug rather than a feel++ bug ?
Feel++ compiles and runs fine with gcc45, gcc46 and clang31.

Best regards
C.

-- Forwarded message --
From: Lucas Nussbaum 
Date: Sat, Jun 9, 2012 at 10:10 AM
Subject: Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal
compiler error: Segmentation fault
To: sub...@bugs.debian.org


Source: feel++
Version: 0.91.4-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory 
> `/build/feel++-TyecKE/feel++-0.91.4/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report 
> /build/feel++-TyecKE/feel++-0.91.4/obj-x86_64-linux-gnu/CMakeFiles
> [ 91%] Building CXX object 
> doc/manual/tutorial/CMakeFiles/feel_doc_mymesh.dir/mymesh.cpp.o
> cd 
> /build/feel++-TyecKE/feel++-0.91.4/obj-x86_64-linux-gnu/doc/manual/tutorial 
> && /usr/bin/g++   -DBOOST_UBLAS_MOVE_SEMANTICS -DFEELPP_HAS_MPI=1 
> -DFEELPP_HAS_MPI_H=1 -DFEELPP_HAS_DLFCN_H -DFEELPP_HAS_DLOPEN 
> -DBOOST_PARAMETER_MAX_ARITY=20 -DBOOST_TEST_DYN_LINK 
> -DBOOST_FILESYSTEM_VERSION=3 -DBOOST_NO_SCOPED_ENUMS -DFEELPP_HAS_PETSC 
> -DFEELPP_HAS_PETSC_H -DFEELPP_HAS_GMSH=1 -D_FEELPP_HAS_GMSH_ 
> -DGMSH_EXECUTABLE=/usr/bin/gmsh -std=c++0x -pedantic  -ftemplate-depth-256 
> -Wno-inline -std=c++0x  -std=c++0x  -pedantic -g0 -O2 -DNDEBUG  
> -ftemplate-depth-256 -finline-functions -Wno-inline -std=c++0x  
> -I/build/feel++-TyecKE/feel++-0.91.4/contrib -I/usr/lib/openmpi/include 
> -I/usr/lib/openmpi/include/openmpi -I/usr/include/libxml2 
> -I/build/feel++-TyecKE/feel++-0.91.4/contrib/eigen -I/usr/include/ANN 
> -I/usr/include/python2.7 -I/usr/lib/petscdir/3.2/include 
> -I/usr/lib/petscdir/3.2/linux-gnu-c-opt/include 
> -I/usr/lib/slepcdir/3.2/linux-gnu-c-opt/include 
> -I/usr/lib/slepcdir/3.2/include -I/usr/include/gmsh 
> -I/build/feel++-TyecKE/feel++-0.91.4/obj-x86_64-linux-gnu 
> -I/build/feel++-TyecKE/feel++-0.91.4 
> -I/build/feel++-TyecKE/feel++-0.91.4/contrib/gmm/include 
> -I/build/feel++-TyecKE/feel++-0.91.4/doc/manual     -Wall -Wno-unused 
> -Wno-sign-compare -o CMakeFiles/feel_doc_mymesh.dir/mymesh.cpp.o -c 
> /build/feel++-TyecKE/feel++-0.91.4/doc/manual/tutorial/mymesh.cpp
> In file included from 
> /build/feel++-TyecKE/feel++-0.91.4/feel/feelvf/vf.hpp:93:0,
>                  from 
> /build/feel++-TyecKE/feel++-0.91.4/feel/feelfilters/gmsh.hpp:47,
>                  from 
> /build/feel++-TyecKE/feel++-0.91.4/doc/manual/tutorial/mymesh.cpp:34:
> /build/feel++-TyecKE/feel++-0.91.4/feel/feelvf/operators.hpp: In 
> instantiation of 'struct Feel::vf::OpId (Feel::vf::OperatorType)2u>::tensor Basis_j_t>::tensor(const this_type&, const Geo_t&) [with Geo_t = 
> boost::fusion::map, 
> boost::shared_ptr Feel::Lagrange>::Context<2307ul, Feel::GeoElement2D<2u, Feel::Simplex<2u, 1u, 
> 2u>, Feel::SubFaceOfNone, double> > > >, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_>; Basis_i_t = 
> boost::fusion::map, 
> boost::shared_ptr > >, 
> boost::fusion::pair, 
> boost::shared_ptr > > >; Basis_j_t = 
> boost::fusion::map, 
> boost::shared_ptr > >, 
> boost::fusion::pair, 
> boost::shared_ptr > > >; Element = 
> Feel::FunctionSpace >, 
> Feel::bases Feel::PointSetEquiSpaced, 0u>, Feel::void_basis, Feel::void_basis, 
> Feel::void_basis>, boost::parameter::void_, boost::parameter::void_, 
> boost::parameter::void_>::Element boost::numeric::ublas::vector boost::numeric::ublas::unbounded_array > > > 
> >; Feel::vf::OpId::this_type = 
> Feel::vf::OpId >, 
> Feel::bases Feel::PointSetEquiSpaced, 0u>, Feel::void_basis, Feel::void_basis, 
> Feel::void_basis>, boost::parameter::void_, boost::parameter::void_, 
> boost::parameter::void_>::Element boost::numeric::ublas::vector boost::numeric::ublas::unbounded_array > > > 
> >, (Feel::vf::OperatorType)2u>]::INVALID_CALL_TO_CONSTRUCTOR722':
> /build/feel++-TyecKE/feel++-0.91.4/feel/feelvf/operators.hpp:722:1:   
> required from 'Feel::vf::OpId (Feel::vf::OperatorType)2u>::tensor Basis_j_t>::tensor(const this_type&, const Geo_t&) [with Geo_t = 
> boost::fusion::map, 
> boost::shared_ptr Feel::Lagrange>::Context<2307ul, Feel::GeoElement2D<2u, Feel::Simplex<2u, 1u, 
> 2u>, Feel::SubFaceOfNone, double> > > >, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, 
> boost::fusion::void_, boost::fusion::void_>; Basis_i_t = 
> boost::fusion::map, 
> boost::shared_ptr > >, 
> boost::fusion::pair, 
> boost::shared_ptr > > >; Basis_j_t = 
> boost::fusion::map, 
> boost::shared_ptr > >, 
> boost::fusion::pai

Re: Processed: severity of 673749 is important

[Christophe Prud'homme]

reopen 673749
thanks



On Sat, Jun 9, 2012 at 1:13 PM, Debian Bug Tracking System
 wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> severity 673749 important
> Bug #673749 {Done: Matthias Klose } [g++-4.7] g++-4.7: gcc47 
> generates buggy code  with optimisation flags
> Severity set to 'important' from 'normal'
>> thanks
> Stopping processing here.
>
> Please contact me if you need assistance.
> --
> 673749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673749
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> --
> To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/handler.s.c.13392403212563.transcr...@bugs.debian.org
>


--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAL5hWmTGzjUUcQT-4yKVkwPn5ubB=qsdtd+rnbum1qh_9m+...@mail.gmail.com

Bug#618351: gcc-doc: Still depends on gcc-4.4-doc after the move to 4.5.

[Russ Allbery]

Axel Beckert  writes:
> Axel Beckert wrote:

>> We're now at gcc 4.7 for most architectures, the freeze is close and
>> gcc-doc still depends on gcc-4.4-doc.

> ... because there doesn't seem to exist any gcc-4.x-doc package with
> x >= 5. *puzzled*

Isn't the GCC documentation now non-free?

-- 
Russ Allbery (r...@debian.org)   



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877gveaoz9@windlord.stanford.edu

Gcc47 -12 breaks Feel++

[Christophe Prud'homme]

Dear Gcc maintainers,

gcc47 -12 breaks feel++ compilation.
it generates ices and sometimes generates new compiling errors that
-11 didn't have.

I am very distressed to have this kind of unstable  compiler behavior
and especially at a time where I don't have much time to
work on my packages.

Best regards
C.


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAL5hWmS2e02jSv3H2QYQkpB+=lrv6esqkc2y7yxbox6v9lt...@mail.gmail.com

Processed: Re: Bug#676729: Fwd: Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 676729 gcc-4.7 4.7.0-12
Bug #676729 [src:feel++] feel++: FTBFS: operators.hpp:722:1: internal compiler 
error: Segmentation fault
Bug reassigned from package 'src:feel++' to 'gcc-4.7'.
No longer marked as found in versions feel++/0.91.4-2.
Ignoring request to alter fixed versions of bug #676729 to the same values 
previously set
Bug #676729 [gcc-4.7] feel++: FTBFS: operators.hpp:722:1: internal compiler 
error: Segmentation fault
Marked as found in versions gcc-4.7/4.7.0-12.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.133936090819821.transcr...@bugs.debian.org

Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

[Touko Korpela]

On Sun, Jun 10, 2012 at 10:41:41PM +0200, Christophe Prud'homme wrote:
> reassign 676729 gcc-4.7 4.7.0-12
> thanks
> 
> On Sun, Jun 10, 2012 at 10:04 PM, Christophe Prud'homme
>  wrote:
> > Hello
> >
> > I get an ice with gcc47 (see email below)
> >
> > I am trying to reproduce it.
> > Shouldn't it be considered a gcc47 bug rather than a feel++ bug ?
> > Feel++ compiles and runs fine with gcc45, gcc46 and clang31.

I recommend that you change feel++ to build-depend on gcc-4.6 for now.



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120610210705.GA5089@lisko

Bug#676729: feel++: FTBFS: operators.hpp:722:1: internal compiler error: Segmentation fault

[Christophe Prud'homme]

Hello

I will certainly build-depend on gcc-4.6 for now. However I am very
dubious as to gcc47 quality:
from one debian version to another it breaks packages, it generates
buggy codes. It just doesn't seem
very reliable and production ready.

Best regards
C.

On Sun, Jun 10, 2012 at 11:07 PM, Touko Korpela  wrote:
> I recommend that you change feel++ to build-depend on gcc-4.6 for now.



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAL5hWmRdk4dt10dNQQdONohQ172A1ZQ89sqWG-RQYMu=kfi...@mail.gmail.com

Bug#618351: gcc-doc: Still depends on gcc-4.4-doc after the move to 4.5.

[Axel Beckert]

Hi Russ,

Russ Allbery wrote:
> >> We're now at gcc 4.7 for most architectures, the freeze is close and
> >> gcc-doc still depends on gcc-4.4-doc.
> 
> > ... because there doesn't seem to exist any gcc-4.x-doc package with
> > x >= 5. *puzzled*
> 
> Isn't the GCC documentation now non-free?

It was already (in) non-free back in the GCC 4.4 days and gcc-doc is a
package in contrib.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5



-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120610225705.ga25...@sym.noone.org