texexec & teTeX

texexec & teTeX

[Idris S Hamid]

Dear folks,

I'm in the process of migrating to Linux (Suse 8.0) and I'm having some 
problems getting texexec to behave:-)

Updating to the latest official ConTeXt I place the appropriate perl scripts 
in 
/usr/TeX/bin/i386-linux
eliminating the .pl extension as suggested in minstall. This is what happens: 

# texexec --make
`texexec.pl' not found.

I was able to use
texconfig --init
to get the default ConTeXt formats generated, but, as embarrassed as I am to 
say it, I don't know how to translate

texexec --make --alone --tex=omega en

to initex syntax (even if I get texexec working I'd like to know this as 
well). 

Any other tips on ConTeXt-teTeX welcome:-)

Thnx in advance

-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: texexec & teTeX

[Siep]

On Sun, 26 May 2002 15:10:36 -0600
"Idris S Hamid" <ishamid@attbi.com> wrote:

> Dear folks,
> 
> I'm in the process of migrating to Linux (Suse 8.0) and I'm having
> some problems getting texexec to behave:-)
> 
> Updating to the latest official ConTeXt I place the appropriate
> perl scripts in 
> /usr/TeX/bin/i386-linux
> eliminating the .pl extension as suggested in minstall. This is
> what happens: 
> 
> # texexec --make
> `texexec.pl' not found.

In later versions of teTeX, texexec is a little script that tries to
find and run the real texexec.pl in the texmf/context/perltk
directory:

#!/bin/sh
what=`echo $0 | sed 's@.*/@@'`
p=`kpsewhich -progname=context -format='other text files' $what.pl`
{ test -n "$p" && test -f "$p"; } \
  || { echo "\`$what.pl' not found."; exit 1; }
perl "$p" "$@"

If your version of teTeX works this way, then you should leave the
perl scripts where they are, under their original name, and you
should also leave the teTeX version of texexec and the various
symlinks to it alone.

Siep

Re: texexec & teTeX

[Bill McClain]

On Sun, 26 May 2002 15:10:36 -0600
Idris S Hamid <ishamid@attbi.com> wrote:

> I'm in the process of migrating to Linux (Suse 8.0) and I'm having
> some problems getting texexec to behave:-)
> 
> Updating to the latest official ConTeXt I place the appropriate perl
> scripts in 
> /usr/TeX/bin/i386-linux

I'm using SuSE 7.2. What does "which texexec" show? On my system:

    /usr/bin/texexec

which is a symbolic link to:

    /usr/share/texmf/teTeX/bin/i386-linux-glibc/texexec

As part of my ConTeXt upgrade procedure I do:

    cp context/perltk/texexec.pl \       
/usr/share/texmf/teTeX/bin/i386-linux-glibc/texexec

Same for texutil.pl and texshow.pl. Alternatively, one could adjust the
symbolic links, but I suspect SuSE upgrades will reset them.

-Bill
-- 
Sattre Press                                The King in Yellow
http://sattre-press.com/                 by Robert W. Chambers
info@sattre-press.com             http://kiy.sattre-press.com/ 

Re: texexec & teTeX

[Idris S Hamid]

Thank you both for your help. I'm halfway there now but no cigar yet:-)

On Monday 27 May 2002 01:33, Siep wrote:
> In later versions of teTeX, texexec is a little script that tries to
> find and run the real texexec.pl in the texmf/context/perltk
> directory:
> 
> #!/bin/sh
> what=`echo $0 | sed 's@.*/@@'`
> p=`kpsewhich -progname=context -format='other text files' $what.pl`
> { test -n "$p" && test -f "$p"; } \
>
>   || { echo "\`$what.pl' not found."; exit 1; }
>
> perl "$p" "$@"

I restored it, but I did not find any lines like this in the original 
/usr/TeX/bin/i386-linux/texexec. I'm using TeXLive6. 

On Monday 27 May 2002 00:24, Michael Hallgren wrote:
> Isn't it that the #! line (path to perl) in your script needs to be
> adjusted?
> ('which' to find perl on your system, then edit the first line of
> texexec.pl.)

Note that both the new texexec and the one from TL6 contain the same initial 
entry:

eval '(exit $?0)' && eval 'exec perl -S $0 ${1+"$@"}' && eval 'exec perl -S $0 
$argv:q'
        if 0;
:<snip>
#D We started with a hack provided by Thomas Esser. This
#D expression replaces the unix specific line \type
#D {#!/usr/bin/perl}.

In any case, backing up to the old TL6 version (texexec 2.5) works. My 
question now:  

How do I safely update to the latest texexec 2.8? I dumped cont-tmf into 
/texmf so context/perltk has the new files with the pl extension. I have 2 
copies of the original texexec 2.5: one in bin/i386-linux and one in 
context/perltk. I'm thoroughly confused about what to do, and I DON'T want to 
depend on an old texexec that may cause me other problems with the newer 
files.

Best wishes
Idris 
-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: texexec & teTeX

[Idris S Hamid]

Thank you, Bill. Still not there yet, though:-)

> I'm using SuSE 7.2. What does "which texexec" show? On my system:
>
>     /usr/bin/texexec
>
> which is a symbolic link to:
>
>     /usr/share/texmf/teTeX/bin/i386-linux-glibc/texexec

I get

:~> which texexec
/usr/TeX/bin/i386-linux/texexec

and my bin path for TeX is

/usr/TeX/bin/i386-linux

It may be that TeXLive and Suse install TeX differently and the teTeX rpm 
package for Suse8.0 may do things the same way as you have it.

> As part of my ConTeXt upgrade procedure I do:
>
>     cp context/perltk/texexec.pl \
> /usr/share/texmf/teTeX/bin/i386-linux-glibc/texexec

This is analogous to what I did but without changing the extension it seems 
that texexec gets ignored. If I remove the pl that's when I get the error 
message. Backing up to the old /usr/TeX/bin/i386-linux/texexec works, though.

This is frustrating; something so simple...

Best wishes
Idris

-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: texexec & teTeX

[Idris S Hamid]

> Is the texexec.pl script executable? (chmod +x). 

Just did this.

>If you specify the
> complete path name (/usr/TeX/bin/i386-linux/texexec.pl), does it run?

Ok, I got it working, though I'm not sure exactly what did it. Here is some 
more strange behavior:

If I'm in root and do texexec, everything works fine.
If I'm in my user account and do texexec, everything works fine.

If I su to my home directory from root (or su to root from my home dir), then  
texexec gives the error

> texexec
`texexec.pl' not found.

If from here I su back to my home dir (or to root), the error remains. 
Starting a new console works if I don't su anywhere.

I have installed the following in /etc/profile.d/texsetup.sh (based on advice 
from David Kastrup):

case ":$PATH:" in *:/usr/TeX/bin/i386-linux:*) ;;
  *) PATH="/usr/TeX/bin/i386-linux:$PATH"
esac

What am I doing wrong?

Best wishes
Idris

-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80526

Re: texexec & teTeX

[Idris S Hamid]

I apologize for sending the earlier mail to tetex-pretest instead of tetex.

> > If I'm in root and do texexec, everything works fine.
> > If I'm in my user account and do texexec, everything works fine.
> >
> > If I su to my home directory from root (or su to root from my home
> > dir), then texexec gives the error
>
> What do you mean with "su to [your] home directory"?  su is used for
> changing users, not directories.

My mistake; still new to Unix. Yes, I meant  "su to a different user id"

> > If from here I su back to my home dir (or to root), the error
> > remains.
>
> What does echo $PATH tell?  What does env|grep "^PATH=" tell?

My default shell is bash.

Upon opening a console:

~> echo $PATH
/usr/TeX/bin/i386-linux:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:
/opt/gnome/bin:/opt/kde3/bin:/opt/kde2/bin:/usr/lib/java/bin:/opt/gnome/bin:
/usr/TeX/bin/i386-linux:/usr/TeX/bin/i386-linux:/usr/TeX/bin/i386-linux 

> env|grep "^PATH="
PATH=/usr/TeX/bin/i386-linux:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:
/opt/gnome/bin:/opt/kde3/bin:/opt/kde2/bin:/usr/lib/java/bin:/opt/gnome/bin:
/usr/TeX/bin/i386-linux:/usr/TeX/bin/i386-linux:/usr/TeX/bin/i386-linux

> texexec

 TeXExec 2.8 - ConTeXt / PRAGMA ADE 1997-2002

                --help   show this or more, e.g. '--help interface'
             --verbose   shows some additional info

        total run time : 0 seconds

Upon su:

 # echo $PATH
/usr/sbin:/bin:/usr/bin:/sbin:/usr/X11R6/bin:/usr/TeX/bin/i386-linux

 # env|grep "^PATH="
PATH=/usr/sbin:/bin:/usr/bin:/sbin:/usr/X11R6/bin:/usr/TeX/bin/i386-linux

 # texexec
`texexec.pl' not found.

Here are all of the PATH mods I made:

1.  /etc/profile.d/texsetup.sh

 case ":$PATH:" in *:/usr/TeX/bin/i386-linux:*) ;;
  *) PATH="/usr/TeX/bin/i386-linux:$PATH"

2. in my home user directory, in .bashrc and .profile:

PATH="$PATH:/usr/TeX/bin/i386-linux"
export PATH

3. in my root home directory, 

in .bashrc and .profile:

PATH="$PATH:/usr/TeX/bin/i386-linux"
export PATH

> This is executed in login shells, but nowhere else.  One possibility
> would be that you need to add
> export PATH
> although I really can't believe that PATH would not already be
> exported.

I tried this; does not change anything

> Another would be that you have some settings in
> ~/.bashrc
> that reset the PATH to a fixed value.

My only other uncommented lines in .bashrc are

if test -z "$DISPLAY" -a "$TERM" = "xterm" -a -x /usr/bin/who ; then
    WHOAMI="`/usr/bin/who am i`"
    _DISPLAY="`expr "$WHOAMI" : '.*(\([^\.][^\.]*\).*)'`:0.0"
    if [ "${_DISPLAY}" != ":0:0.0" -a "${_DISPLAY}" != " :0.0" \
         -a "${_DISPLAY}" != ":0.0" ]; then
        export DISPLAY="${_DISPLAY}";
    fi
    unset WHOAMI _DISPLAY
fi

test -s ~/.alias && . ~/.alias

> A third one would be that after doing the change above you have not
> logged out: the change will only take effect in sessions started
> after it has been done.

makes no difference

> A fourth one would be that the permissions of
> /etc/profile.d/texsetup.sh are set in a way as to make the file
> unreadable for some users.

I checked; User, Group, and Others all have Read permission

> A fifth one would be that your default shell is not bash or a Bourne
> shell.

Default is bash.

Thnx to all for trying! I'll keep working on it....

Best 
Idris

-- 
Dr. Idris S Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80526