Mail Archives: cygwin/2004/10/25/12:28:31
> -----Original Message-----
> From: cygwin-owner On Behalf Of Alex Vinokur
> Sent: 25 October 2004 14:50
> "Igor Pechtchanski" wrote in message
> news:Pine DOT GSO DOT 4 DOT 61 DOT 0410250916210 DOT 28948 AT slinky DOT cs DOT nyu DOT edu...
> [snip]
> > 'mount' command, you can do something like
> >
> > mount -fst c:/cygwin /
> > mount -fst c:/cygwin/bin /usr/bin
> > mount -fst c:/cygwin/lib /usr/lib
> >
> [snip]
>
> There is some progress.
> Thanks.
>
> After that I have all my aliases.
> But here is what Cygwin concole shows.
> ------------------------------------------
> bash: kpsexpand: command not found // it is not mine
Presumably that non-cygwin installation of texmf that you have in your $PATH is
breaking the cygwin one:
Path: C:\texmf\miktex\bin
C:\WINNT\system32
C:\WINNT
C:\WINNT\System32\Wbem
C:\cygwin\bin
C:\cygwin\X11R6\bin
C:\DJGPP\bin
C:\my-root\sys\unix-mks\bin
C:\mingw\bin
C:\my-root\sys\sage
C:\my-root\sys\araxis
C:\dm\bin
C:\Borland\Bcc55\Bin
C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\include\
C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\include\
C:\Program Files\Microsoft Visual Studio .NET\Vc7\bin\
C:\lcc\bin
C:/Program Files/Intel/CPP/Compiler80/Ia32/Bin
C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\include\
C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\include\
C:\Program Files\Microsoft Visual Studio .NET\Vc7\include\
C:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\Lib
I mean, yow! You have texmf, cygwin, djgpp, MKS *and* mingw all in your path at
the same time. That's four clashing posix-on-windoze installations plus one posix
app. I think you'd better try isolating them from each other a bit more.
Also, I'd imagine that the reason that your install was fine until you recently
upgraded it, doesn't mean that something in setup suddenly got broken. I think
that in between the previous upgrade and the most recent one, you installed some
other clashing software on your computer, and it's _that_ which caused the problem
next time setup tried to work. If the post-install scripts fail and crash owing
to running in a clashing environment, you can expect lots of stuff to go wrong.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -