Bug#299018: antlr: No rule to make target `/skole/tjener/home0/pere/src/debian/java/antlr-2.7.5/scripts/../lib/cpp/Makefile.in'

[Christian T. Steigies]

On Fri, Mar 11, 2005 at 09:58:04AM +0100, Michael Koch wrote:
> On Fri, Mar 11, 2005 at 09:05:37AM +0100, Christian T. Steigies wrote:
> > Package: antlr
> > Version: 2.7.5-2
> > Severity: serious
> > Justification: FTBFS
> > 
> > Automatic build of antlr_2.7.5-2 on aahz by sbuild/m68k 1.170.5
> > [...]
> > ** Using build dependencies supplied by package:
> > Build-Depends: debhelper (>= 4), kaffe, fastjar, classpath, jikes-classpath (>= 1.18), autotools-dev, gcj, libgcj4-dev
> > [...]
> > cd lib/cpp; /usr/bin/make install prefix=`pwd`/../../debian/libantlr-dev/usr
> > make[1]: Entering directory `/build/buildd/antlr-2.7.5/lib/cpp'
> > make[1]: *** No rule to make target `/skole/tjener/home0/pere/src/debian/java/antlr-2.7.5/scripts/../lib/cpp/Makefile.in', needed by `Makefile'.  Stop.
> > make[1]: Leaving directory `/build/buildd/antlr-2.7.5/lib/cpp'
> > make: *** [install] Error 2
> > 
> > There is no /skole directory on my buildd, and it is not immediately obvious
> > from the build-depends that there should be one. This fails to build
> > everywhere.
> 
> That is strange as this package uses always local paths. It should
> replace this with paths on the autobuilder. Can you try to find out why
> it doesn't for you ? It worked for several people before uploading.

According to http://buildd.debian.org/build.php?&pkg=antlr
it hasn't worked for any autobuilder, unlike previous versions.

I've just built it manually on my athlon, and it built fine. Then I built it
in an unstable chroot on the same machine, and it failed with the same
error. Should't all packages be tested by building in a chroot before
upload ;-)

When I build only binary packages however, ie with debuild -B, it also fails
to build outside the chroot. The paths in the Makefile are still all wrong.
When I build with sbuild, inside the chroot, and also have it build
binary-all packages, the build succeeds.

So I guess you are doing something in binary-all, like adapting the paths,
recreating Makefile.in (it is deleted in dh_clean?), that is also needed for
binary-arch.

Christian