Dear Martin Michlmayr, you wrote: > > Package: bisonc++ > Version: 5.00.00-1 > Severity: serious > > This package fails to build in unstable: > > > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux > ... > > Yodl: including file algorithm/ruleprec.yo > > Yodl: including file algorithm/condep.yo > > Yodl: including file algorithm/reduce.yo > > usage: [-a] [-N] [-n] [-s<nr>] [-t<nr>] [-S<nr>] [-T<nr>] marker file > > See also: `man yodlverbinsert' > > Yodl: including file algorithm/mysterious.yo ... > > Fatal: system - failure of system call (status 256) > > debian/rules:41: recipe for target 'build-indep' failed > > make: *** [build-indep] Error 1 > > -- > Martin Michlmayr > Linux for HPE Helion, Hewlett Packard Enterprise
Hi Martin,
Thanks for the bug report. Ususally a bug report provides me with clear hints
about its causes, but this time I'm at a loss. Building the manual on amd64
archs works OK, and I have no access to a HPE Helion machine, so it's hard to
reproduce the bug.
I'm also wondering why the bug appears when yodl processes
algorithm/reduce.yo, and not earlier. E.g., the macro 'verbinsert' is called
in documentation/manual/algorithm/reduce.yo, but before that in
examples/rpndecl.yo: verbinsert(//DECL)(rpn/parser/grammar)
examples/rpngram.yo: verbinsert(//RULES)(rpn/parser/grammar)
examples/errors.yo: verbinsert(//LINE)(errorcalc/parser/grammar)
and only then:
algorithm/reduce.yo: verbinsert(-as4)(examples/rr1)
But when used in reduce.yo another type of argument (-as4) is passed to
yodlverbinsert than in the other three cases, where a //XXX marker is used
(the short usage info displayed by yodlverbinsert suggests that a marker is
required, but that's not actually true, cf. yodlverbinsert's man-page).
There is of course a poor-man's solution: I build the documents and provide
the pre-built documents with the debian package. But it would be nice to know
why we get the FTBFS problem on the Helions. Maybe I could ask you to replace
line 7 ofdocumentation/manual/algorithm/reduce.yo
verbinsert(-as4)(examples/rr1)
by
VERBOSITY()(0x4)
verbinsert(-as4)(examples/rr1)
VERBOSITY()(NONE)
and then run ./build manual in bisonc++'s base directory (where you also find
a file named CLASSES) and send me the output? That might provide a little
more info about what went wrong.
For now, lacking access to a Helion machine, I'm afraid I have to ask you for
some help....
Cheers,
[Cc: Tony/George]
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
signature.asc
Description: PGP signature
