Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #283700 > unrolled thread

Bug#966903: gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#966903: gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory Lucas Nussbaum <lucas@debian.org> - 2020-08-03 10:30 +0200
    Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10:  fatal error: parser.tab.hpp: No such file or directory) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-08-08 23:00 +0200
    Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10:  fatal error: parser.tab.hpp: No such file or directory) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-08-09 08:30 +0200

#283700 — Bug#966903: gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory

Source: gecode
Version: 6.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -I. -fcx-limited-range -fno-signaling-nans -fno-rounding-math -ffinite-math-only -fno-math-errno -fno-strict-aliasing  -fvisibility=hidden -ggdb -std=c++11 -pipe -Wall -Wextra -fPIC -pthread -DNDEBUG -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2  -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB  -I. -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ \
>  \
> -c -o gecode/flatzinc/parser.tab.o  gecode/flatzinc/parser.tab.cpp
> gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory
>   526 | #include "parser.tab.hpp"
>       |          ^~~~~~~~~~~~~~~~
> compilation terminated.
> make[2]: *** [Makefile:1492: gecode/flatzinc/parser.tab.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/gecode_6.2.0-3_unstable.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.

[toc] | [next] | [standalone]

#284368 — Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 08 Aug 2020 20:52:12 +0000
with message-id <E1k4Vp6-0009AC-BE@fasolo.debian.org>
and subject line Bug#966903: fixed in gecode 6.2.0-4
has caused the Debian Bug report #966903,
regarding gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory
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.)


-- 
966903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966903
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#284390 — Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 09 Aug 2020 06:18:40 +0000
with message-id <E1k4efI-00057w-9q@fasolo.debian.org>
and subject line Bug#966903: fixed in gecode 6.2.0-5
has caused the Debian Bug report #966903,
regarding gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory
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.)


-- 
966903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966903
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web