[tex-live] mptopdf problem: texmf.cnf not found.

[Byung-Jae Kwak]

On Wed, Sep 1, 2010 at 1:02 PM, Byung-Jae Kwak <byung.kwak at gmail.com> wrote:
> On Tue, Aug 31, 2010 at 11:41 PM, George N. White III <gnwiii at gmail.com> wrote:
>> On Tue, Aug 31, 2010 at 7:06 AM, Byung-Jae Kwak <byung.kwak at gmail.com> wrote:
>>
>>> On Tue, Aug 31, 2010 at 7:55 AM, George N. White III <gnwiii at gmail.com> wrote:
>>>> On Mon, Aug 30, 2010 at 7:08 PM, Reinhard Kotucha
>>>> <reinhard.kotucha at web.de> wrote:
>>>>> On 30 August 2010 George N. White III wrote:
>>>>>
>>>>>  > > It appears that somehow, MSYS interferes with my TeX Live install, and
>>>>>  > > the search
>>>>>  > > path is prefixed with "/msys/1.0".
>>>>>  > > Please help!
>>>>>  >
>>>>>  > When you move from an Msys process to a windows process, Msys tries
>>>>>  > to adjust environment vars that look like paths from "Msys" to
>>>>>  > "Windows" locations.  This certainly seems to be what you are
>>>>>  > seeing.
>>>>>
>>>>> I didn't encounter something like this on the MSYS version I installed
>>>>> two or three years ago.  I ran TeX and Perl in an MSYS environment.
>>>>> TeX Live doesn't set environment variables, so nothing unexpected
>>>>> should happen.  But ActivePerl sets PERL5LIB and it worked without any
>>>>> problems too.  Seems that you have a newer version of MSYS.  I don't
>>>>> have access to the Windows machine anymore.  If newer versions of MSYS
>>>>> really behave as you describe, I suspect they are buggy.
>>>>
>>>> See the entry "A tail about the Windows Unix shells and MSYS path mangling"
>>>> <http://curiousprogrammer.wordpress.com/2010/03/13/enablers-and-obstructors>
>>>> for some examples.
>>>
>>> I am not versed in UNIX enough to understand the blog entry.
>>
>> The UNIX part is that $PATH lacks drive letters and uses forward slashes.
>> MSYS works with "/bin" which Windows knows as "C:\msys-NN\bin".
>>
>> Please post your results for the two perl examples from the blog.  There is a
>> basic perl provided by TL2010, but it may be that some other perl is being
>> used.
>
> D:\>which perl
> C:\msys\1.0\bin\perl.EXE
>
> D:\>which bash
> C:\msys\1.0\bin\bash.EXE
>
> D:\>bash
> bash-3.1$ perl -e 'print $ARGV[0], "\n"' '/c/xxx:/c/yyy'
> /c/xxx:/c/yyy
> bash-3.1$ echo '/c/xxx:/c/yyy'
> /c/xxx:/c/yyy
> bash-3.1$
> bash-3.1$ perl -e 'print $ARGV[0], "\n"' "$PATH"
> /c/Ruby191/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/c/Python27/:/c/Program
> Files (x86)/Mercurial/:/c/Program Files (x86)/GnuWin32/bin/:/c/Program
> Files (x86)/Pandoc/bin:/c/gnuplot/binary/:/c/texlive/2009/bin/win32:/mingw/bin/:/bin/:/c/Program
> Files (x86)/gs/gs8.71/bin
> bash-3.1$
> bash-3.1$ echo $PATH
> /c/Ruby191/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/c/Python27/:/c/Program
> Files (x86)/Mercurial/:/c/Program Files (x86)/GnuWin32/bin/:/c/Program
> Files (x86)/Pandoc/bin:/c/gnuplot/binary/:/c/texlive/2009/bin/win32:/mingw/bin/:/bin/:/c/Program
> Files (x86)/gs/gs8.71/bin
> bash-3.1$
> bash-3.1$ exit
> exit
>
> D:\>
>
> Besr Regards,
> BJ

I just found out that perl comes also with TeX Live 2009. But the executable
is named differently:

D:\>which perl
C:\msys\1.0\bin\perl.EXE

D:\>which perltex
C:\texlive\2009\bin\win32\perltex.EXE

D:\>

So, I think what's happening is,
when I run "mptopdf logo.1", my TeX Live installation calls perltex.
When perltex is running, it uses the PATH provided by MSYS for
MSYS's own perl.

So, if this is the case, how do I ask perltex not to use the PATH set by MSYS?

Best Regards,
BJ