Bug#458669: gauche: FTBFS: gosh: "error": unbound variable: require:require

2 views

Skip to first unread message

Lucas Nussbaum

unread,

Jan 2, 2008, 6:00:18 AM1/2/08

Package: gauche
version: 0.8.12-2
Severity: serious
User: debi...@lists.debian.org
Usertags: qa-ftbfs-20080101 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:

> make[3]: Entering directory `/build/user/gauche-0.8.12/build-tree/lib'
> if test -f /usr/share/slib/require.scm; then \
> /bin/sh ./mklibcat ../src/gosh ; \
> fi
> gosh: "error": unbound variable: require:require
> make[3]: *** [slibcat-in-place] Error 1
> make[3]: Leaving directory `/build/user/gauche-0.8.12/build-tree/lib'
> make[2]: *** [slibcat-in-place] Error 2
> make[2]: Leaving directory `/build/user/gauche-0.8.12/build-tree'
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/build/user/gauche-0.8.12'
> make: *** [binary] Error 2
> dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error exit status 2

The full build log is available from:
http://people.debian.org/~lucas/logs/2008/01/01

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.

--
To UNSUBSCRIBE, email to debian-bugs...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Debian Bug Tracking System

unread,

Jan 15, 2008, 11:50:08 PM1/15/08

Your message dated Wed, 16 Jan 2008 04:17:03 +0000
with message-id <E1JEzi3-...@ries.debian.org>
and subject line Bug#458669: fixed in gauche 0.8.12-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)