On Tue, Feb 26, 2002 at 12:24:04AM +0000, James Troup wrote:
> Steve Langasek <vorlon@netexpress.net> writes:
> > Most auto-built packages in Debian are built using chroot'ed build
> > environments.
> It's worth idly noting, btw, that every single active auto-builder
> manager to build the tetex-bin you're bug is about btw ;-) (And many
> of them use fakeroot...)
With much squinting in the direction of the autobuilders, I've gone back
and re-tested trying to build tetex-bin 1.0.7+20011202-3.1 on my
machine. I still see the same error. It looks like the reason it
doesn't manifest on the autobuilders is because none of the autobuilders
have /bin/sh -> ash, like I do. I would have hoped that autoconf wasn't
producing bash-specific scripts, but it seems I'm wrong.
I definitely end up with some Makefile's in subdirectories where the
value of mandir is hard-coded:
$ grep mandir ./texk/makeindexk/Makefile
mandir = /usr/share/man/man$(manext)
$(SHELL) $(top_srcdir)/../mkinstalldirs $(mandir)
$(INSTALL_DATA) $(srcdir)/makeindex.1 $(mandir)/makeindex.$(manext)
$(INSTALL_DATA) $(srcdir)/mkindex.1 $(mandir)/makeindex.$(manext)
This is the case even though the top-level makefile still shows
'${prefix}/share/man/man$(manext)' instead. My best guess is some kind
of screwy interaction between ash, and the multi-level configure scripts
that tetex-bin uses.
So, I don't know that an ash-specific build problem still qualifies as
RC. The patch is still there if you're interested. :)
Steve Langasek
postmodern programmer
Attachment:
pgpNCzqZW10qb.pgp
Description: PGP signature