I'm having problems starting ConTeXt with texexec
on my Gentoo system.
I've installed ConTeXt using the MikTeX Package Manager:
"for p in `mpm --list|grep context | tr -s [:space:] | cut -d ' ' -f 4`; do
mpm --install=$p; done"
followed by a "texhash" and an "updmap" for good measure,
and I've upgraded to the latest tetex-3.0_p1-r3 in Gentoo's portage.
I've also followed the guide:
http://wiki.contextgarden.net/Linux_Installation#Updating_Gentoo_Linux
and modified /etc/texmf/fmtutil.d/00fmtutil.cnf
by adding a '*' where indicated in the above referenced wiki.
followed by texmf-update.
BUT:
$ texexec --version
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006
pdfetex: unrecognized option `--alias=context'
pdfetex: unrecognized option `--undump=cont-en'
kpathsea: Running mktexfmt context.fmt
fmtutil: no info for format `context'.
tex : unknown
context : ver: 2006.07.14 12:08
cont-en : unknown
pdfetex: unrecognized option `--alias=context'
pdfetex: unrecognized option `--undump=cont-nl'
kpathsea: Running mktexfmt context.fmt
fmtutil: no info for format `context'.
cont-nl : unknown
total run time : 5 seconds
warning : use 'texmfstart texexec' instead
And if I try to process some contex file:
$ cat >test.tex < \starttext
Hello World
\stopttext
EOF
$ texexec test.tex TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
fixing texformat path : .:
{!!/home/jeremy/.texmf-config,!!/home/jeremy/.texmf-var,/home/jeremy/texmf,!!/var/lib/texmf,!!/var/lib/texmf,!!/var/lib/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf-site,!!/usr/share/texmf}/web2c/{$engine,}
fixing engine variable : pdfetex
executable : pdfetex
format : cont-en
inputfile : test
output : standard
interface : en
current mode : none
TeX run : 1
pdfetex: unrecognized option `--alias=context'
pdfetex: unrecognized option `--undump=cont-en'
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
(/usr/local/share/texmf/web2c/natural.tcx)
kpathsea: Running mktexfmt context.fmt
fmtutil: no info for format `context'.
I can't find the format file `context.fmt'!
return code : 256
run time : 1 seconds
total run time : 2 seconds
warning : use 'texmfstart texexec' instead
On Friday 29 September 2006 09:45, Jeremy Johnson wrote:
I'm having problems starting ConTeXt with texexec on my Gentoo system.
I've installed ConTeXt using the MikTeX Package Manager:
Miktex is for Windows, not Linux. Try another distro, such as TeX Live or the the minimal distro at the Context site, www.pragma-ade.nl -- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com
On Sep 29, 2006, at 1:35 PM, John R. Culleton wrote:
On Friday 29 September 2006 09:45, Jeremy Johnson wrote:
I'm having problems starting ConTeXt with texexec on my Gentoo system.
I've installed ConTeXt using the MikTeX Package Manager:
Miktex is for Windows, not Linux.
There is now a MikTeX package manager for Linux. Steve
Steve Peter wrote:
On Sep 29, 2006, at 1:35 PM, John R. Culleton wrote:
On Friday 29 September 2006 09:45, Jeremy Johnson wrote:
I'm having problems starting ConTeXt with texexec on my Gentoo system.
I've installed ConTeXt using the MikTeX Package Manager:
Miktex is for Windows, not Linux.
There is now a MikTeX package manager for Linux.
And it is best not to use it since it ships a context that believes it is running on windows... Taco
And it is best not to use it since it ships a context that believes it is running on windows...
Taco
OK,
I've uninstalled context: "mpm --uninstall=context"
as well as all other context packages installed through mpm:
for `f in mpm --list|grep context|grep ^i|tr -s [:space:]|cut -d ' ' -f 4`; \
do mpm --uninstall=${f}; done
Then I've downloaded
http://www.pragma-ade.nl/context/current/cont-tmf.zip
and followed the instructions in:
http://www.pragma-ade.nl/general/manuals/minstall.pdf
<edit and activate context formats>
# slocate fmtutil.cnf
/etc/texmf/web2c/fmtutil.cnf
/etc/texmf/fmtutil.d/00fmtutil.cnf
#texexec --make
<Regenerate formats>
#cd /usr/local/share/texmf
#unzip ~/DOWNLOADS/cont-tmf.zip
#texexec --make en de nl
#texexec --make metafun
I've also update /etc/texmf/web2c/texmf.cnf:
openaout_any = a
shell_escape = t
allow_multiple_suffixes = f
MPXCOMMAND=texexec --mptex
But I now get following error when I run:
$texexec new.tex
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
fixing engine variable : pdfetex
executable : pdfetex
format : cont-en
inputfile : new
output : standard
interface : en
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
\write18 enabled.
(/usr/local/share/texmf/web2c/natural.tcx)
entering extended mode
(./new.tex
ConTeXt ver: 2006.07.14 12:08 fmt: 2006.9.29 int: english mes: english
language : language en is active
Hi, Looks like your update went fine excep that you have an old format file still on your disk:
FatalError : Your format does not match the base files!
Context source version used to generate cont-en.fmt:
FormatVersion : 2006.07.14 12:08
Current (runtime) source version:
FilesVersion : 2006.09.28 22:43
Search the stale cont-en.fmt and delete it. Greetings, Taco
Search for the stale cont-en.fmt and delete it.
Right -- most likely produced by fmtutil before you commented out the automatic regeneration of context formats. Same problem happens with other Unix installations, e.g. I got bit a few times on Debian and Ubuntu. Here's one way to find the cont-en.fmt that you are using: $ kpsewhich -engine=pdfetex cont-en.fmt /home/sanjoy/.texmf-var/web2c/pdfetex/cont-en.fmt (when pdfetex finishes turning into pdftex, as in the latest pdftex releases, the engine line should I guess change to pdftex) Then you can look at it's date and make sure it's the one you just generated. kpsewhere does a more general tex path search, which looks in each TEXMF tree (kpsewhich tells you only the first one it finds): $ kpsewhere -engine=pdfetex cont-en.fmt /home/sanjoy/.texmf-var/web2c/pdfetex/cont-en.fmt -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
On Saturday 30 September 2006 09:55, Sanjoy Mahajan wrote:
Search for the stale cont-en.fmt and delete it.
Right -- most likely produced by fmtutil before you commented out the automatic regeneration of context formats. Same problem happens with other Unix installations, e.g. I got bit a few times on Debian and Ubuntu. Here's one way to find the cont-en.fmt that you are using:
$ kpsewhich -engine=pdfetex cont-en.fmt /home/sanjoy/.texmf-var/web2c/pdfetex/cont-en.fmt
(when pdfetex finishes turning into pdftex, as in the latest pdftex releases, the engine line should I guess change to pdftex)
Then you can look at it's date and make sure it's the one you just generated.
kpsewhere does a more general tex path search, which looks in each TEXMF tree (kpsewhich tells you only the first one it finds):
$ kpsewhere -engine=pdfetex cont-en.fmt /home/sanjoy/.texmf-var/web2c/pdfetex/cont-en.fmt
-Sanjoy
`Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
OK, I regenerated "texexec --make en de nl; texexec --make metafun" and checked to see what was created: # for f in `kpsewhere -engine=pdfetex cont-en.fmt`; do ls -l ${f}; done -rw-r--r-- 1 root root 6642152 Sep 30 16:04 /root/.texmf-var/web2c/pdfetex/cont-en.fmt -rw-r--r-- 1 root root 6562550 Sep 29 15:21 /var/lib/texmf/web2c/cont-en.fmt -rw-r--r-- 1 root root 6562550 Sep 29 15:21 /var/lib/texmf/web2c/cont-en.fmt -rw-r--r-- 1 root root 6562550 Sep 29 15:21 /var/lib/texmf/web2c/cont-en.fmt So, today (Sept 30) /root/.texmf-var/web2c/pdfetex/cont-en.fmt was created. So I simply copied /root/.texmf-var/web2c/pdfetex/* /var/lib/texmf/web2c/ "texexec new.tex" seems to run OK now, without error. I'll investigate further. THANKS.
So I simply copied /root/.texmf-var/web2c/pdfetex/* /var/lib/texmf/web2c/ "texexec new.tex" seems to run OK now, without error. I'll investigate further.
You run texexec as root, I'm guessing, so that the formats will be visible to all users. However, that means they go into root's .texmf-var/ directory because the TEXFORMATS kpse variable contains the home-directory .texmf-var before /var/lib/texmf. Here's how to check: $ kpsewhich --expand-path='$TEXFORMATS' .:/home/sanjoy/.texmf-var/web2c:/home/sanjoy/texmf/web2c:/var/lib/texmf/web2c:/usr/local/share/texmf/web2c:/usr/share/texmf/web2c:/usr/share/texmf-tetex/web2c Yup, ~/.texmf-var/web2c comes first. That's due to these lines in /etc/texmf/texmf.cnf, at least on my Ubuntu (teTeX 3.0) system: TEXMF = {$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFLOCAL,!!$TEXMFMAIN,!!$TEXMFDIST} TEXFORMATS = .;$TEXMF/web2c/{$engine,} The TEXMFVAR is short for $HOME/.texmf-var and is what means the formats go in /root/.texmf-var/. So, you need to change TEXFORMATS for the texexec run, telling it to place them in /var/lib/texmf: # TEXFORMATS='/var/lib/texmf/web2c/{$engine,}' texexec --make --all Or slightly more general, in case TEXMFSYSVAR changes someday from /var/lib/texmf (note all the horrid quoting): # TEXFORMATS=`kpsewhich --expand-path='$TEXMFSYSVAR'`'/web2c/{$engine,}' \ texexec --make --all I just tried it as root, and it seemed to work -- I got brand-new formats in /var/lib/texmf/web2c/pdfetex: # ls /var/lib/texmf/web2c/pdfetex/*.fmt /var/lib/texmf/web2c/pdfetex/cont-nl.fmt /var/lib/texmf/web2c/pdfetex/mptopdf.fmt /var/lib/texmf/web2c/pdfetex/cont-en.fmt
# for f in `kpsewhere -engine=pdfetex cont-en.fmt`; do ls -l ${f}; done
Or slightly simpler (using -U to preserve the order produced by kpsewhere): # ls -lU `kpsewhere -engine=pdfetex cont-en.fmt` or # kpsewhere -engine=pdfetex cont-en.fmt | xargs ls -Ul -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
On 9/29/06, Taco Hoekwater wrote:
Steve Peter wrote:
There is now a MikTeX package manager for Linux.
And it is best not to use it since it ships a context that believes it is running on windows...
But then it has to be fixed, not thrown away ... I bet that the main reason is one of the many "if (MikTeX)" switches in the source code assuming that MikTeX is running on windows. Are there any MikTeX/Lunux users around? (I work on windows 99% of time, but if I manage to install MikTeX on the linux partition, I'll give it a try.) The other thing is: I have no idea how the executables are created. I sent quite a few requests, so that now finally the ruby scripts are used instead of the old perl-based ones. But I don't have the slightest idea how they work under Linux. Mojca
Hi, I've installed Tex and Context on my Mac through II-installer and started to experiment with simple Context files. I'm using Texshop v2.09 as text editor. When I generate output with the pdftex default script I get a pdf-file with poor letter quality (thick p's and t's and j's). Also the combination of the characters ij are shown as .. in the pdf-file. When I switch to the default Texshopscript "tex + ghostscipt" I'll get a dvi-file. Double-clicking on this file generates a PDF-file with high quality characters and the ij characters. Apparently there is something wrong in my setup. Any ideas? Many thanks in advance, Robert Kroon
2006/10/1, Robert Kroon
v2.09 as text editor. When I generate output with the pdftex default script I get a pdf-file with poor letter quality (thick p's and t's and j's). Also the combination of the characters ij are shown as .. in the pdf-file. When I switch to the default Texshopscript "tex + ghostscipt" I'll get a dvi-file. Double-clicking on this file generates a PDF-file with high quality characters and the ij characters. Apparently there is something wrong in my setup.
Does this help? http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3 http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1 Best Martin
On 10/1/06, Mojca Miklavec
On 9/29/06, Taco Hoekwater wrote:
Steve Peter wrote:
There is now a MikTeX package manager for Linux.
And it is best not to use it since it ships a context that believes it is running on windows...
ConTeXt should adjust to the differences (see ruby/tex.rb), but someone may need to search out the bugs and report them.
But then it has to be fixed, not thrown away ... I bet that the main reason is one of the many "if (MikTeX)" switches in the source code assuming that MikTeX is running on windows. Are there any MikTeX/Lunux users around? (I work on windows 99% of time, but if I manage to install MikTeX on the linux partition, I'll give it a try.)
The other thing is: I have no idea how the executables are created. I sent quite a few requests, so that now finally the ruby scripts are used instead of the old perl-based ones. But I don't have the slightest idea how they work under Linux.
I have ConTeXt under MikTeX and also on Fedora Core 5 both using the
Aug. 8 release from a separate texmf-cont tree, so I didn't install
the MikTeX version at all (I did steal
texmfstart.exe from W32tex).
There were some problems in the MikTeX-2.5 betas due to different
command-line switches in linux (and W32TeX) versions of pdftex, but I
thought that had been fixed in the
final version. There are some system specific flags set in
base/tex.rb to deal with any lingering differences, so if there are
problems I'd compare the options for pdftex and see if they are
reflected in tex.rb.
--
George N. White III
participants (9)
-
gnwiii＠gmail.com -
Jeremy Johnson -
John R. Culleton -
Martin Schröder -
Mojca Miklavec -
Robert Kroon -
Sanjoy Mahajan -
Steve Peter -
Taco Hoekwater