ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: texexec slow
Date: Thu, 23 Apr 2009 23:19:45 +0200	[thread overview]
Message-ID: <6faad9f00904231419u48ad969fwacff60a9d576a9ae@mail.gmail.com> (raw)
In-Reply-To: <20090423171029.62c8904d@KUBUNTU64>

On Thu, Apr 23, 2009 at 17:10, R. Bastian wrote:
> On Thu, 23 Apr 2009 16:55:56 +0200
> "R. Bastian" scribit:
>
>> "ruby $TEXMFCONTEXT/scripts/context/ruby/texexec.rb <texfile>"
>>
>> Haha ! with this tip I get an error message from 'pdftex' :
>> libstdc++.so.5 ... No such file ...

Taco, what's the state with this particular library dependency?

There are two problems:
- texexec might not always check if pdftex fails and it eats some
messages inbetween
- library dependency should be fixed

>> The libstdc++6 is installed. What can I do ?
>>
> I installed libstdc++5 - now pdftex complains "cant find ... 'cont-en.fmt' "

What about
    texexec --make --all
?

When I started using ConTeXt (2004) the average running time for
"hello world" documents was definitely somewhere between 30 seconds
and a minute. But it has improved dramaticaly over time (3 seconds in
the second run as I mentioned) whereas LaTeX runtime has increased.

But TeXLive 2007 is not so old after all, so it's still a bit strange.

> i dont know if it is of interest for you:
> - I switched back to TL2007 (now pdftex finds 'cont-en')
> - texexec source.tex compiles 3 min 14 sec for 1 page of pdf
> - pdftex -fmt cont-en compiles  1 sec and produces a dvi file

Weird. Maybe texexec does some crazy stuff, but it's a bit hard to
tell what exactly.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2009-04-23 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  8:24 R. Bastian
2009-04-23  8:48 ` Hans Hagen
2009-04-23  9:08   ` R. Bastian
     [not found] ` <6faad9f00904230222q166fbd8cvaf90f9ed7bca15f2@mail.gmail.com>
     [not found]   ` <20090423122232.5e7cdbc0@KUBUNTU64>
     [not found]     ` <6faad9f00904230329r6c31c5a3h4dfb2dbda1d998af@mail.gmail.com>
     [not found]       ` <6faad9f00904230332p21279574ud33a2b508955d69c@mail.gmail.com>
2009-04-23 12:37         ` R. Bastian
2009-04-23 14:26 ` Aditya Mahajan
2009-04-23 14:55   ` R. Bastian
2009-04-23 15:10     ` R. Bastian
2009-04-23 17:32       ` R. Bastian
2009-04-23 21:19       ` Mojca Miklavec [this message]
2009-04-24  6:36         ` Taco Hoekwater
2009-04-24  9:17           ` Mojca Miklavec
2009-04-23 17:40   ` 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=6faad9f00904231419u48ad969fwacff60a9d576a9ae@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).