Your message dated Thu, 2 Aug 2018 23:50:51 +0300
with message-id <20180802205051.GA30379@localhost>
and subject line Re: Bug#897868: spark: ftbfs with GCC-8
has caused the Debian Bug report #897868,
regarding spark: ftbfs with GCC-8
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 ow...@bugs.debian.org
immediately.)


-- 
897868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:spark
Version: 2012.0.deb-11
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/spark_2012.0.deb-11_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html

[...]
gnatprep -c -r -DSPARK=False indexmanager-cache.SHADOW.adb 
indexmanager-cache.adb
gnatprep -c -DSPARK=True indexmanager-cache.SHADOW.adb indexmanager-cache.shb
gnatprep -c -r -DSPARK=False sli-xref.SHADOW.adb sli-xref.adb
gnatprep -c -DSPARK=True sli-xref.SHADOW.adb sli-xref.shb
# -p = Operate as parser
# -s = Perform self-pack
# -m = Accept multi comp
# -v = Verbose
# -du = Activate debug feature: dump memory
../sparklalr/sparklalr SPARK -p -s -m -v -du
STATE 309: * REDUCE/REDUCE CONFLICT


     0 SHIFT/REDUCE CONFLICTS
     1 REDUCE/REDUCE CONFLICTS

   145 TERMINALS (255 MAX)
   380 NONTERMINALS (511 MAX)
   837 PRODUCTIONS (1023 MAX)
  1682 STATES (2047 MAX)
 13660 PARSING ACTIONS GENERATED
  4944 GOTO ENTRIES GENERATED
   355 PARSING ACTIONS OPTIMISED BY CASE LABEL MERGE
 19238 MEMORY RECORDS USED.
  3726 MEMORY RECORDS USED FOR PRODUCTION STORAGE.
 15512 MEMORY RECORDS USED FOR OTHER INFORMATION.
DUMPMEM Set...

Determing Shift States, Reduce States, and Unique Reduce States...
Generating relation Left Corner...
Generating Essential Expected Symbols...
Calculating Table Sizes...
Generating SPARK Parser Tables...
gnatchop -w SPARK.PAR
gcc: error trying to exec 'gnat1': execvp: No such file or directory
SPARK.PAR: parse errors detected
SPARK.PAR: chop may not be successful
no compilation units found
no source files written
make[4]: *** [Makefile:124: sp_symbols.ads] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/examiner'
make[3]: *** [Makefile:89: makeall] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
make[2]: *** [Makefile:79: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:32: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:22: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

--- End Message ---
--- Begin Message ---
On Fri, May 04, 2018 at 12:23:46PM +0000, Matthias Klose wrote:
>...
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
>...

This is the old problem of gnat changing the default not in sync with 
gcc, there isn't much to be done other than waiting for gnat 8 to reach 
unstable.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--- End Message ---

Reply via email to