ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Idris S Hamid <ishamid@attbi.com>
Cc: ntg-context@ntg.nl
Subject: Re: texexec & teTeX
Date: Mon, 27 May 2002 07:17:55 -0600	[thread overview]
Message-ID: <200205270717.55165.ishamid@attbi.com> (raw)
In-Reply-To: <20020527064346.61891420.wmcclain@salamander.com>

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


  reply	other threads:[~2002-05-27 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-26 21:10 Idris S Hamid
2002-05-27  7:33 ` Siep
2002-05-27 13:00   ` Idris S Hamid
2002-05-27 11:43 ` Bill McClain
2002-05-27 13:17   ` Idris S Hamid [this message]
     [not found]     ` <20020527091854.4ba41f93.wmcclain@salamander.com>
2002-05-27 15:20       ` Idris S Hamid
     [not found]         ` <x5d6vhk353.fsf@tupik.goethe.zz>
2002-05-27 18:42           ` Idris S Hamid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200205270717.55165.ishamid@attbi.com \
    --to=ishamid@attbi.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).