Bug 40610 - Latex build "cannot find Hyphenation patterns for US english"
Summary: Latex build "cannot find Hyphenation patterns for US english"
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: jmz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-15 20:00 UTC by Chris Shenton
Modified: 2004-06-14 14:28 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Shenton 2002-07-15 20:00:13 UTC
	
Ports cvsupped every night.  Built tex-3.14159 successfully a couple
days ago:

    cshenton@Palimpsest(306> pkg_info -ia|grep -i tex
    Information for gettext-0.11.2:
    Information for musixtex-T98:
    Information for p5-Text-Template-1.31:
    Information for p5-Text-Wrapper-1.000:
    Information for tex-3.14159:

Latex build fails on INITEX when trying to find a hyphenation
file. Details below.

Fix: 

Unknown :-(
How-To-Repeat: 	

Latex building starts OK:

    Palimpsest# pwd
    /home/ports/print
    Palimpsest# cd latex
    Palimpsest# make clean
    ===>  Cleaning for gmake-3.79.1_2
    ===>  Cleaning for tex-3.14159
    ===>  Cleaning for latex2e-2000.06
    Palimpsest# make
    ===>  Extracting for latex2e-2000.06
    >> Checksum OK for latex_mf-2000.06.tar.gz.
    >> Checksum OK for latex_tfm-2000.06.tar.gz.
    >> Checksum OK for latex_base-2000.06.tar.gz.
    >> Checksum OK for latex_tools-2000.06.tar.gz.
    >> Checksum OK for latex_graphics-2000.06.tar.gz.
    >> Checksum OK for latex_psnfss-2000.06.tar.gz.
    ===>   latex2e-2000.06 depends on executable: tex - found
    ===>  Patching for latex2e-2000.06
    ===>  Configuring for latex2e-2000.06
    ===>  Building for latex2e-2000.06
    This is TeX, Version 3.14159 (Web2C 7.2) (INITEX)
    [...]

Then fails running INITEX because it can't find the US hyphenation
file:

    * Now run INITEX on latex.ltx
    *
    ***********************************

    Overall statistics:
    Files  processed: 70
    Lines  processed: 75430
    Comments removed: 49662
    Comments  passed: 442
    Codelines passed: 22393
     )
    No pages of output.
    Transcript written on unpack.log.
    This is TeX, Version 3.14159 (Web2C 7.2) (INITEX)
    (latex.ltx (texsys.cfg)
    ./texsys.aux found


    \@currdir set to: ./.


    Assuming \openin and \input 
    have the same search path.


    Defining UNIX/DOS style filename parser.

    catcodes, registers, compatibility for TeX 2,  parameters,
    LaTeX2e <2000/06/01>
    hacks, control, par, spacing, files, font encodings, lengths, (fonttext.ltx
    === Don't modify this file, use a .cfg file instead ===

    (omlenc.def) (t1enc.def) (ot1enc.def) (omsenc.def) (t1cmr.fd) (ot1cmr.fd)
    (ot1cmss.fd) (ot1cmtt.fd)) (fontmath.ltx
    === Don't modify this file, use a .cfg file instead ===

    (omlcmm.fd) (omscmsy.fd) (omxcmex.fd) (ucmr.fd)) (preload.ltx) page nos.,
    x-ref, environments, center, verbatim, math definitions, boxes, title,
    sectioning, contents, floats, footnotes, index, bibliography, output,
    (hyphen.ltx
    ! OOPS! I can't find any hyphenation patterns for US english.
      Think of getting some or the latex2e setup will never succeed.
    \reserved@a ...e latex2e setup will never succeed}
						      \@@end 
    l.65 ...  latex2e setup will never succeed}\@@end}

    ? 
    ! Emergency stop.
    \reserved@a ...e latex2e setup will never succeed}
						      \@@end 
    l.65 ...  latex2e setup will never succeed}\@@end}

    No pages of output.
    Transcript written on latex.log.
    *** Error code 1

I don't know what file it's looking for; the only installed
hyphen-named file I find is:


    cshenton@Palimpsest(307> find /usr/local/share/ -name '*hyphen*'
    /usr/local/share/texmf/tex/hyphen.tex

And there is a hyphen.ltx in the port's work dir:

    cshenton@Palimpsest(308> find /usr/ports/print/latex/work/ -name '*hyphen*'
    /usr/ports/print/latex/work/base/lthyphen.dtx
    /usr/ports/print/latex/work/base/hyphen.ltx

the latter tries to include a "hyphen.tex" file and fails if it can't
find it, but the error message doesn't tell me where it's trying to
look for the file:

    \InputIfFileExists{hyphen.tex}%
       {\message{Loading hyphenation patterns for US english.}%
	\language=0
	\lefthyphenmin=2 \righthyphenmin=3 }%
       {\errhelp{The configuration for hyphenation is incorrectly
		 installed.^^J%
		 If you don't understand this error message you need
		 to seek^^Jexpert advice.}%
	\errmessage{OOPS! I can't find any hyphenation patterns for
		    US english.^^J \space Think of getting some or the
		    latex2e setup will never succeed}\@@end}
    \endinput
Comment 1 cshenton 2002-07-15 20:02:50 UTC
Immediately after sending the PR, I checked the environment root used to 
build the port.  It had the variable TEXINPUTS set with a couple 
directories that were not ones where the hyphen.tex files lives.  So I 
added /usr/local/share/texmf to TEXINPUTS and did a make clean then a 
make and it appears to have built LaTeX now.  

I just tried removing TEXINPUTS from my environment and did a make clean 
&& make and this also works.  

So it appears that if you define TEXINPUTS,  it better have  the 
system's correct path for the base  includes in it -- it won't include 
it by default in addition to whatever you put in TEXINPUTS.

This seems more like a (mis-)feature of TeX rather than the port but 
perhaps the port could check for a set TEXINPUTS and emit a warning or 
something.
Comment 2 Mario Sergio Fujikawa Ferreira freebsd_committer freebsd_triage 2002-08-04 19:08:26 UTC
Responsible Changed
From-To: freebsd-ports->jmz

Over to maintainer
Comment 3 Volker Stolz freebsd_committer freebsd_triage 2004-05-18 09:13:08 UTC
State Changed
From-To: open->analyzed

Partial pilot-error. Keep around, maybe there's a lesson to 
be learned in there.
Comment 4 jmz freebsd_committer freebsd_triage 2004-06-14 14:27:49 UTC
State Changed
From-To: analyzed->closed

The port has been patched and should now ignore the TEXINPUTS environment variable.