fusebirth is only used to generate fused_loop.c, which is then used to
build the final freebirth. so shipping a generated fused_loop.c instead
of trying to generate it every time would be a solution.
IMO if this is still an issue building the generator with -O0 would be a
more appropriate solouti
Processing commands for [EMAIL PROTECTED]:
> tags 367831 +pending
Bug#367831: FTBFS with GCC 4.2: fusebirth segfaults
Tags were: sid lenny
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, De
tags 367831 +pending
thanks
--
hi,
well, i got to reproduce this bug on my 'new' powerpc machine.
but, mmh, i still haven't found a way around it though.
the problem seems to lie somewhere in topo_sort, a recursive function,
when it reaches the end of graph branches, hitting NULL pointer there.
* Paul Brossier <[EMAIL PROTECTED]> [2007-09-28 14:51]:
> unfortunately, i don't have access to powerpc at the moment, so Martin,
> any help would be greatly appreciated.
I just tried to compile the current version of freebirth with the
current gcc (4.2) version in unstable, and it still segfaults
hi,
unfortunately, i don't have access to powerpc at the moment, so Martin,
any help would be greatly appreciated.
cheers, Paul
On Mon, May 07, 2007 at 05:18:50PM +, brian m. carlson wrote:
> Just as a data point, freebirth builds fine on amd64 as well. I might
> eventually get around to bo
5 matches
Mail list logo
