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

Bug#925567: marked as done (gcc-8-cross: FTBFS: conftest.c:72: undefined reference to `getexecname')



Your message dated Thu, 28 Mar 2019 10:47:00 +0100
with message-id <[🔎] 3a639c42-1540-356e-0f09-35bd28f41605@debian.org>
and subject line Re: Bug#925567: gcc-8-cross: FTBFS: conftest.c:72: undefined reference to `getexecname'
has caused the Debian Bug report #925567,
regarding gcc-8-cross: FTBFS: conftest.c:72: undefined reference to `getexecname'
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.)


-- 
925567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925567
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8-cross
Version: 26
Severity: serious
Tags: buster sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20190325 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> /usr/bin/ld: /tmp/cc7hDO1R.o: in function `main':
> /<<PKGBUILDDIR>>/gcc/build/libbacktrace/conftest.c:72: undefined reference to `getexecname'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2019/03/25/gcc-8-cross_26_testing.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Version: 26

I think this is a false positive. The gcc-8-cross-ports package sucessfully
built, and gcc-8-cross 27 built as well.

On 26.03.19 21:48, Lucas Nussbaum wrote:
> Source: gcc-8-cross
> Version: 26
> Severity: serious
> Tags: buster sid
> User: debian-qa@lists.debian.org
> Usertags: qa-ftbfs-20190325 qa-ftbfs
> Justification: FTBFS in buster on amd64
> 
> Hi,
> 
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.
> 
> Relevant part (hopefully):
>> /usr/bin/ld: /tmp/cc7hDO1R.o: in function `main':
>> /<<PKGBUILDDIR>>/gcc/build/libbacktrace/conftest.c:72: undefined reference to `getexecname'
>> collect2: error: ld returned 1 exit status
> 
> The full build log is available from:
>    http://qa-logs.debian.net/2019/03/25/gcc-8-cross_26_testing.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 

--- End Message ---

Reply to: