[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#649307: marked as done (FTBFS on kfreebsd-amd64: gengtype: Internal error: abort in get_output_file_with_visibility, at gengtype.c:1998)

Your message dated Tue, 16 Oct 2012 14:59:43 +0100
with message-id <507D684F.1000007@pyro.eu.org>
and subject line Re: Bug#637236: FTBFS on kfreebsd-amd64: gengtype: Internal error: abort in get_output_file_with_visibility, at gengtype.c:1998
has caused the Debian Bug report #637236,
regarding FTBFS on kfreebsd-amd64: gengtype: Internal error: abort in get_output_file_with_visibility, at gengtype.c:1998
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 owner@bugs.debian.org
immediately.)


-- 
637236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637236
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: gnat-4.6
Version: 4.6.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

See the build log at
https://buildd.debian.org/status/fetch.php?pkg=gnat-4.6&arch=kfreebsd-amd64&ver=4.6.2-2&stamp=1321357341

Cheers,
Julien

--- End Message ---
--- Begin Message --- 
Version: 4.6.3-12

On 08/10/12 00:47, Matthias Klose wrote:
> On 07.10.2012 18:29, Steven Chamberlain wrote:
>> The Internal error: abort in get_output_file_with_visibility, at
>> gengtype.c:1998, seen sometimes on kFreeBSD, seems to be here:
> 
> [...]
> 
> checked in both changes. will wait until -11 migrates, or if not, upload -12 to
> unstable.

Hi Matthias,

Many thanks for including those changes in the -12 upload.  It built on
kfreebsd-amd64 this time on its first attempt, so hopefully it has
worked.  I think we can assume for now the problem is fixed, unless it
is seen to come back again (or if anyone manages to reproduce it
elsewhere than on the buildds).

This build was also notably faster (which figures, if the problem was
due to resources being leaked).  Curiously it built faster on most
arches (in 15-50% less time), compared to each previous build on the
same buildd.

Thanks again,
Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org

--- End Message ---
Reply to: