Your message dated Sun, 6 Aug 2017 11:53:33 +0200
with message-id <>
and subject line Re: flightgear: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
has caused the Debian Bug report #868909,
regarding flightgear: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Source: flightgear
Version: 1:2017.2.1+dfsg-1
Severity: serious
Tags: buster sid
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64


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

Relevant part (hopefully):
> /usr/bin/cc  -g -O2 
> -fdebug-prefix-map=/<<BUILDDIR>>/flightgear-2017.2.1+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now  
> CMakeFiles/cmTC_b6134.dir/CheckSymbolExists.c.o  -o cmTC_b6134 -rdynamic 
> CMakeFiles/cmTC_b6134.dir/CheckSymbolExists.c.o: In function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
> reference to `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:

A list of current common problems and possible solutions is available at . 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 ---
Control: fixed -1 1:2017.2.1+dfsg-3


there were other build issues in -1 and -2 that got fixed in -3, which
now builds on all release architectures on buildd as well as on 3
different architectures I manually tried on porter boxes (including
amd64). So I'm assuming this has been fixed and I'm therefore closing
this issue.

Note that I couldn't ever reproduce this exact error, though.

Kind Regards

Markus Wanner

Attachment: signature.asc
Description: OpenPGP digital signature

--- End Message ---

Reply via email to