Your message dated Mon, 05 Nov 2012 12:32:43 +
with message-id
and subject line Bug#672030: fixed in beast 0.7.4-5
has caused the Debian Bug report #672030,
regarding FTBFS with gcc-4.7: segfaults in lt-bseprocidl
to be marked as done.
This means that you claim that the problem has been
tags 672030 - help + pending
thanks
Hi everybody,
this is just to inform you that a patch is ready, I'm going to upload
the fixed version within few hours.
Cheers,
--
Alessio Treglia | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer| quadr
On 25.10.2012 08:43, Reinhard Tartler wrote:
> On Thu, Oct 25, 2012 at 4:15 AM, Tim Janik wrote:
>> On 20.10.2012 12:42, Reinhard Tartler wrote:
>>> Hi Tim,
>>>
>>> I wonder if there is any news on this bug on your side?
>> Beast 0.7.6 with full support for g++-4.7 has been released now, see our
>
Am 25.10.2012 08:43, schrieb Reinhard Tartler:
Any chance to isolate the g++-4.7 fixes? Is there a public gitweb
available somewhere so that we can apply them as patches to the old
version?
http://git.gnome.org/browse/beast/log/
I guess the first three commits of 2012-10-21 are relevant for g+
On Thu, Oct 25, 2012 at 4:15 AM, Tim Janik wrote:
> On 20.10.2012 12:42, Reinhard Tartler wrote:
>> Hi Tim,
>>
>> I wonder if there is any news on this bug on your side?
>
> Beast 0.7.6 with full support for g++-4.7 has been released now, see our
> website: http://beast.testbit.eu/
>
> The full an
On 20.10.2012 12:42, Reinhard Tartler wrote:
> Hi Tim,
>
> I wonder if there is any news on this bug on your side?
Beast 0.7.6 with full support for g++-4.7 has been released now, see our
website: http://beast.testbit.eu/
The full announcement is here:
https://mail.gnome.org/archives/beast/2012
On 20.10.2012 12:42, Reinhard Tartler wrote:
> Hi Tim,
>
> I wonder if there is any news on this bug on your side?
Hey,
now that I'm back from the libreoffice conference, I managed to install
g++-4.7.2 and reproduce your issue.
I'm investigating it now.
>
> Cheers,
> Reinhard.
--
Yours sin
oblem.
> I don't have a distribution with gcc-4.7 yet, so can only look into this
> later.
>
>>
>> I'm a Debian Developer and I'm triaging a bug reported against the beast
>> package in Debian:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?b
Hey Giovanni, I was wondering if you have heard anything from upstream
on this issue yet? :)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
bug reported against the beast
> package in Debian:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672030
>
> Beast doesn't compile with gcc 4.7, but it does with 4.6. The same
> behavior happens both for the Debian package and the pristine tarball
> distributed on your
Ehy Giovanni!
On Mon, Aug 27, 2012 at 5:37 PM, Giovanni Mascellani wrote:
> I can do this: any objections? Any special care I need to have with
> upstream? (is he Debian friendly?)
I don't have so much time these days, upstream is usually kind and
responsive with me so please go ahead.
Cheers!
retitle 672030 FTBFS with gcc-4.7: segfaults in lt-bseprocidl
thanks
Hi.
(context: I'm writing about the FTBFS in beast)
I can reproduce this bug using gcc-4.7, but the package compiles
correctly with gcc-4.6 (which is bad, because the bug is buried inside
the internals of glib). The same behavi
, the build log contains
70 CRITICAL warnings from GLib, GLib-GObject or BSE.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
Description: Fix #includes to avoid FTBFS with GCC 4.7.
Author: Alessio Treglia
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672030
Forw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Program received signal SIGSEGV, Segmentation fault.
0x7fff0005 in ?? ()
(gdb) bt
#0 0x7fff0005 in ?? ()
#1 0x770d891e in g_type_class_ref () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2 0x004047c2 in printI
Hi
On Thu, Jun 21, 2012 at 09:54:15PM +0100, Steven Chamberlain wrote:
> # the fix for this seems finalised in VCS
> tags 672030 + patch
I tried to build beast in current state of the git repository, it
succeeds at least at the previous part but now the package FTBFS later
on (build segfaults). A
Processing commands for cont...@bugs.debian.org:
> # the fix for this seems finalised in VCS
> tags 672030 + patch
Bug #672030 [src:beast] beast: FTBFS: birnetutils.cc:725:44: error: 'access'
was not declared in this scope
Added tag(s) patch.
> thanks
Stopping processing here.
user debian-...@lists.debian.org
usertags 672030 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To UNSU
Source: beast
Version: 0.7.4-4
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /bin/bash ../libtool --silent
18 matches
Mail list logo
