public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: /bin in path before /usr/bin breaks latex
Date: Thu, 26 Apr 2012 17:05:00 -0000	[thread overview]
Message-ID: <4F998057.8080200@cornell.edu> (raw)
In-Reply-To: <CA+tVKpCVNKN0p1rpTWd2eXG=h38wzDa1RzoaVjVX_J31MjDsag@mail.gmail.com>

On 4/26/2012 11:05 AM, Mark Frazer wrote:
> Updating cygwin yesterday broke several of my scripts.  Turns out this
> was because they have /bin before /usr/bin in their PATH exported to
> child processes which broke latex.
>
> To reproduce:
>    env PATH=/bin:"$PATH" latex manual.tex
>
> Seems that the latex related symlinks in /bin do not function.
> Putting /usr/bin in the path first fixes this.

This has nothing to do with symlinks.  You have the same problem if you 
try to run /bin/pdftex directly.  Furthermore, the files in /bin are the 
same as those in /usr/bin (see /etc/fstab), so you can't remove files or 
symlinks in /bin without also removing them from /usr/bin.

The problem here is that the tex-related binaries don't find the 
configuration file /usr/share/texmf/web2c/texmf.cnf when invoked as 
/bin/* rather than /usr/bin/*.  I'll fix this and release an updated 
texlive package shortly.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2012-04-26 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:06 Mark Frazer
2012-04-26 17:05 ` Ken Brown [this message]

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=4F998057.8080200@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).