bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

texi2dvi is a bash script, not a Bourne shell script


From: Prof Brian Ripley
Subject: texi2dvi is a bash script, not a Bourne shell script
Date: Wed, 1 Jul 2015 08:49:53 +0100
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1

On Solaris 10, installed from the sources:

swift-9% texi2dvi --version
texi2dvi (GNU Texinfo 6.0) 6363

and any invocation gives

/usr/local/bin/texi2dvi: BSTINPUTS: not found

The head of the script is

#! /bin/sh
# texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
# $Id: texi2dvi 6363 2015-06-26 12:36:32Z gavin $

and /bin/sh is a Bourne shell derived from AT&T Unix.

Using --debug does not help me:

Error: compiling TeX file 'displaylist.tex' failed with message:
Running 'texi2dvi' on 'displaylist.tex' failed.
Messages:


#
   Main program main loop - TeXify each file in turn.
for command_line_filename
do
  verbose "Processing $command_line_filename ..."

  input_file_name_decode

  # `texinfo' or `latex'?
  in_lang=`compute_language "$command_line_filename"`

  # An auxiliary directory used for all the auxiliary tasks involved
  # in compiling this document.
  case $build_dir in
      '' | . ) t2ddir=$out_noext.t2d ;;
      *) # Avoid collisions between multiple occurrences of the same
         # file, so depend on the output path.  Remove leading `./',
         # at least to avoid creating a file starting with `.!', i.e.,
         # an invisible file. The sed expression is fragile if the cwd
         # has active characters.  Transform / into ! so that we don't
         # need `mkdir -p'.  It might be something to reconsider.
         t2ddir=$build_dir/`echo "$out_dir_abs/$out_n
Execution halted

Changing to

#! /bin/bash

makes this work.

--
Brian D. Ripley,                  address@hidden
Emeritus Professor of Applied Statistics, University of Oxford
1 South Parks Road, Oxford OX1 3TG, UK



reply via email to

[Prev in Thread] Current Thread [Next in Thread]