Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Frank B. Brokken]

Dear Martin Michlmayr, you wrote:

> Yeah, that's the whole point of these archive rebuilds of unstable
> that various people in Debian do -- to rebuild everything in unstable
> and to catch build failures because of something changed in unstable
> (e.g. toolchain, libraries, other tools).

Agree 100%. And the fix is on its way :-)

Thanks again!

-- 
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

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Martin Michlmayr]

* Frank B. Brokken  [2016-04-25 04:28]:
> Oops, guys: OK, hold your fire: the flaw is at my side: I missed
> that Martin already used yodl 3.07.01

Yeah, that's the whole point of these archive rebuilds of unstable
that various people in Debian do -- to rebuild everything in unstable
and to catch build failures because of something changed in unstable
(e.g. toolchain, libraries, other tools).

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Frank B. Brokken]

Dear Martin Michlmayr, you wrote:

> Looks like Tony can reproduce it.  I just wanted to add briefly that
> this has nothing to do with HPE Helion.  It's a normal Debian
> installation and a normal Debian sid chroot using sbuild.

Oops, guys: OK, hold your fire: the flaw is at my side: I missed that Martin
already used yodl 3.07.01, and while reading Tony's mail I noticed that Tony
*did* use the latest Yodl version. When I do that too, I also reproduced the
error. So I think the bug can safely be reassigned to yodl, and I also think
it can quickly be fixed. 

Thanks for the quick reply, guys: I'll do my best to come up with the fix
equallly quick :-)

Cheers,

-- 
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

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Martin Michlmayr]

* Frank B. Brokken  [2016-04-24 19:11]:
> 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.

Looks like Tony can reproduce it.  I just wanted to add briefly that
this has nothing to do with HPE Helion.  It's a normal Debian
installation and a normal Debian sid chroot using sbuild.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[tony mancill]

On 04/24/2016 10:11 AM, Frank B. Brokken wrote:
> 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] [-t] [-S] [-T] 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.

Hi Frank,

I'm able to reproduce the bug building bisonc++ on amd64 in a clean
chroot with yodl-3.07.01-1.  The same bisonc++ source package builds
successfully against yodl-3.06.00-1.  I haven't reassigned the bug to
yodl (yet) because I haven't yet determined where the issue lies.  Other
packages that build-dep upon yodl - e.g., oxref - build correctly
against with the updated yodl version.

Cheers,
tony



signature.asc
Description: OpenPGP digital signature

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Frank B. Brokken]

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] [-t] [-S] [-T] 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

Bug#822410: bisonc++: FTBFS: failure of system call / usage: ...

[Martin Michlmayr]

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] [-t] [-S] [-T] marker file
> See also: `man yodlverbinsert'
> Yodl: including file algorithm/mysterious.yo
> Yodl: including file error.yo
> Yodl: including file error/intro.yo
> Yodl: including file error/syntactical.yo
> Yodl: including file error/recovery.yo
> Yodl: including file error/semantical.yo
> Yodl: including file invoking.yo
> Yodl: including file invoking/options.yo
> Yodl: including file invoking/usage.yo
> 
> If a message about a failing NOEXPANDINCLUDE is shown, create the file 
> `usage' in documentation/manual/invoking containing the latest usage info
> 
> Error(s) detected
> /usr/bin/yodl indicates failure!
> 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