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

Bug#957757: marked as done (renderdoc: ftbfs with GCC-10)

Your message dated Wed, 22 Jul 2020 12:30:04 -0700
with message-id <159544620441.921990.4427329428416909136@kelvin>
and subject line renderdoc 1.8 doesn't FTBFS with gcc-10
has caused the Debian Bug report #957757,
regarding renderdoc: ftbfs with GCC-10
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.)


-- 
957757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957757
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:renderdoc
Version: 1.6+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/renderdoc_1.6+dfsg-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:371:19: error: ‘FileIO::fclose’ cannot be used as a function
  371 |   FileIO::fclose(f);
      |                   ^
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h: In function ‘bool FileIO::ReadAll(const char*, rdcstr&)’:
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:378:3: error: ‘FILE’ was not declared in this scope
  378 |   FILE *f = FileIO::fopen(filename, "rb");
      |   ^~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:378:3: note: ‘FILE’ is defined in header ‘<cstdio>’; did you forget to ‘#include <cstdio>’?
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:378:9: error: ‘f’ was not declared in this scope
  378 |   FILE *f = FileIO::fopen(filename, "rb");
      |         ^
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:378:21: error: ‘fopen’ is not a member of ‘FileIO’
  378 |   FILE *f = FileIO::fopen(filename, "rb");
      |                     ^~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:382:11: error: ‘fseek64’ is not a member of ‘FileIO’
  382 |   FileIO::fseek64(f, 0, SEEK_END);
      |           ^~~~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:384:25: error: ‘SEEK_SET’ was not declared in this scope
  384 |   FileIO::fseek64(f, 0, SEEK_SET);
      |                         ^~~~~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:390:19: error: ‘FileIO::fclose’ cannot be used as a function
  390 |   FileIO::fclose(f);
      |                   ^
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:382:25: error: ‘SEEK_END’ was not declared in this scope
  382 |   FileIO::fseek64(f, 0, SEEK_END);
      |                         ^~~~~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:383:28: error: ‘FileIO::ftell64’ cannot be used as a function
  383 |   uint64_t size = ftell64(f);
      |                            ^
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:384:11: error: ‘fseek64’ is not a member of ‘FileIO’
  384 |   FileIO::fseek64(f, 0, SEEK_SET);
      |           ^~~~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:384:25: error: ‘SEEK_SET’ was not declared in this scope
  384 |   FileIO::fseek64(f, 0, SEEK_SET);
      |                         ^~~~~~~~
/<<PKGBUILDDIR>>/renderdoc/os/os_specific.h:390:19: error: ‘FileIO::fclose’ cannot be used as a function
  390 |   FileIO::fclose(f);
      |                   ^
In file included from /<<PKGBUILDDIR>>/renderdoc/os/posix/posix_libentry.cpp:25:
/<<PKGBUILDDIR>>/renderdoc/core/core.h: At global scope:
/<<PKGBUILDDIR>>/renderdoc/core/core.h:43:18: error: ‘FILE’ was not declared in this scope
   43 | bool is_exr_file(FILE *f);
      |                  ^~~~
/<<PKGBUILDDIR>>/renderdoc/core/core.h:36:1: note: ‘FILE’ is defined in header ‘<cstdio>’; did you forget to ‘#include <cstdio>’?
   35 | #include "common/timing.h"
  +++ |+#include <cstdio>
   36 | #include "os/os_specific.h"
/<<PKGBUILDDIR>>/renderdoc/core/core.h:43:24: error: ‘f’ was not declared in this scope
   43 | bool is_exr_file(FILE *f);
      |                        ^
make[3]: *** [renderdoc/CMakeFiles/rdoc.dir/build.make:66: renderdoc/CMakeFiles/rdoc.dir/common/common.cpp.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:366: renderdoc/CMakeFiles/rdoc.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
make[3]: *** [renderdoc/CMakeFiles/renderdoc_libentry.dir/build.make:66: renderdoc/CMakeFiles/renderdoc_libentry.dir/os/posix/posix_libentry.cpp.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:312: renderdoc/CMakeFiles/renderdoc_libentry.dir/all] Error 2
[  3%] Linking CXX executable ../bin/include-bin
cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/renderdoc && /usr/bin/cmake -E cmake_link_script CMakeFiles/include-bin.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -Wno-unused-variable -Wno-unused-parameter -Wno-unused-result -Wno-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas -Wno-reorder -Wno-unused-but-set-variable -Wno-maybe-uninitialized -Wno-class-memaccess -Wimplicit-fallthrough=2 -O3 -DNDEBUG  -Wl,-z,relro -rdynamic CMakeFiles/include-bin.dir/3rdparty/include-bin/main.cpp.o  -o ../bin/include-bin 
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[  3%] Built target include-bin
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
[  3%] Built target rdoc_intel
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:133: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Control: fixed -1 1.8+dfsg-1
Control: owner -1 !

I did reproduce the FTBFS with 1.6, but the current version, 1.8
builds for me in an up-to-date sbuild environment.

Attachment: signature.asc
Description: signature


--- End Message ---
Reply to: