ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: Re: texexec doesn't finish
Date: Sat, 13 Sep 2003 19:48:17 +0200	[thread overview]
Message-ID: <m21xuko9zy.fsf@levana.de> (raw)
In-Reply-To: <pan.2003.09.11.02.56.28.510163@math.ubc.ca> (Boris Tschirschwitz's message of "Wed, 10 Sep 2003 19:56:29 -0700")

Hello Boris,


Boris Tschirschwitz <boris@math.ubc.ca> writes:

> I am using ConTeXt for a few weeks now without major problems.
> Today I felt like updating to the latest version (Aug 21?).
> Now when I try to generate even the simplest document (like 'texexec
> --pdf test.tex), texexec never finishes and spawns huge numbers of perl
> jobs.
>
> Any hint what I did wrong?


Not really. Are there any old texexec programs in your PATH somewhere?
Could you be more specific about your system configuration
(Windows/Linux/...)? Can you find out where texexec spawns the new
perl jobs? Is there any hint in the output?

 
Patrick

  reply	other threads:[~2003-09-13 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  2:56 Boris Tschirschwitz
2003-09-13 17:48 ` Patrick Gundlach [this message]
2003-09-13 19:22 ` Hans Hagen

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=m21xuko9zy.fsf@levana.de \
    --to=pg@levana.de \
    --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).